Piero Bosio Web Site

ska can you please check that those three posts are actually federated outwards?

The human-readable URLs don't contain the expected Link header to the ActivityPub resource.

e.g.

link: ; rel="friends-base-url"
link: ; rel="https://api.w.org/"
link: ; rel="alternate"; title="JSON"; type="application/json"
link: ; rel=shortlink

It does contain the shortlink, which I tried to pull with the appropriate Accept header, but was sent HTML in response.

Perhaps there is a toggle you can press to enable federation on those posts?

Confirming at this time that at least the first URL shared does not get pulled in. Debugging.

ska which one doesn't work?

Does it work here?

ska ok great news thank you!

ska I added some logic changes to better handle the locks... can you update to the latest version on the develop branch, and run NodeBB using ./nodebb dev?

ska Are you able to restart NodeBB without using the regular buttons from the ACP... just by stopping the service from the command line and restarting?

Then perhaps the locks will clear.

ska Unfortunately I can't seem to reproduce the issue on my test instances (here and one other). The URL does seem to load fine.

Are you able to SSH into your forum server? Can you run curl -H "Accept: application/activity+json" https://www.lealternative.net/?p=63326 and tell me what shows up?

ska that is just a coincidence

baris added the additional logging at the same time

ska hmm that sounds like a regression, can you share the link to one of your posts here?

(Actually nevermind, I see it in OP.)

Can you try something for me... Can you restart NodeBB, and then search the direct post ID instead? (The one displayed in the log snippet you sent)

rimu@piefed.social that's surprising, isn't aguppe just a standard 1b12 community?

What integration did you have to add?

I mean... I could stand up a replacement service using NodeBB... How hard could it be?

famous last words