Don't worry. Elon's gonna sue and Zuck will quietly shut Threads down. /s

I've been reading blog posts taking various positions and remain undecided.

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:

• reducing frictions like unclear UI, broken links, etc.
• improving usability of the various web frontends (the one from Lemmy, kbin, etc.)
• collecting bug reports and making sure they will be fixed

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.

What worries me most is how this has shown me how how wildly insecurely ActivityPub seems to be storing and sharing user data.

@SDF@lemmy.sdf.org Would love to know from you, what do you plan to do?

What is the SDF's current attitude to Threads?

I'm somewhat undecided here, because ultimately I don't care for federated services to become dominant at all costs, nor do I care if they shrink slightly. I want the users of these services to voluntarily choose them based on the principles that federated social media stands for right now. My personal opinion right now is let them federate, but defederate the minute the "extend" starts. But we'll see.