Proposed text:

Update to 6.4 Follow Activity:

The Follow activity is used to subscribe to the activities of another user.

The side effect of receiving this in an outbox is that the server SHOULD add the
object to the actor's Following Collection when and only if an Accept activity
is subsequently received with this Follow activity as its object.

Update to 7.5 Follow Activity:

The side effect of receiving this in an inbox is that the server MUST generate
either an Accept or Reject activity with the Follow as the object and deliver
it to the actor of the Follow. The Accept or Reject MAY be generated
automatically, or MAY be the result of user input.

In the case of an Accept, the server SHOULD add the actor to the object user's
Followers Collection. In the case of a Reject, the server MUST NOT add the
actor to the object user's Followers Collection.

New sections in Server-to-Server, probably after 7.5:

Accept Activity

If the object of an Accept received to an inbox is a Follow Activity previously
sent by the receiver, the server SHOULD add the actor to the receiver's
Following Collection.

Reject Activity

If the object of a Reject received to an inbox is a Follow Activity previously
sent by the receiver, this means the recipient did not approve the Follow request. The
server MUST NOT add the actor to the receiver's Following Collection.

I'm a bit concerned about how it's suddenly really easy to see if someone rejected your follow request. If I reject a request on facebook, I think it happens silently. Perhaps this is an implementation/UI detail that should allow people to dismiss requests (so they're not cluttering up the place) without explicitly acknowledging them (ie. the server doesn't ever send a Reject). Maybe we should have a NOTE about this though.

Maybe the 7.5 MUST should be a SHOULD, and we make a note about it MUST happen to be sure the other end knows you ack'd it, but if you don't ever want to ack it (or you want to wait 10,000 years to do so) that's allowed.

Accept / Reject a Follow #244

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions