Notification

[SoftlySplinter]

Upon a post being created a notification is sent out to all followers with access to the post and any entity mentioned in the post.

If the entity being notified is following the publishing entity, the following is performed:

POST <follower>/<notification_path> HTTP/1.1

Where follower is the follower entity (e.g.: http://tent.example.com) and the notification_path is the path specified by the follower relationship.

If the entity is not being followed (in the case of a mention) then the following is performed:

POST <entity>/posts HTTP/1.1

Where entity is the entity mentioned. This notification is signed by the publish entity if it is following that entity.

This seems a little bit odd to me. Posting to /posts is normally for creating a new post. So why it should be used for a notification seems a bit weird.

Completion

• Notify all followers
• Notify non-follower mentioned entities
• Sign the above if there is a following relationship from publisher to notified entity (potentially a separate issue)

[SoftlySplinter]

Non-follower mentions requires authentication to be complete so the server can check the request signing ( #22 )

[SoftlySplinter]

I believe @borntyping mentioned that the tent specification may be for the latter part, I'm going to move this to pytentd future pending this change.

[borntyping]

Currently wondering if Celery would be a useful addition, since it would allow us to send notifications in the background instead of the somewhat fragile way (i.e. if one fails, so do the rest) we do it currently.