#bubble

@a@fedi.layer02.net Decided to instead do what Mastodon does, since that's what most of the network is. And since it's always Mastodon. That section now is as follows. Differentiating between scopes can then be done like this: Public - to has as:PublicUnlisted - cc has as:PublicFollowers Only/Locked - Followers Only/Locked - Actor's followers Collection is either in cc, to, or both, and as:Public is in neitherDirect - Actor's followers Collection is neither in cc or to, cc and to have only Actors, and as:Public is in neither It can be more complicated since different scopes than that are being used, but this is the gist. As a side-effect I think it is also more readable. >if you wanted to, the bubble thing could be done with collections That would be ideal and that was also my intention. Issue is how you indicate it properly as a new scope without doing dumb things. You introduce a new special URI (ak:Bubble) that when dereferenced gets you a Collection. The jank would be, that cc/to would have something like https://ak.example.com/ns/extensions#Bubble and GETing that URI would give you an AP collection. Not really a fan of how that would work, but you don't have much options. Doing it the Misskey way of inserting _akkoma_audience: "Bubble" to the Object is even dumber. There is probably a better way, but I can't think of one right now.