FEP-7888
-
infinite love ⴳreplied to Jesse Karmani on last edited by
@jesseplusplus I think blocks would be handled completely separately. If I send a post to a context's audience, and someone I block is in that audience, then they will receive a copy of the post. This isn't really something that can be avoided -- the audience belongs to the context, not to you. You are participating on the terms of the context's moderator or manager. A "block" just means that you will discard any post that *you* receive back from the blocked actor.
But there is a workaround...
-
infinite love ⴳreplied to infinite love ⴳ on last edited by
@jesseplusplus The workaround is, if you specifically want for your object to not be visible to someone, then you can make that object private, send out an activity that references it only by its id, and force everyone to fetch it directly from you... then, you can implement access control however you want. This probably implies some form of cross-domain authorization or authentication, so you can make that access control decision.
-
@julian @jesseplusplus yeah, more or less exactly this. you can sub out signed fetches for any other authentication/authorization scheme, but the general principle is that if you don't want someone having a copy of the object, then don't send out the object to audiences outside of your control. sending a reference is fine.
-
infinite love ⴳreplied to Jesse Karmani on last edited by
@jesseplusplus ohhhhhh, i see! that PR is nothing to do with context or conversation, it's about the "groups" PR here: https://github.com/mastodon/mastodon/pull/19059
-
Jesse Karmanireplied to infinite love ⴳ on last edited by
-
Jesse Karmanireplied to infinite love ⴳ on last edited by
@trwnh ahh, gotcha! thanks for sharing that PR
-
@trwnh @jesseplusplus @julian I'm also working on a FEP, it is based on Conversation Containers and FEP-7888: https://codeberg.org/silverpill/feps/src/branch/main/171b/fep-171b.md
Still not sure about outbox and collection-actor thing. I'll try to implement Conversation Containers and obtain an informed opinion
-
@[email protected] maybe we can press @[email protected] into service and discover what happens when instances send an Array
typeinstead of a string. -
@julian @silverpill @helge that would be useful information to have but you don’t actually need to make collection-actors into multityped objects, although it would be useful to define and multitype against some type(s) that described how the actor operates. But for now it can just be a Collection with inbox+outbox+followers. Later it can be a [Collection, Conversation, Context, Whatever]
-
infinite love ⴳreplied to infinite love ⴳ on last edited by
@julian To expand on that last bit:
- Collection = an AS2 Collection. (implied to have properties like items or first/last)
- Conversation = specifically contains objects with `content` (these contentful objects represent “posts”)
- Context = an `attributedTo` actor will Add objects that it encounters where `context` points to the current object (can be manually managed or auto or even self managed)
- Whatever = some extension type for some other use casecc @silverpill
