my issue with snaps is honestly just that they are controlled too much by just one entity (canonical) and there is no reason for them to exist because flatpak already does everything they do.

yiff is furry sex

I think it’s meant to be about gnome’s refusal to show the user anything ever lest they be overwhelmed by 1 (one) ui element cluttering the screen.

yeah, which is why we need to make sure that doesn’t happen to other locks (and make the TSA start doing security instead of security theater).

so? does the quality of my lock change whether or not I should be allowed to have it?

I’m talking about legally, and as much as I don’t like trump we are not in a fascist country (yet).

fair enough, padlock was the wrong type of lock for the analogy. how about a vault door? sure that may not be as common, but you don’t have to support a government master key for those either.

Bolt cutters are not a key, they are a method of bypassing the lock. they still need a warrant to do that, which is the point.

@[email protected] I’ve been liking floorp and zen. used floorp for a while but i’m giving zen a real try for the first time in a while rn and I think it’s my favorite implementation of vertical tabs.

There is no ‘lawful access’ without a warrant or my permission. there aren’t laws saying padlocks need to support a government master key, and encryption is just a digital lock.

no more issues since that one thing i mentioned in matrix

@[email protected] sick

@[email protected] @[email protected]

mastodon is already the next twitter, bluesky is just a direct copy of it with nothing keeping it from going the same way. mastodon is open source (can’t be corpoed), federated (can talk to other platforms/instances so being on a small one doesn’t hurt anything), and most importantly, uses a protocol that doesn’t make self-hosting impossible due to storage requirements.

when the obvious troll is obvious

@[email protected] I think mastodon should implement a post-to-community type thing like mbin has for microblog posts. It (and all other fedi. platforms, really) also needs like a tutorial or smth to show how to actually use the federation features of the platform.

I may have issues I never had on windows but I have way fewer issues and if I mention them online roughly half the time a dude who develops the thing that caused it sees it and, completely unlike any microsoft employee, gives a fuck. I once mentioned that I experienced a bug in the only mbin mobile app in reply to a post that was related to mbin but not the app (directly, anyway) and jwr1, the guy who makes that app, responded asking what it was.

I have seen the reasoning they are actually presenting, and it is just various versions of “but I don’t want this to be here” even though they have the option of not interacting with it. nobody is forcing maintainers to support rust code in the thing they maintain, they just can’t prevent rust code from interfacing with it. their arguments are based purely on not wanting to interact with rust but they don’t have to, so they are wrong to block it.

being new does not mean you do not have the right to develop the same way everybody else is. they did not start these issues, there were C people causing issues for no reason other than not liking rust that started it.

cry about it?

yeah how dare they want to develop in the same way that everyone else does