Bitwarden only autofills if the page’s URL is the same as the account in your vault. So it actually helps you make sure that you aren’t putting your info into a phishing site or something
This is true, though wasn't my concern. My concern is that it (and other PW managers ofc) can sometimes fill in fields its not supposed to, and you end up accidentally including a username or password in a GET header.
although, I’m pretty sure autofill is disabled by default anyway?
US Courts have already ruled in the past that human authorship is required for copyright. It'd be a logical conclusion as such that human authorship would also be required to justify a fair use defence. You providing a summary without any quotations would likely justify fair use - which is still copyright infringement, but a mere defence of said infringement. A machine or algorithm that cannot perform the act of creative authorship would thus not be exempted by the fair use defence.
Bitwarden checks all the boxes. I've had great experience with it. https://bitwarden.com/
I will say, auto-fill on load is a bad idea. On desktop I keep my auto-fill bound to a key so it doesn't actually end up in fields it shouldn't be.
2FA is locked behind the $10/year premium if that's something you wanted, but beyond that the free plan has everything 99% of people will use. They do third party security audits, have public white papers, and is completely open source.
idk I quite like the changes he's making. Rate limiting, preventing people who don't sign up from using it, killing embeds. It's all great for reducing the net presence of what has become an almost entirely white nationalist platform. If anything he's not rolling out these changes fast enough, for if he was, Twitter would have also restricted itself from having new sign ups (like Voat in its later years) and eventually completely shutting down.
It's an impressive game, 100%, but I don't think the comparison is quite so straightforward. Pokemon had only 8 KB working RAM, 4 shades of colour, and the cart only had 373 KiB stored on it. But the GameBoy CPU was over double the speed of the of the BBC Micro or the Acorn Electron.
Both are really impressive games for their size; though Elite's no doubt more impressive for its time given Pokemon Red/Green released after 5 years of development to an already quite aged handheld, and ended up undergoing a full revision to patch out the bugs with Pokemon Blue version a half year later.
I think the real king is ET, a multicolor game with a layered gameworld, and detailed graphics on just a 1.2MHz CPU, 128 bytes of RAM, with less than 6KB on the cartridge. The game made a few mistakes that cost it any recognition, but it's a really impressive game given its hardware and time.
There's also many small-to-medium sized instances that just haven't bothered signing that will be defederating. Mastodon.social's gonna be one of the few who do, and I already think it's fine to defederate from them too tbh.
Meta's fine with transphobia. I am not. It can hardly be called a decision at that point, I don't need Libs of Titkok and their ilk filling my federated feed.
I think this is going outside the realm of self-hosting and moreso into actually creating a server architecture. All servers would need to use the same database, so you'd want likely as its own server a database server, caches on the front-end servers so popular things aren't queried for the same info again and again.
I've never set up anything like this, so this is just me trying to think of how I'd throw it together, I'm sure there's a bunch of async problems I've not even considered how to tackle, and even having the DB be offsite from either of the front-end servers would be less than ideal.
I suppose you could have the DB in one of the servers, but then that one now has the same frontend-load as the other while it also is the only one doing DB queries, so the load's not really being distributed properly. 🫠
Ya, on Lemmy's end there'd still be control over the removal of content.
Though I do wonder if it even makes sense for interop to come from Lemmy's side? After all, Lemmy's just one of many implementations of ActivityPub. Kbin, Mastodon, and other softwares can freely traverse Lemmy with varying levels of usability. Instead of implementing Aether interop from the Lemmy side and give Lemmy access to Aether content, it seems more sensible to make Aether interoperable with the ActivityPub protocol. Of course this isn't exactly feasible without a maintained fork.
Ram @ ram @lemmy.ramram.ink Posts 0Comments 41Joined 2 yr. ago
MS isn't even top 2 in a hardware market of 3. They're not even top 4 in publishers either. Hardly a monopoly.