596
What should we do about Threads?
(programming.dev)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 06 Jul 2023
596 points (96.1% liked)
Fediverse
28389 readers
170 users here now
A community to talk about the Fediverse and all it's related services using ActivityPub (Mastodon, Lemmy, KBin, etc).
If you wanted to get help with moderating your own community then head over to !moderators@lemmy.world!
Rules
- Posts must be on topic.
- Be respectful of others.
- Cite the sources used for graphs and other statistics.
- Follow the general Lemmy.world rules.
Learn more at these websites: Join The Fediverse Wiki, Fediverse.info, Wikipedia Page, The Federation Info (Stats), FediDB (Stats), Sub Rehab (Reddit Migration), Search Lemmy
founded 1 year ago
MODERATORS
In order to compete in user experience we need to up our game. We need to set up communities which collect, categorize and funnel user requests upstream. These features should be focused on:
This is meant to be a proxy between average users and tech enthusiasts who know how to do pull requests or open GitHub issues. Moderators of these communities would do it for them. This would enable us to gain visibility in the needs of the users.
This is only a part of what needs to be done, but I think this can be done quickly.
Lemmy doesn't need to compete. Hell, it can't compete. It's an open-source platform developed basically as volunteer work. Meta (and Threads) has millions of dollars and massive teams behind it.
Thankfully, we don't need Meta. We just need to do what we can to resist. The best we can hope for and what we should aim for is to limit the impact/damage Threads will have on our segment of the Fed. How to do that, I'm not sure exactly, but my first instinct is to block off anything corporate. Any interaction at all is basically just asking monied interests to take over.