@r000t 2) Why not RSS or Atom? Not efficient enough? 3) What would be the point in this? 1) Does it already support something like robots.txt that allows instances and users to opt-out?
@bonifartius@Hyolobrika@r000t Scopes are determined by `to` and `cc` fields in the object. There is a special schema address (https://www.w3.org/ns/activitystreams#Public) that determines if the post should be public, if it's in `to` field, then the final scope is public, if it's in `cc` field, then it's unlisted.
@r000t@Hyolobrika > 1) Given how collection happens, that's tricky to implement. This is why ActivityPub privacy scopes are used, instead.
i never had the mood to really dig into AP, this reads as if the scopes are just flavor? guess DMs only are delivered to the respective servers, but "unlisted" is probably just pushed out like public posts?
@Hyolobrika 2) For use with existing applications that use the websockets API. This would allow you to funnel any amount of instances into one feed. This would probably dovetail with a built-in relay, which is essentially what is is. 3) Scale, mostly. There's a much longer answer if you want it. It also allows different people to run different parts. 1) Given how collection happens, that's tricky to implement. This is why ActivityPub privacy scopes are used, instead.
@bonifartius@Hyolobrika@r000t Unlisted posts are shown on profiles but not in public or federated feeds. His streaming endpoind is just TWKN updated in real time, I think.
@mint@Hyolobrika@bonifartius I kinda like the effect that his words are more or less wispy in the air, fading away, while the logo is sharp and center.