Issue propagating Updates to Mastodon

julian

Haven't had the chance to test with other software, but sending Update(Note) via AP is accepted by Mastodon, but the resulting note isn't updated.

I thought it might be because I wasn't sending an id with my Update activity, so I started sending one, but no dice. Anyone have any other ideas?

On the upside, Update propagations work fine between NodeBB instances, so that's pretty cool.

Test topic once again

In this topic, I will be testing post editing, which should properly federate to followers via ActivityPub. => This is the edited text! Here is a second upda...

NodeBB-ActivityPub Bridge Test Instance (bb.devnull.land)

django

@julian the object probably needs an updated property with timestamp

small circle 🕊 in calmness

This post is deleted!

julian

@[email protected] indeed... that's a separate issue with the link-preview plugin in NodeBB. We parse urls into nice looking boxes, but that ends up in the HTML which Mastodon faithfully tries to preserve.

small circle 🕊 in calmness

This post is deleted!

julian

@[email protected] Yes, I do know about that too!

Right now I send back the user id, not the URL. Need to do some minor refactoring to make that work.

As for whether I send back the whole handle or just strip out the domain, I think leaving it in might be better from a transparency standpoint. It's up to the implementor I think, how to stylize it.

julian

@[email protected] but on the upside, your edit to your toot to add spaces to the mentions and urls propagated successfully back to NodeBB!

So, success! Onwards!