For people invested in the migration from #reddit.

marius

@silverpill so I did find it in storage, but something went wrong when dispatching it to the proper inbox. I'll create a test-case from it to check what happened. TY!

silverpill

@mariusor I tried it again today, now the server returns status 500 Internal Server Error and there's a detailed error report with these messages:

Can't save activity Follow to inbox
jsonld: error calling MarshalJSON for type *activitypub.Actor: invalid character 'h' after object key:value pair

Any ideas what might cause that?

marius

@silverpill thank you for keep trying, but this past week I've been doing a lot of reshuffling of the internals. I'm not surprised some things still fail.

Could you send me a link to a pastebin with the Activity? I'll add a bug report.

silverpill

@mariusor Sure, here is my activity

HackLiberty.org PrivateBin

Visit this link to see the note. Giving the URL to anyone allows them to access the note, too.

HackLiberty.org PrivateBin (paste.hackliberty.org)

marius

@silverpill I added a ticket here: https://todo.sr.ht/~mariusor/go-activitypub/296

I will need to create a test-case for it, but I think I have all I need.

silverpill

@mariusor I saw it had been closed and tried to send a Follow again to @[email protected]. This time there was no error, but I didn't receive Accept

Time: 2024-12-20T20:58:47+00:00

julian

@[email protected] @[email protected] apologies for butting in. I'd be interested in implementing ed25519 keys instead of RSA.

Backwards compatibility is a concern, however.

marius

@silverpill the actor received it, but on federated.id all actors are the manually confirming kind.

And as brutalinks is a little out of order, there's no way to respond outside of sending a hand crafted client to server Accept activity.

marius

@julian @silverpill I have a stupid validator that iterates through ed25519, rsa-512 and rsa-256 methods and succeeds on first.

silverpill

@julian @mariusor You can implement FEP-521a: https://codeberg.org/fediverse/fep/src/branch/main/fep/521a/fep-521a.md
The proposed solution is backwards compatible, and there are four interoperable implementations