AFAIK the C implementation is a kernel module that's not shipped in stock Android releases. The WireGuard Android app uses that module when available, but otherwise uses wireguard-go.
Good knowledge here, was unaware of this feature of the app. Would there be any case of the app defaulting to the wireguard kernel module if it's not included by any OEM Android release? I would assume that means most users are actually running wireguard-go.
Yeah they could take some lessons from Plato. However, koreader works on everything. Android, Kindle, Kobo, PocketBook etc. Not just on Kobo like Plato does.
It took me some getting used to but it's not bad IMO. It's more that its conventions are a bit different from the commercial readers but that's not a bad thing.
Koreader is pretty intimidating at first but once you dig into its features and know what's going on, it's pretty easy to navigate into the menus. It require some time to invest at first, but after that it's really "set and forget" with some lovely features and power to customise absolutely everything. I love the statistics wallpaper that shows you how much you read previous 7 days, per day, and the fact that you can set every book parameter as default, making every epubs looking the same, something I've never been able to achieve with stock Kobo, where I absolutely hated beginning a new book and discover huge fonts, weird margins, and tiny line-spacing, that I had to set again.
I just installed it on my Kindle Oasis. No way to just replicate the Kindle view of all my books in a list regardless of directory, and the real killer was that it doesn't invert page turn buttons when the display is rotated. PRs welcome, I'm sure, but I had to give up on it.
Unless the author is insanely rich, they probably don't want to spend increasingly large amounts on hosting unless they have a way to make money back (even if it's just to break even).
e.g. the machine is a big box. You can "start" the machine once and "end" it once. When you "start" the machine it instantaneously teleports everything inside it from when you "end" the machine.
If you "start" the machine and break it before "end"ing it, nothing gets sent through, or there's a giant explosion, or the universe collapses, etc.
Alternatively, you can "receive" and "send" any number of times on the machine. But every time you "receive" you get a unique ID, and you can only "send" to that ID once.
Doesn't any scenario of time travel imply an unlimited amount of entities?
If you go back in time to observe (but not interfere with) your younger self, your younger self will get old and go back to that exact time too. So there will be an infinite number of your old selves observing your younger self.
Not to mention that travelling back also means adding matter to the universe.
...and how would you actually do that if we assume that your travel has added matter to the universe, rather than completed an iteration of a time loop that was happening there already?
Yeah, "interfering with" is open to interpretation. One might argue that you don't have to say "hi" to yourself to interfere with, and it is sufficient to be within the same light cone.
Hurricane Electric support a hidden primary as part of their free DNS nameserver service (do you actually want to expose your primary when someone else can handle the traffic?)
Yup, but it's a bit of a dance for bootstrapping, since they require you to already have delegated to them, but some TLDs require all NSes to be in sync and answer for the domain before delegating…
How relevant is this in the context of the mesh networks under discussion?
How resilient are those protocols to attacks on the integrity of the network, when most (or signicant part) of the nodes are controlled by a bad actor and deliberately operate in a mode that prevents the functioning of the network?
