search

randomouscrap98 / contentapi

A generic content system to make some kinda standard websites
GNU General Public License v3.0
8 stars 2 forks source link

Suggestion: add "permission update" event for content #129

Open randomouscrap98 opened 2 years ago

randomouscrap98 commented 2 years ago

When content goes out of scope due to a change in privacy, the people left behind don't know about it. You could send two events when content permissions change: first a "permission changed" event, then the regular activity event. This way, people know when permissions change and can update their frontends accordingly. Currently, the content would just sit there because nobody knows.

Oh right, this is all based on live updates, that's all

randomouscrap98 commented 2 years ago

Problem: who gets the permission update? It can't be everyone, what if it's already a private page and it's made MORE private? It should be sent to the previous list of people allowed by the old permissions? Is that possible to do?

randomouscrap98 commented 2 years ago

One suggestion given by 12 is to just generate the event BEFORE the new content is written, so it has the old permissions. However, I think the permissions assigned to the event come from a permission cache, and you can't have multiple permissions there.... see if each event has a copy of the permissions or not

randomouscrap98 commented 2 years ago

Another suggestion given by 12 is, to reduce the strain on frontends, it could look like a deletion event... mmm right... but I'd have to figure out for WHOM the deletion event should show