I'd like to point out that the South was only a fan of States Rights exactly insofar as they let them do slavery. The millisecond it came to forcing Northern states to return escaped slaves, they suddenly weren't the same principled supporters of devolving and federating power. Funny how that works.
And just in case it wasn't clear enough already: one of the first acts of the Confederacy was to draft a provisional constitution which explicitly authorized slavery, and which prohibited either Congress or any state from passing laws to the contrary.
That place is notoriously kind of a cult. I can see it from a place I frequent, and some of the staff at that place are co-op members. They occasionally engage in illicit gossip, any the co-op sounds awful. They also boast among their members several 60s era leftist terrorists, and weather underground hangers on.
It's not a cult. Sure, there are busybodies pushing weird issues at the general assembly meetings, but I'd compare it to Trader Joe's if it were staffed by mostly volunteers who only work every 6 weeks - bit incompetent, but very normal.
The product being open source doesn't prevent the situation the OP mentions. It just provides a mitigation or a workaround by forking.
I also hope it won't happen but many good projects have gone this way before.
In this case the investment is not for the password manager but for a new identity service. However if that doesn't end up providing the promised results, the shareholders will start looking at the existing successful product to extract more value. After all they own part of that now and they want their returns. It's just what they do. This will clash with the users' best interests sooner rather than later.
Then it becomes forking time but can they find a good maintainer? Open source is not always a guarantee for continuity.
Of course if the new project pans out this won't happen but it's a gamble, and one the existing userbase never asked for.
Yeah the Rust version works well. I had an issue with it when importing passwords from a file exported from Dashlane, but other than that no issues. And I run it on a bottom tier Digital Ocean vm.
Lots of people can't set up their own bitwarden servers on a slow weekend. Yeah I can, but I venture 98% of people can't. Sorry, you're assuming everyone (including every HN audience) member can do that. Are we supposed to just keep quiet? I think we all know what happens when the VC folks come in. If you haven't lived through it (I have a few times now) you've at least heard about it if you read tech news at all. As long as the comments are respectful I don't see any reason to gatekeep them
That's how it looks to me as well. OP's claim borders on FUD and comes a bit disingenuous while shilling their project. Bitwarden is opensource as well and there's also this independent popular 3rd party project that uses the bitwarden protocol that is much loved by the community.[1]
This is right. No none has yet written “The Design of Everyday Things” for voice interaction. We just don’t know what works yet so we are redoing what was done before.
Isn't one problem with this is that intermediate caches now have two resources that represent the same thing, therefore invalidation of intermediate caches will be nearly impossible?
They just have a domain validation cert. That doesn't mean much, other than your communication with the site is secure. And there's HTTP resources being pulled in invalidating most of that security. Bonus derp points for being a COMODO cert.
One thing they should consider doing is using the average of the surrounding points to rise or lower the score of a particular spot. For instance, near where I live there a number of examples where there is a green dot on one side of the street and a red on the other, just down the block they reverse, this doesn't make any objective sense at all.
I'd be cautious about that. You can easily have a dark foreboding alleyway just off a bright, well-lit street. Safety gradients (perceived and actual) can be quite steep.
