ActivityPub question: why is it forbidden to change audience on an Activity after creation?
-
ActivityPub question: why is it forbidden to change audience on an Activity after creation?
#ActivityPub #Mastodon #FediverseDev #ActivityPubDev -
ActivityPub question: why is it forbidden to change audience on an Activity after creation?
#ActivityPub #Mastodon #FediverseDev #ActivityPubDev@liquidparasyte AFAIK, the ActivityPub spec doesn't prohibit a change like that. Is this a question about specific implementations of ActivityPub?
-
ActivityPub question: why is it forbidden to change audience on an Activity after creation?
#ActivityPub #Mastodon #FediverseDev #ActivityPubDev@liquidparasyte this is not forbidden.
However, there are two things that you may be talking about. I'll address both.
-
@liquidparasyte this is not forbidden.
However, there are two things that you may be talking about. I'll address both.
@liquidparasyte one is changing the `to`, `cc`, `bcc`, `bto` or `audience` properties of an object using an `Update` activity. That is allowed. However, it can not go back in time; if the object was already delivered to a broader audience, it cannot withdraw those deliveries after the fact. On the plus side, some implementations check the addressing properties before showing the object to the end user.
-
@liquidparasyte one is changing the `to`, `cc`, `bcc`, `bto` or `audience` properties of an object using an `Update` activity. That is allowed. However, it can not go back in time; if the object was already delivered to a broader audience, it cannot withdraw those deliveries after the fact. On the plus side, some implementations check the addressing properties before showing the object to the end user.
@liquidparasyte the second is replying to an object with a broader audience than the original object had. For example, replying to a private message with a public one. This is not technically changing the audience of the original object, but people use this term anyway.
This is perfectly workable but frowned upon socially. First, because most of your audience won't be able to see what you are replying to. Second, because the original author expressed intent for a private conversation.
-
@liquidparasyte the second is replying to an object with a broader audience than the original object had. For example, replying to a private message with a public one. This is not technically changing the audience of the original object, but people use this term anyway.
This is perfectly workable but frowned upon socially. First, because most of your audience won't be able to see what you are replying to. Second, because the original author expressed intent for a private conversation.
The former is what I had in mind.
So nothing in the spec prevents that, besides social convention/implementations not taking that into account?
-
The former is what I had in mind.
So nothing in the spec prevents that, besides social convention/implementations not taking that into account?
liquidparasyte@app.wafrn.net you can do it, there's nothing stopping you from doing it and re-delivering to any new recipients.
