A single post is somehow creating multiple topics with no replies

Community
13

It seems to be getting worse, about ~15 identical topics have been created today.

And I still don’t understand why this change was made. Why break our past agreement about context being a collection, @devnull ?
Collection worked for everyone. Object adds an unnecessary layer of indirection, and doesn’t work for blogging platforms where “topics” may not exist.

I think context should remain a collection. Other features like “topics” and subscribing to conversations should be implemented independently. I mentioned a possible solution for the latter problem on GitHub, and will describe it in more detail here:

  • context property points to a collection
  • top-level post and/or context collection may also have an observer property, which points to an actor
  • this actor can be followed to receive conversation updates
  • it can also represent a topic

Example:

{
  "type": "Note"
  "context": {
    "type": "Collection",
    "items": []
  },
  "observer": {
    "type": "Application",
    "inbox": "..."
  }
}

What do you think?

There’s no intermediary between post and conversation collection. All components can be implemented independently. Only one new property. Compatible with ActivityPub spec.

2 Likes