Ariadne Conill

to be absolutely clear, I don't think anyone here is under any illusion that this isn't basically "`as:Public`, but please interpret me in a different way" but our patient (the...

the problem with using `sharingLevel` is that it doesn't really fit into how recipients are calculated, which, at least in Pleroma, we calculate a recipient set and then filter using...

fwiw I left out discussion of instance-wide actors because I figured that would be worse than leaving it flexible. should I just say "use an instance-specific actor to sign your...

> if you use an instance-specific actor to do an authenticated fetch, then that still says nothing about what the instance will do with the content afterward. the instance could...

and, yes, this is what i mean with `as:Public`. we already have something which behaves like a security label. so, lets just admit it's a security label, that it's advisory...

Yes, I think `Reject.Follow` would work to tear down the relationship.

Testing shows that Pleroma already accepts `Reject.Follow` to do this, incidentally. Now the question is what other implementations do? And when can we switch to that for unsubscribes? :)

To be absolutely clear, this case is for when you are unsubscribing someone else from your own actor.

Nice. Do you know what version of Mastodon this has been supported since? I'd like to organize a flag-day to switch to reject.follow instead of soft-blocking to do unsubscribes, as...

I think it would be reasonably safe to swap to Reject.Follow then in the short term. It'd be nice if we could get this documented as the *proper* way of...