Ram

Do you have a source on that?

It’s the heavy machinery required to do it that’s the problem. This is also not Elon Musk’s building, but a building Twitter rents. The building management company were the ones who called the police.

Or an AI that’s pulling over cheap and old cars because the owners are more likely to get ticketed due to living in over-policed neighbourhoods.

How long before we find out it always flags certain makes and models as criminals?

Rename Twitter Blue to X Pass

Rename the Post Tweet textbox to the X Box

Let me know when you know.

It’s legal to end a license at your own arbitrary discretion if that’s under the license terms (it is)

Ya I wasn’t really making an argument.

It’s entirely legal, yes. As people have been saying for years, you don’t own the games, you own a license to them.

They’re gonna be NFTs come next week

a lot of hate for capitalism here

The fediverse is largely populated by 2SLGBTQIA+ people and people of colour who are oppressed by capitalist regimes. The other big contingent is marxists and people who like FOSS. FOSS, at its core, is anti-capitalist.

You’re in a place founded by anti-capitalism, that exists in spite of capitalism, asking “why is there so much anti-capitalism here?”

Nuke Studio

If we find instances infested with bots and unwilling to deal with them, we defederate them. It at least makes it more difficult to mass-infest the network with bots if we have basic things like captcha, email verification, and applications implemented in all the major instances. cough

Based

This fediverse at least. AT Protocol, used for bluesky, supports nomadic identity. Instead of accounts being @[email protected], they attach your domain / home instance / whatever, to a DID. You can read more about it in their various spec pages but here’s the one for DIDs.

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?

Auto-fill on page-load is, yes.

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.

Don’t fill in this field, that turns your instance into a whitelist server. Remove everything from the allowed instances list

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.

You mean you read the article before replying about it???