Patrick Csikos @akzel@librem.one

I just pitched in a little to help fund Tusky, a great native Android app for Mastodon. If you use Mastodon on Android, consider doing so as well! https://opencollective.com/tusky/donate?referral=41229

"Most people want to opt-in to what they want to follow, be that a news feed, a celebrity, a friend, or family. Most people do not want to be force-fed a constant stream of manipulated content to catch and keep their attention." #LibremOne

https://puri.sm/posts/opt-in-no-ads-and-no-tracking-solve-a-lot-of-problems-in-society/

@purism Thx for this blog post. I would really appreciate it if you put a notice into Librem social that it is a fork of Tusky. Here is our opencollective in case you want to support the Tusky team https://opencollective.com/tusky

@cwebber

Trouble is we admin folk get to pay whack a mole with instances they may offer up or those who end up deploying their fork. We have no ability to stay ahead of the deployments and manage things appropriately.

I *could* get creative with an MRF in Pleroma to auto-block instances that don't public the usual mastodon timeines but that's guess work and leaves Mastodon instances open to more harassment.

I encounter at least 1 shitty instance per week and I'm NOT a target, I can't imagine what others who are targets have to deal with.

Why should we waste the collective time of others when the TOOLS EXIST ALREADY and were REMOVED?

Admins are rarely paid and I do not appreciate people wasting my precious time by removing safety features and pushing bock lists.

When was the last time you tried self-hosting e-mail? Ever end up on a block list or gray list?

How easy is it to undo a bad actor submitting your instance to a block list or graylist?

@Are0h

@purism you would be wise to merge !4 in your GitLab instance

https://source.puri.sm/liberty/smilodon/merge_requests/4

Not doing so would be a fools errand on the ActivityPub network.

Block lists do NOT work.

Ever self-hosted an e-mail server and had a bad actor submit your domain to a block list? How hard was it to be removed from said list once you were part of it? Were all of the other servers using that list ever updated to remove your entry once it was discovered and the problem rectified?

Think about that scenario long and hard, especially in the context of NON CORPORATE admins and actors who don't have the time, capacity or desire to fight with a block list removal because they were targeted by a bad actor.

PR to Purism's Masto fork: Revert "Disable Reports"

https://source.puri.sm/liberty/smilodon/merge_requests/4