Yep - and in that case, what you interact is, is your instance. You have no direct interaction with the Threads server, whatsoever. Your instance pulls that content (which is publicly available!), and shows it to you. If you comment on it, you do so on your instance, and it federates that comment back to the Threads instance (where the data federated is publicly available - it’s the content of your comment, and your handle). There’s nothing malicious going on here.
That’s not to say that something bad can’t happen in the long run. E.g., if people get used to content from Threads, and then Threads suddenly stops supporting ActivityPub (or forks it with negative changes), many people might be lured to start using Threads in order to keep accessing its content. That’s definitely a potential issue. But the technical side of federating with Threads is absolutely benign.
Yep - and in that case, what you interact is, is your instance. You have no direct interaction with the Threads server, whatsoever. Your instance pulls that content (which is publicly available!), and shows it to you. If you comment on it, you do so on your instance, and it federates that comment back to the Threads instance (where the data federated is publicly available - it’s the content of your comment, and your handle). There’s nothing malicious going on here.
That’s not to say that something bad can’t happen in the long run. E.g., if people get used to content from Threads, and then Threads suddenly stops supporting ActivityPub (or forks it with negative changes), many people might be lured to start using Threads in order to keep accessing its content. That’s definitely a potential issue. But the technical side of federating with Threads is absolutely benign.