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.

https://bb.devnull.land/topic/9/test-topic-once-again

django

@julian the object probably needs an updated property with timestamp

smallcircles (Humanity Now 🕊)

@julian

Here's a screenshot of how your toot looks like in my Mastodon web UI. Looks like Mastodon UI doesn't recognize the edits (revisions should be accessible at the bottom and indicated as "Edited").

The text "Text topic once again" in this narrow frame occupies 3 lines with the spacing at the start and end.

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.

smallcircles (Humanity Now 🕊)

@julian

Just FYI (you likely know already) ..

I also notice that in your reply my mention references URL "social.coop/users/smallcircles" and not "social.coop/@smallcircles" and with a link text of "@ smallcircles @ social.coop" (spaces added), not "@ smallcircles".

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!