I don't know how docker is to blame here; to me it's a bit unfair.
It's more about the setting of the ufw. Docker relies on their own NAT table, and setting ufw accordingly requires a bit of setup. That said, having a good setting from hosting provider is quite easier ans safer.
Docker's default goes against best practices. Just look at all those opened issues on Github. Clearly people get caught by surprise and may suffer a security compromise as a result.
Docker is 100% to blame here and they need to change the default! Just put it in the release notes and get it over with.
I had been a heavy Duolingo user and collected a great record until I had a crazy 2 days busy with some company work. Once I finished I recognized all my records were gone. I never use the app again =))
I couldn't go back (with Back button) once I visited the page https://rr-tw5.github.io/#DAILY%20NOTES. Honestly I really hate this style that many sites are using :(
THIS. Last time I pointed this out on another site I got downvoted. There really is no excuse to break the down button and if the abuse becomes widespread I can imagine browser devs will react the same way they did with popups.
As soon as browse nav was busted I totally lost interest in any benefits this app has. If nothing else it’s shoddy development.
You probably got downvoted because it was against the sidewide guides.
I sometimes/often wish there was tags on submissions so that one could avoid even clicking on stories that had this "feature". It would also be great if I could get a feed without, e.g US politics in it.
TiddlyWiki runs entirely in the local browser, without any server-side logic – sharing it with the world is an atypical use-case to me, aside from plugin demos. https://classic.tiddlywiki.com
That's the initial page that clicking on the submitted link redirects to. The back button seems to work in a standard way for navigation with the webpage itself (as it's just a single html file; it's Tiddlywiki after all); it seems that the back button is broken only across the initial navigation from an external site to this webpage. That's ok with me personally (just have to long press/long click the back button on Chrome/Firefox, and on Safari even the initial navigation works fine), given everything else that this page is doing. (Besides, in practice if you were to use this you would be opening the downloaded index.html file in a separate tab/window anyway, not navigating to it from other webpages.)
Me either. Getting some critical job done is impossible during normal working time when I get a lot of direct questions over slack and have to spend my time on meeting and communication.
The hard thing is that it's not easy to explain critical job' result to the team. Most people simply think that's [my] job.
The very annoying thing to me is that people tend to ask via PM. Why don't they just ask question on common group where there are a lot of people in the team can help? Oh... that's then Slack @here and @channel are problems. They are using that too much, and people don't care anymore lolz
I just delay any response for any new topic or I do not respond at all if that is just "Hi XYZ". Often I see "nevermind/found it/sorted it out" after a while.
My rule of thumb is 15 minutes.
I also never send "Hi XYZ" alone and then form a question. "Hi" is part of question message (Shift+Enter ftw!) and often while forming the question sentence with some guiding information I manage to find an answer too. No message send, win-win.
aws does this every 24 hours for a normal setup and that's pita. They just don't care what their users are doing. Yes I was on middle of something and suddenly saw that I had to log into their web console again. w???
It's more about the setting of the ufw. Docker relies on their own NAT table, and setting ufw accordingly requires a bit of setup. That said, having a good setting from hosting provider is quite easier ans safer.