I’m still using public instances for now. I started w/ Piped but the buffer speed was lacking for most of the instances I used. Switched to Invidious and the buffer speed as amazing, albeit a lot more error messages that Google is blocking an instance temporariliy

Similar thought process for me. The only downside I’ve experienced thus far is that once or twice a week, I’ll get error messages when I try to interact w/ content (upvote/boost/etc).

I think I’ll likely create another account when Threads joins the federation but kbin.social chooses to defederate 🤔

Thanks for linking! Currently using OpenBoard to get away from Swiftkey’s privacy issues, but OpenBoard’s lack of swipe has been a hard adjustment. FlorisBoard is en route to swipe tho it’s still very much in beta (but feels like alpha with the current implementation)

Same. Privacy was trumped by the environment (still use blockers tho)

Ecosia.org too

I am not an expert, but I don’t think there’s a “good for one crash” stamp or anything on the recorders, so I’d imagine that since they’re made as indestructible as possible, they could survive multiple plane crashes

Yes you would be able to few the content that is similar to our content here as well.

I do think a better way to think of it is Mastodon & Kbin though… You can definitely interact w/ toots on Kbin which stands out when compared to Lemmy. However, when compared to the Mastodon, the experience is not nearly as integrated enough to warrant using it as a replacement.

Based on what I heard on the Hard Fork podcast (where they interviewed Adam Mosseri), I think the plan is to build Thread-specific UI/UX experiences/features that go beyond the average ActivityPub client currently.

We would be able to read the threads, but we wouldn’t get access to any additional functionality built on top of the ActivityPub structure unless we replicated their code base.