It might be your bias, or even mine, but in my opinion, what you and I are saying are pretty much the same...
There is not much actual difference between "I heard here and there that some exotic glorified home tablet thingy is running it" and
"There are multiple devices that have shipped with Fuchsia on it in the home ecosystem over the last 5 years".
Would love to hear where it was actually used, searching for it, I really only found a handful of examples.
I was an active Flutter community member and it was driving me crazy how people would say "Flutter is great because Fuchsia also uses Flutter", and all I thought "show me one person who is using Fuchsia at this whole conference / meetup".
You can go to a normal store and buy a device using fuchsia today, it's just not advertising that is the OS under the hood. That is why I do not think what you said is the same thing.
Tailscale [0] says the private keys never leave the device.
“Security
Tailscale and WireGuard offer identical point-to-point traffic encryption.
Using Tailscale introduces a dependency on Tailscale’s security. Using WireGuard directly does not. It is important to note that a device’s private key never leaves the device and thus Tailscale cannot decrypt network traffic. Our client code is open source, so you can confirm that yourself.”
That is true as far as it goes, but how does your node learn the public keys of the other nodes in your tailnet? My understanding is that they are provided by the coordination server, so you have to trust that the public key the coordination server gives you is actually the one for your peer device.
Tailnet lock helps mitigate this by requiring that node public keys are signed by a trusted signing node, but it isn't bulletproof.
Like what? I'm saying both sides of the connection would be given the wrong public keys by the coordination server. The private keys of which would be held by a MITM.
To add to that, they also provides Tailnet lock [0], which protects from the only way the coordination server can mess with the tailnets, by connecting unauthorized nodes.
> Better UX would have helped adoption and would have led to Google keeping the RSS button
The most obvious people to have improved that UX is the browser... aka Google. The way that XML rendered was controlled by the browser. This all sounds like Google apologism.
Reader was killed in 2013, Chrome already had ~40% market share by then. It may have not been as dominant as it is now, but Chrome was already a major influence on the web user experience.
The funny thing is...non-Google browsers had even done that. Chrome was the odd one that didn't, and Firefox was still more popular at the time.
Firefox had Live Bookmarks, which I used for a long time. You'd just drag the icon to your bookmarks toolbar and then it would appear as a folder containing all of the entries as clickable bookmarks to the relevant web pages. The browser alerted you to autodiscovered feeds as well. The orange RSS pictogram (not the initialization) would appear right there in the URL bar if the site was set up right.
As early as OS X 10.4, desktop Safari had a built in RSS reader as well. You'd open the sidebar that's currently mostly used for the reading list and bookmarks, and there was some way to add the current page's discovered RSS feed with a button click or two. It also rendered feed XML in a particularly nice way that looked like a very clean looking blog, so landing on an XML page wouldn't intimidate less technical users.
Chrome deliberately was dysfunctional, and it taking over probably had more to do with RSS not growing more mainstream (as well as the rise of social networks and over commercialization) than Google Reader shutting down.
Did you actually look at that list? Most have under 1,000,000 in population. Many even have less than 100,000. There are only a handful of cities on the list comparable to NYC. It’s also worth noting that Manhattan would be 9 on the list, if listed as an individual city. The current number 9 is Port au Prince. Is that the kind of metropolis you were comparing NYC to?
The Jira I'm familiar with may be extremely powerful, but fast it certainly is not. I also rarely need that power which comes with non-trivial complexity.
But try telling that to the people who like feeding them. It'll just make them hide their feeding and the problem will persist.
I spent a lot of time a few years ago helping people trap and neuter their feral colonies, keeping the population under control with the support of the caretakers rather than fighting them.
Unfortunately, this won't solve the problem of feral cats, it only mitigates it. Culling doesn't really seem to work either though. Chemical sterilization is a promising approach, but hard to enact on large scale without sterilizing other species by accident.
Yup. Voting has received a dizzying amount of academic research. That doesn’t mean it’s impossible to innovate, but diving into that field without an advisor that’s familiar is a recipe for years of rediscovering existing results.
Also there's was a lot of over enthusiasm about moving voting to remote and online that took a while to get people to realize the major pitfalls they were setting up.
Did anyone ever solve the issue of vote verification (a voter being able to verify that their vote was counted) being a massive threat to vote secrecy? ie they're threatened to vote for Candidate X by a group and forced to show a verification they did?
