@lydiaconwell My impression is that the resources required to interface their system with Fediverse proved more than they expected, so the effort got pushed to the back burner.
@lydiaconwell Ha! I mean it reflects on the scalability issues with Fediverse's ActivityPub protocol, so it's not purely a reflection on Threads.
@volkris [Points at Threads] Ha ha!