Context deletion vs. Removal brainstorming
Technical Discussion
3
Posts
2
Posters
0
Views
-
Currently I am grappling with the specifics behind how to federate out the deletion of a topic in a category (or in ForumWG terms, the deletion of a context from an audience.)
For those unaware, a context is essentially an OrderedCollection containing all objects within its purview.
Deleting a note or other object is easy. If you are same-origin as the object, you
Delete(Object), done.Deleting a context is more difficult... you can't rely on other implementors to store references to your contexts, since it is essentially meaningless to them. Furthermore, if a context is deleted, then when a
Delete(Context)is federated out, receivers will have no idea what they're seeing, will try to retrieve the object, and find a 404. So it doesn't even work at all.Even worse, you can't really delete other peoples' contexts (or for that matter, their content) since you're not same-origin.
Finally, I realized I'm looking at this the wrong way — I'm not deleting contexts, I'm simply removing them from an audience.
Removeworks perfectly fine when the context continues to exist (as it can be referenced and duck typed).Removealso works for remote content; the same-origin check applies to the audience you're removing from.If you're deleting a context, you have to be the same-origin, and you really should just federate out deletion of the local members in that collection, via regular
Delete(Object).I suppose federating out self-destruction of a context would be the most complete but it is quite difficult to do when it is no longer resolvable...
-
undefined NodeBB shared this topic on
-
@julian I forgot, why do you want to delete a context? If it's your thread, isn't it enough to just
Deletethe top-level post? -
@julian I forgot, why do you want to delete a context? If it's your thread, isn't it enough to just
Deletethe top-level post?I'm looking into federating out deletion of contexts because in NodeBB the concept of a topic is a discrete entity, not tied to the posts contained within. Deleting the top-level post would not alter the topic in any way, except perhaps that the next oldest reply is suddenly promoted to top-level, which is odd.
Conversely, in ActivityPub, there either is no concept of a context (threaded objects only), or merely the suggestion of one as a view (current implementations of resolvable contexts). I'm hoping to move this more towards contexts as discrete entities with their own activities.
Gli ultimi otto messaggi ricevuti dalla Federazione
-
reiver@mastodon.social so, are we doing this?
-
fentiger@mastodon.social Flow control is the feature in TCP where the receiving host, in its ACK, can send back information about its remaining buffer space. The sending host can slow down its sending rate to prevent overflowing that buffer. If this works correctly, no error is ever sent.
-
In Activity Streams 2.0, we can represent the result of an activity using the result property. Here, when the actor accepts a Follow activity, the result is that the follower is added to the actor's followers collection.
{ "@context": "https://www.w3.org/ns/activitystreams", "id": "https://social.example/accept/12931", "type": "Accept", "actor": "https://social.example/person/24405", "to": ["as:Public", "https://other.example/person/21356"], "object": { "id": "https://other.example/follow/30360", "type": "Follow", "to": ["as:Public", "https://social.example/person/24405"], "actor": "https://other.example/person/21356", "object": "https://social.example/person/24405" }, "result": { "id": "https://social.example/add/11066", "type": "Add", "actor": "https://social.example/person/24405", "to": ["as:Public", "https://other.example/person/21356"], "object": "https://other.example/person/21356", "target": "https://social.example/person/24405/followers" } }My question is: how can the Add activity refer to the activity that caused it? I don't think we have a standard property for this. My best guess right now is context or maybe instrument, neither of which seems ideal. I think an extension inverse property, like resultOf, might be the best option.
-
I'm looking into federating out deletion of contexts because in NodeBB the concept of a topic is a discrete entity, not tied to the posts contained within. Deleting the top-level post would not alter the topic in any way, except perhaps that the next oldest reply is suddenly promoted to top-level, which is odd.
Conversely, in ActivityPub, there either is no concept of a context (threaded objects only), or merely the suggestion of one as a view (current implementations of resolvable contexts). I'm hoping to move this more towards contexts as discrete entities with their own activities.
-
@julian love to see the reports of cross project colab!
-
@elvecio Further investigation showed that this wasn't a Mastodon's fault. There was some weirdness on behalf of the originating instance.
Mastodon server received a post addressed to public and I received a post addressed to followers.
-
@silverpill
For superior control of your content, suggest to use hubzilla
-
@silverpill One thing that has always been different in Mike's software is that only authorized people can see non-public things. It is of little use to have the right address for the image, video, or file (as instead happens and happened in Mastodon Diaspora and others - almost all of them). In the software created by him, you cannot see even if you have an address/id or whatever you like.
