ActivityPub

projectmoon@forum.agnos.is I will 100% be working on addressing all three of those use cases. I’ll rework it into my cross-posting functionality Relay support is on the list (awaiting NLNet funding) Auto cross-posting perhaps? (If uncategorized, it would just categorize it)

trwnh@mastodon.social before, I was not sending Accept at all, now I am sending application/jrd+json.

@julian@community.nodebb.org It would be good for outgoing posts if cross posting is used for synced categories. But it doesn’t solve the problem of incoming posts. For that, it would make sense to still slot incoming posts based on the sync setup. But there is still the problem of Lemmy not accepting follows from category actors.

A little semantics thing: I'd argue that HTTP 410 and as:Tombstone are semantically equivalent, i.e.an as:Tombstone should always be served with the HTTP 410 status, andA HTTP 410 status should be treated as a tombstoneSoftware unaware of tombstones will then treat it as a hard delete. "Fully" tombstone aware software can then use logic likeif (status == 200 && contentType is as2) { // treat as normal} else if (status == 410 && contentType is as2 && in body.type) { // also treat as normal} else if (status == 410) { // synthesize a tombstone} else if (status == 404) { // hard delete?} else // existing error handling logic

I think you’re right

@Kichae said in Organizing the many worlds you’re part of through NodeBB: > But man, do I ever desperately want the bulletin board experience in /world. It really feels like what the fediverse was always meant to be, to me. I’ve been inspired by some teaser images from @johnonolan@mastodon.xyz’s Ghost blog, which physically segregates microblogging content apart from long-form content (e.g. blogs). Forum topics fit somewhere in the middle, although since title and body are present we tend to align more with long-form content. It’s a really neat idea I’d like to play around with more.