cross-posted from: https://sopuli.xyz/post/13985430

The problem:

Most #fedi authors post links with no idea if the hosting server discriminates against people, or who. The consequence is that the fedi is muddied with references to exclusive venues that do not treat people equally, which wastes the time of readers who are impacted by discrimination. A variety of walled gardens pollute our threadiverse experience. So how can we remedy this?

Proposed fix:

Suppose we create a community and designate it as a testing area which welcomes bots. So e.g. I post something in the test community, and a bot that is paywall-aware replies yes or no whether the link is paywall-free. A bot that is Cloudflare-aware does the same. A regional bot, such as a bot in Poland can check that Polish IP addresses can reach the URL and make noise if the website blocks Poland. Etc. It need not be just bots.. someone in some oppressed region might manually attempt to visit links and report access problems. We would certainly like a bot in a GDPR region to test whether access is refused on the basis of a data controller’s unwillingness to respect GDPR rules. The OONI project could have a bot that reports anything interesting in their database.

There could also be anti-enshitification bots, which point out things like cookie walls.

There are bots that find better links to replace Cloudflare links. Those bots could help direct authors to better URLs to share.

There could be a TL-DR bot that replies with a summary or even the full text, so an author can decide before posting in the target community whether to omit a shitty link and just post the content.

---

(update) It’s worth noting that for Mastodon there an ad hoc tool. If you follow @mg@101010.pl, that bot will follow you back and analyze every URL you share for whether it is Cloudflared. If yes, it will DM you with alternative URLs.

Note that the mitigator bot is quite loose it its judgement. If the host is not Cloudflared but another host on the same domain is Cloudflared, it is treated as a positive because it’s assumed that when you visit the host it will link to other hosts on the same domain.

It’s interesting to visit threads from an mbin instance because it shows you the number of up votes and down votes. When I see a Lemmy thread with 10 up votes then I go over to visit the same thread from mbin and see 20 up votes and 10 down votes, it really gives a different perspective.

i think this is for maintenance so mabye nothing too much to worry about.

The psychology of this problem is that users are too lazy to maintain multiple accounts when all they have is Lemmy’s stock web client. So they choose one of the big nodes: lemmy.world, sh.itjust.works, lemm.ee, lemmy.ca, etc.

These Cloudflare-centralized nodes are able to greedily exploit the #networkEffect because due to lack of multi-account software. If there were some well-made 3rd party client apps for Lemmy that would be designed for multiple accounts, then more users would be willing to create accounts in more decentralized parts of the fedi.

Mastodon somewhat proves this because the client-side tooling is in place to make it convenient to have 6 or Mastodon accounts. And Mastodon nodes are better balanced.

cross-posted from: https://discuss.online/post/6776820

The Sublinks team has written up a little survey, which we feel is both thorough and inclusive. It covers a wide range of topics, such as user privacy, and community engagement, along with trying to gauge things that are difficult when moderating.

Also please be aware the information collected by this survey is completely anonymous. As many of us in the social sciences background know, if you want the REAL feelings of individuals, they need to feel safe to express themselves.

👉Moderation Survey HERE👈

Please feel free to comment in this thread, we will do our best to respond to any genuine questions.

We look forward to hearing from each and every one of you!

Sincerely, The Sublinks Team