And prevent trackers, the official app uses.
Not sure about Lemmy, other Mastodon-like clients are better suited for this
If they federate, yes.
How? We don’t see Mastodon content in Lemmy unless they specifically tag a community or something. Why would it be different with Threads?
You don’t see anything if someone doesn’t subscribe to it.
If you follow someone on mastadon from lemmy/kbin in theory you’ll get… Something. Not sure how it works exactly. If threads federate then the same will be true of threads users.
How do you follow someone on Mastodon from Lemmy? I’m not sure that’s possible. I see you’re a kbin user so it’s possible for you, but I don’t think Lemmy users can.
If Lemmy instances defederate from Threads, it’ll just be a symbolic message that the fediverse is anti corporate greed. A good precedent to set imo, but our actual experience probably won’t be impacted either way.
What really needs to happen is Mastodon defederating from Threads.
If you search someone by @user on kbin at least there’s a follow option. Whether lemmy has the same and where it puts stuff I cannot tell.
Lemmy can’t afaik. Kbin is like Lemmy + Mastodon.
Even instances that don’t federate are compatible with fedi clients afaik.
That’s to say, if Threads is truly compatible, you should be able to use any fedi client. I doubt it actually works.
They will make sure no other client is able to read their content.
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.
