Syncing was an utter disaster. Inevitably something would cause syncs to be delayed, and then there would be a conflict and one of our changes would be silently lost. We were constantly going to lookup a password we entered, and finding it was not there anymore, at which point I would have to dig through sync conflict backup files and manually reenter the passwords that were lost, or go through the password reset flow for the sites. It was a giant mess, and that was just with two desktops and a laptop. I was using btsync at the time but all the issues I encountered apply to any file based synchronization, like syncthing, nextcloud or dropbox. Performing whole database file synchronization is simply not the right approach for password safe.

I eventually switched over to self-hosted BitWarden with the browser plugin and it has been much smoother.

This is just a workflow issue. In the past it was very rare for multiple people to find and report a security vulnerability at once, so it made sense to keep the discussion private until they were ready to release a fix. With AI that is happening all the time, so it makes more sense for the discussion to be in public to avoid duplication. So they changed the policy accordingly. That is it.

[1]https://lwn.net/Articles/1066581/

Part of what made Mythos so effective for Mozilla was the integrated agentic workflow where it not only looked for bugs, but then created an exploit to demonstrate them, and ran that exploit while dynamic analysis was enabled verifying that invalid memory access occurred. In this case it hard to know how much of their success was because they put more effort into the harness compared to previous tools (we know they did), or if Mythos was more suitable for this sort of workflow to begin with.

Not many apple-to-apple comparisons to be made with Mythos at this point.

The flip side is drastically fewer parking spaces needed, most of which can be located outside of the city core. And decreased costs due to fewer accidents.

That is already a huge jump from two cities a year.

When I graduated college I used Dvorak and Emacs on Linux. Six months of having to use shared Windows lab computers extensively beat me down to surrender all of those points - my brain just couldn't handle switching, so I conformed my desktop to match. Then later I switched jobs to a group that was all Unix, but of many varieties most of which only had vi, not Emacs. And so I learned vi. Sometimes minimizing friction means going with the flow.

I don't think that old business names should be "retired" and forever banned from use. After a certain amount of time the name should be free for someone to use again, and 10 years of non-use seems reasonable to me. The main concern with reuse is confusing consumers into thinking they are dealing with the old friendster, but I think consumers are savvy enough to realize that an old trademark rising from the dead often has nothing to do with the original, regardless of whether the current trademark holders purchased rights from the original, or claimed abandoned ones, as in this case.

His other business dealings aside, I don't have a problem with how he obtained/revived the friendster domain and trademark.