I have an account that I use to read, but I’ve never posted on Mastodon. Decided to tweet after seeing this post and I see a privacy option called “Quiet Public - Fewer Algorithmic Fanfares”.

Seriously, wtf is this? What does that even mean? If techie people like me can’t figure out Mastodon then you can’t expect the general public to do that. I’m not blaming this feature in particular, but Mastodon is quirky in all the wrong ways.

I drink ridiculously large amounts of water… I should probably drink less.

I mean regular keepass, I feel like XC is more likely to implement passkeys

Is keepass actually going to have support for passphrases? The author works in archaic ways and I have a feeling he’s never going to truly support it.

Fucking hell got so confused by the title, was wondering what the fuck do these guys have to do with cricket.

That’s regarded

Not OP but I’ve accidentally fingered another key a split second before hitting enter a few times. It’s not implausible.

Why are you acting like shoes with laces are the only footwear in existence

Lots of people don’t have the luxury of buying a laptop and a desktop, so they buy the best laptop they can afford to and hope it works real well.

This coward blocks accounts on Government request in India but not in Brazil? Guess he knows how to butter his bread.

Higher than normal but not even close to annoying IMO.

Lipi is basically alphabet bhai (or written script)

Obsidian is one of those applications I sooo want to install because everyone loves it, but to me if I’m going through the pain of selfhosting I want to go FOSS only. Argh!

In very basic terms - GPL means that any modifications you make to a code base and distribute to public, you need to keep the license as GPL and open source all your modifications.

Once cloud started becoming a thing, the cloud vendors went “Well ackchyually🤓, the code changes we’re making are hosted on OUR server so we’re not technically distributing them to the public. So fuck you we have no obligation to make them open source”.

Which is why AGPL exists so even server side code needs to be public. Since the application in question here is a backend service, it’ll always be used server side and so any forks need to be open source.

Normally a breaking change means after you apply the change it’s not easy/straightforward to rollback to the older version if you want to do that for whatever reason.

For example, a new version is released and underlying database table or structure changes. You upgrade properly, and find the new version has some bugs (or you simply don’t like it). If you want to use the older version again until the newer one is fixed it’s not a matter of simply point to old version.

As the database structure has fundamentally changed underneath in the new version, when you put back the old version it simply doesn’t understand the new structure and might stop working. You need ways to be able to make the DB structure compatible with the older application.

If the application is stable the devs might provide ways to do this. But since this is an alpha… You’re on your own.

TL;DR it means the older and newer version of the application aren’t strictly compatible with each other

… I think it’d be something you’d call an oxymoron.

I thought this was about FIFA

I’m surprised 27 was the original age, it feels high

UP needs to be nuked, fuck that Yogi