What if Meta’s hidden objective behind the Threads-to-Mastodon initiative is a play on app.net? And, what if threads.net is a measured step towards what could be the greatest pivot in all of tech?
What if Meta’s hidden objective behind the Threads-to-Mastodon initiative is a play on app.net? And, what if threads.net is a measured step towards what could be the greatest pivot in all of tech?
Either start pitching realistic changes that can help protect the protocol or kindly stop posting this stuff. Everyone now has a pages long article all saying the same thing, and no one actually suggesting changes that could help.
At this point more people have spent time trying to figure out for Meta how they could EEE the fediverse then people have spent trying to make Libre fediverse better.
I mean y’all if want to spend your time thinking of cool and exciting ways meta can better extinguish the fediverse post it to LinkedIn and try to get on their payroll at least.
That’s my main point exactly. We all know it’s a threat, it’s been talked about to the point of annoyance here. We all have heard EEE here now. Anyone have ideas on how to prevent that from happening though?
Personally, I see decentralized IDs being a big one, one accepted account that can let someone log into multiple servers as the same person. That’ll lower the difficulty on choosing a server.
The other one, and this one I think may be controversial, but more and better feed algorithms. People want content that is relevant to them to be served to them automatically. Now we’re FOSS, and not ran for profit, so we can do even better a give people control over their algos, but I think most people would rather just click a couple interests and just get going and not have to figure out federated search and subscriptions before they do (not as a replacement but in addition too). The added benefit is we could potentially build a database of what a server’s network has access too and further help people figure out what server they want to join, so you get a little less dead Fediverse syndrome when you join a server that happens to block communities you would have been interested in. It of course could also be used to better refining searches in the first place.
Less feudal systems and more democracy for server admin, and community moderation I think will also help. Currently, admins and mods I think fall into lazie fair and organizers of the great purgers, it’s almost always been this way to me too. I think this will help make more server more aligned to their user’s interests and give servers a little more purpose for the end user.
More bridges! Matrix bridges (e.g. commune)! BlueSky bridges! Nostr bridges! Email bridges! SMS bridges! Signal bridges! XMPP bridges! IRC Bridges! More forum plugins and bridges! Q/A fediverse support! IndieWeb, just website bridges (good example bridgy-fed, but also the word press plugin! ). Meet people where they are. Make the Fediverse ubiquitous.
More selective federation rules, so you can have private server communities limit federation on per actor basis (Community/Group, User/Person, Post/Page, Comment/Note), maybe allow delays or rate limit federation, etc. Give servers and mods tools to be more granular on how they interact with the Fediverse so we get less ban hammer activity. This is most direct one to the current thread’s debate, but I think we need to do more than defederate. I think more servers should have a limited federation policy with Threads because of it’s size and influence, we want to interact with more people most of the time, but added where we need it and in ways mods and admins can handle (again more democratic systems could help here).
I also see a real potential for the fediverse everything app, but a big issue I see here is that the backend support is pretty tightly coupled with the fronts ends for most of the sites. At least there doesn’t seem to be a lot of reusue for the server and interoperability with multi UIs. That seems like the first real step towards that.
Some of these are problems for devs to solve, some for admin to implement, some are documentation issues, some are just the people that need to know about them don’t.
You’re right, we should all stop talking about and discussing problems and risks. And silently stare at each other tille someone else comes up with a solution.
Step 1 in fixing a problem is to recognize and get awareness for it.
Step 2 is garnering interest from the people who are qualified to actually make realistic proposals
Step 3 is collaborating on ideas to figure out what will or won’t be effective, and to create new ideas by returning to step 2.
Step 4 is to circle back to step 1, but for actions and implementations. Repeat ad nauseum.
**We’re Still in Step 1. ** Complaining that we aren’t getting to the next step quick enough without providing assistance to get there is incredibly meta to this process 🤔
I think what they’re saying is that we’re beating step 1 to death. Do that enough and people start ignoring the articles. If all the articles are saying the same thing, it’s not adding much to the discussion.
This article WAS a bit different though. It’s suggesting how the plan isn’t limited to microblogging or Mastodon but the fediverse as a whole, and what the process could look like
Yeah, what this guy said 👍
I think I see the problem. Theirs no path to step 4 in your workflow.