I presented a use case or a challenge that I had in connection with a use case in Fediverse. I had more or less accidentally used as:ignore → as:follow as an example.
marius (@mariusor@metalhead.club) - Metalhead.club contributed:
in my opinion an Ignore activity on an object means that any future activities that arrive with that object as an Object, or any different objects that have it in their inReplyTo shouldn’t get dispatched to the inbox of the actor that Ignored it.
If you look at it from this perspective, then as:ignore would be the wrong activity to express what I mean. And to my mind, this view sounds more like the as:block activity.
What I want to achieve:
You can as:accept or as:reject an as:follow activity.
When rejecting, there is the option with and without notification of the actor who sent the follow activity.
And i thought you could make a nice distinction by informing the original sender in the case of as:reject and NOT informing the original sender in the case of as:ignore.
@mariusor@metalhead.club How would you distinguish between these two cases?
If delivery is not desired, couldn’t the C2S Client simply not specify any targeting properties (to, cc, etc.) in the as:Reject response? The client’s server should still process the reject in the client’s outbox, but with no delivery targets, the response will not be delivered to any inboxes.
sounds like an easy solution 