Post AyynTgRLm7TrGXSdd2 by julian@community.nodebb.org
 (DIR) More posts by julian@community.nodebb.org
 (DIR) Post #AyygqZCq8bkvoLddke by silverpill@mitra.social
       2025-10-07T21:10:49.077869Z
       
       0 likes, 0 repeats
       
       @julianDelete(Context)? This is very unusual because other collections are not created or deleted, they are server-generated views.I assume this problem arises when you create a topic for a remote post? Perhaps deletion of such topics shouldn't be federated?Or you can generateAnnounce(Remove(object: root, target: Context))It would be valid from the authorization point of view.
       
 (DIR) Post #AyynTgRLm7TrGXSdd2 by julian@community.nodebb.org
       2025-10-07T21:40:31.584Z
       
       0 likes, 0 repeats
       
       Well, the whole idea behind them being resolvable is so that when they are acted upon (by the context owner), they can be queried.For example if I receive a Delete(Context), I'll resolve it to find the root level post, and from there find my local representation, and delete it, assuming the actor was allowed to delete it.They're only server generated views per current usage... but why do they have to be constrained to that usage?
       
 (DIR) Post #AyynThS60pfgP8okQi by silverpill@mitra.social
       2025-10-07T22:25:09.989536Z
       
       0 likes, 0 repeats
       
       @julian Client generated collections are impractical. Collections are dynamic by nature, they can be paginated, filtered.That's why there is no Create(Collection), Update(Collection) and Delete(Collection).