Looks like #Threads still doesn't federate properly with #Snac2 or #GoToSocial.

Which may be a feature as far as most GTS and Snac users are concerned!

But I do want Threads to technically be able to federate with most/all other software that uses #ActivityPub, so it can be user/admin choice whether to accept connections from the giant instance...and more importantly, to cut down on the risks of vendor lock-in and EEE.

And I hope more compatible systems will cut down on the "OK, my software federates with itself and Mastodon, I'm done" problem. In some cases there may be bugs on the smaller project's side, and fixing them might also fix issues talking to other small projects.

GTS has already fixed a bug found by trying to federate with Threads, but there's still a bug on the Threads end preventing them from talking to each other.
https://github.com/superseriousbusiness/gotosocial/issues/2491

Key quote:
If Facebook had an issue tracker for threads, someone could open an issue there. If threads was an open source project, we could look at the code and immediately know what's up, but... 🤷
I might take a look at the Snac logs later and see if there's anything on this end breaking communication with Threads, or if it's all on the Meta side.