Comment on PieFed 1.4 is released - emoji, federated stackoverflow and AI content filters

<- View Parent
Skavau@piefed.social ⁨3⁩ ⁨days⁩ ago

My point, in one sentence: it’s not up to the developers of a project building on ActivityPub to define policy regarding “exposure”.

As someone who actually opposed the initial implemention of Piefed’s voting being made non-public to non-instance admins (as much as possible) to other users, I completely disagree. Some people don’t like it and don’t want their votes to be easily accessible to the wider fediverse. The only way that can be implemented currently is by removing federation. Rimu serves that.

This is a good example of *selection bias*. You are getting *most* of your feedback from *other PieFed users*, who clearly are not aware of the implications of such implementation.

No, I’ve seen this opinion from others. It’s also a wider criticism of the viability of the fediverse long-term in that communities are only as long as their hosted instance. This does a lot to mitigate that.

Yes, I am opposed to any functionality being added to the server when it can be solved at the client. Content discovered can be done by the client and using a separate service like Fediverser, fedidb, or anything else. It makes no sense to have this built-in into the ActivityPub server. It is one of the many examples where the piefed devs are adding a feature because they can without thinking whether they should.

Can you tell me exactly what harm this does to the mythical ActivityPub, beyond an instance owner toggling it on in ignorance to their own detriment.

source
Sort:hotnewtop