@Turret3857 I don't have any documentation, but I do know that Friendica (which is a multi-protocol platform) created a Bluesky addon. Maybe their code might be a good example. #^https://github.com/friendica/friendica-addons/tree/develop/bluesky
Also, Bridgy Fed can be used by any ActivityPub-based platform to connect to Bluesky. That can work in the meantime until direct integration with AT Protocol is developed.
<sarcasm>That's why we need sarcasm tags.</sarcasm>
The interesting thing is that Bluesky might become federated because of bridges to the fediverse. You would be able to federate with Bluesky with a fediverse server.
@Jupiter Rowland The public stream, if turned on, would only show the public posts. Not the private ones.
I was thinking about that the other day. Most fediverse servers won't even qualify to be federated with Threads. Especially single user instances, since they are unlikely to have a privacy policy for themselves and a public stream.
This is similar to how bridging ActivityPub and AT Protocol would result in more federation for Bluesky, while blocking the bridge would let Bluesky remain (mostly) centralized.
If you thought Twitter’s nonexistent moderation was bad, then get ready for Meta’s moderation.
To be fair, there is no global moderation on the fediverse. Anyone can start up their own instance with their own rules, or lack thereof. But that is also a plus since you or your server administrator decide how to moderate content, rather than depending on the decisions of some mega company's moderation team.
@ma1w4re It's because it works similar to email. When someone posts, it sends out copies of the message to all of the followers. But some don't arrive, or some people have blocks in place, or something is not configured right. As a result, not all servers get the complete conversation.
But some people are working to fix that so that all of the servers that support threaded conversations can download the complete conversation.
Something like this:
{ "@context": "https://www.w3.org/ns/activitystreams", "thr": "https://purl.archive.org/socialweb/thread#", "thread": { "@id": "thr:thread", "@type": "@id" }, "root": { "@id": "thr:root", "@type": "@id" } "traits": { "traits": "inbox, outbox, conversation, amendable" }}
This would let me know that it is a thread and that people can follow the context. I can then render it as a thread and potentially add a follow or subscribe button for the context.
You could also declare that it does not have an inbox and outbox, which saves me the trouble of checking myself.
@TheAlbatross
One of the problems is that if the post is public, anyone you block could just log out and see your post.