As the morning dawns, Cy awakens a little tentatively, cautiously opening his eyes and hoping his headache didn't return. After a few moments, he determines he's feeling pretty well -- other than his ribs, which still echo with the force of Rowan's sister's embrace. Working through his morning routine, he dons his cloak and re-packs his backpack, then steps out of his tent, looking for Edwin to have a short discussion.
That's easy, use a password that has a single apostrophe in it. No joke, shit was screwed up royally because the root MySQL password got left unset and the rest of the install script shits bricks because of that.
remotely turn on/off...and adjust temperature or time on your oven
The only possible use I could see with that is some kind of reminder... "You left the stove on, dufus".
That could actually be useful...
I remember this one time back when I was in 5th grade where something like that might have come in handy.
We had a pretty simple procedure on Sunday mornings. Part of it was preparing a big pot of soup: the parents would put all the ingredients in the pot, turn it on High to get it boiling, and then turn it back down to Low before we left for church to keep it warm, so that when we got home, there would be a nice warm pot of soup waiting.
Guess which step they forgot this one time?
We arrived home to black smoke pouring out one of the windows. Luckily a fire hadn't quite started yet, but the soup pot now contained a massive hunk of charcoal, and it took weeks to get the smoke smell out of the house! Some sort of automated warning from the stove would have been very useful. (Conveniently ignoring the fact that this was well over a decade before the advent of the smartphone or IOT stuff...)
So you simply can't make a "Linux program", unless you only want to use text I/O and don't depend on external services. You make a Ubuntu program, or an OpenSUSE program.
Or you depend on a higher-level platform on top of those variations that hides all that stuff. Which is what most people actually do. (As a bonus, it also usually makes the program easier to port to other platforms too.)
Tip: If you do your thinking by composing and re-composing posts in the editor over a longish period of time, make sure to refresh the page after posting. Sometimes the websocket hiccups and posts don't stream in and then your read marker is on your own post and you miss something.
IMO they should crawl following the current robots.txt, but only display what the authors authorized and things already in public domain.
IMHO they should archive every page regardless of what robots.txt says, but not necessarily display it (I’m not sure whether that should use robots.txt as it was when the page was archived or when it’s viewed, though — both have their pros and cons). This leaves it possible to make the information public later on, when copyright has expired or is lifted by whoever owns it.
It's the same on android. In landscape you can read but posting is impossible because it doesn't quit seem to get it's head around displaying both the composer screen and the keyboard simultaneously let alone see anything that you are replying too.