hachyderm.io is one of the many independent Mastodon servers you can use to participate in the fediverse.
Hachyderm is a safe space, LGBTQIA+ and BLM, primarily comprised of tech industry professionals world wide. Note that many non-user account types have restrictions - please see our About page.

Administered by:

Server stats:

9.8K
active users

I'm not sure how much overlap this has with the principles of what you're doing, but CC @ariadne for comments.

@dalias I think it should be more granular; requiring permission to quote boost should be an option and the default should be "deny always" for safety reasons.

@yuki2501 If you read back to the top of the issue, that's how it was originally proposed (except for deny-all not including deny-self 😀). I just didn't go into detail on the policy options there because the same sketch works whatever the set of policy options are, and whatever the default is.

@dalias in my implementation, posts have capability URLs, which can be personalized so they expire after a single fetch, or where continuous fetching is allowed (thus, boosting/quoting is allowed)

@dalias Do I understand correctly that in your proposal the quoted party gets "bcc"ed mentions of any ensuing discussion of the boost quote? If so, why is this desirable? It sounds utterly horrifying to me.

@siderea No, the idea of the "b" in "bcc" is that further replies won't cc it, but I don't know if that works on here. If not, it needs a different mechanism. The whole idea is not to do that, because yes, I agree that's awful.

@dalias Phew! Okay, I guess I still don't understand what you mean to have happen by "bcc". Who is getting bcced? When?

@siderea The list of @'s in the post body text and "outbox" addresses for delivery are separate.

The idea is to include the quoted post author on the latter but not the former so they get notified and get to see the post even if they otherwise wouldn't be in the audience for it, but so anyone replying to the quoting post don't include them in @'s of replies.

@siderea "Bcc" isn't a term used in Mastodon/ActivityPub AFAIK, but the idea is that it's analogous to Bcc in email, where you omit the "Bcc" addresses from the outgoing email header but include them in the transport level metadata so that the mail gets delivered to them too.

@dalias (Yeah, I'm v familiar with email, hence my confusion.)

@dalias Ah!

Presumably nobody mentioned in the original toot should be on the outbox for the boosted toot, either. Like if you're discussing something with a third party, and page me in with a mention, and then that toot gets quote boosted, I do not want replies to the subsequent discussion, either.

Really, it sounds like a boost quote should have no live mentions in the quoted part. The toot author should be notified, of the quote boost, but only the added commentary is live on it.

@dalias To put it another way: the boosted toot's author is notified of being quote boosted, but the way the quote boost displays, in the quoted parts, all the @S aren't live, and do not propagate to replies.

@siderea @S Right. The @'s within the quoted part are just part of the "embedded preview render", not text that will be picked up when someone hits reply.

@siderea The "quote boost" doesn't actually contain any of the quoted post, just a link to it, so none of the @'s from it are present in the quoting post unless you put them there.

Doing a "hidden, non-propagating @" of the author is just to let them know they were quoted (and give them an opportunity to react, block or report if unwanted, etc.)

@dalias Amazing! Thanks very much! I've put some curation here so it doesn't just disappear!