PaaP! Platform-as-a-platform!

The one-time payments sound interesting. I learned the internet in the 90’s, so I don’t “do” subscriptions. Hence I’m on SDF,

The fact that it is still tried to pass one, two, three times, is problem enough. Good has to fight, tire out and win every time; evil only has to win once.

Mirror? What even for?

Each of them.

You could use XMPP but they don’t have any nice clients

[citation needed]

There’s at least three good clients for Desktop (multiplatform) and two for Android.

Plus, XMPP is the best thing to run service-wise. Relatively cheap, runs on a potato, not a nu-protocol that requires a server cluster and friggin’ npm.

There was a commit posted in another thread by the creator where they specifically substitute thorns (þ) to spite a member of the community who uses them.

opt-out

Shouldn’t it be the reverse? That communities opt-in into this feature? It’s 2025 we all know opt-out by default is bad.

Do not eagerly misread what could be an evidence of the converse - that we already have low policulturalism because of difficulties in implementation and this feature is just going to nail the nail in the coffin.

It’s a crapload more work to support XMPP/Matrix/whatever messaging on any platform than just using a robust, reliable, resilient, widely supported good old SMTP

For the minimal of sending out a message to their accounts, they are just as easy as each other. Heck, there are simple packages to send XMPP messages from the CLI.

From comments in the bug report I got the feeling they should have, but aren’t; proably because of intrinsic issues with what it means to be a “system” component.

I have no means to test in Firefox Linux if local fonts are hidden because I don’t know what makes a font “local” either. Any font placed where the fontserver looks for them (be it system paths or .local/share/fonts) seems to count as “system”, which is why I specifically suggest using .local/share/fonts with different users: it’s the only path where you can offer variability. More importantly, CSS font visibility settings seem to mostly be intended for Javascript-based fingerprinting, and they do not work at all against CSS-based fingerprinting.

I am pending to raise an issue ticket to make it so that “Use Document Fonts” becomes a Site Preference instead of a Global Preference; that should go a very long way to enhance privacy in these cases. Once I do, I’ll link it here.

I don’t know how that helps either, since it is a fixed diff. Just pre-check adding 48 to any sus screen resolution you get reported. Enabling letterboxing by default and reporting the screen resolution as the nearest larger “common” size would be a far more practical response.

One known problem is that on Firefox for Linux, every font you install via the package manager becomes a System Font, and thus is immediately “visible” as soon as Use Document Fonts is enabled, irrespective of the setting for CSS font visibility. I’ve even asked about here if it is possible to run multiple fontservers on a single session, as that would help palliate the fingerprinting by running Firefox profiles connected to different font lists.

As a relatively useful alternative, you can have Firefox profiles on different users, each having their own fontset available at .local/share/fonts, but for that to work you also have to remove all those extra fonts you installed via the package manager.

Agree. Piefed doesn’t give me much confidence with their “centrist-esque” more-centralized-than-not, and actually has lost some in my eyes since the creator has specifically pushed code for antagonizing one specific member of the community for the sin of [checks papers] behaving in a quirkier way than the average.

Agree, this basically feels like it would generate various dark incentives in the Fediverse. A bit far too similar to the social networks we are supposed to escape from, even.

So thats why whenever I try to find a package in apt, I have to iterate through thousands of simiparly named librust-{dictionaryword}-{component}-dev packages in order to find the simple component I want… Apt repos have really been trying too hard for granularity, I’m pretty sure there are more librust áckages than actual end-user program packages.

What drugs are you even on? Share me your dealer, c’mon. Why would I want to be mad? I’m just look observing the world around me, it’s not my fault it has gone to shit.

It might not require anything more as currently written, but it’s a foot-in-the-door. Its acceptance and implementation will be taken as precedent that more compufascism can and should be implemented.

It’s still pretty bad and senseless. We all know how antis, nazis and conservationists are: you given them an inch, they’ll try to bite your entire arm off, not to mention leaving an infection behind.

Any particular reason why you can’t do something like host a Send instance instead? Better to treat “filesystem behind the network” and “files to share” as two different things: one is imanent, the other is punctual and sporadic.