For people invested in the migration from #reddit.

marius

@silverpill yep. Another one of those small frictions with Mastodon, that doesn't support EC keys.

silverpill

@mariusor Interesting. I'll update my server to accept PEM-encoded ed25519 keys. Do you know any other Fediverse software that supports EC keys?

I'm currently writing a FEP with a related topic: https://codeberg.org/fediverse/fep/pulls/105/files. In this proposal, a different property is used to ensure compatibility with existing services.

marius

> Do you know any other Fediverse software that supports EC keys?

@silverpill no, not on the top of my head. I think everyone should support it at least on the basis of much smaller size though.

And, as always when it comes to interop, crickets from the Mastodon devs: https://github.com/mastodon/mastodon/issues/21429#issuecomment-1549405785

silverpill

@mariusor I sent a follow request to @marius, but haven't received an Accept activity yet. Something is wrong?

Delivery time is 2023-06-13T16:57:12Z

marius

@silverpill federated.id doesn't accept follows automatically. It's in my inbox.

@marius

marius

@silverpill I guess this one wasn't you. The time is different.

It means your follow didn't make it to my inbox. What client/service did you sent it from?

silverpill

@mariusor I sent it from this account.
The server is running Mitra, it's the software I'm developing.

marius

@silverpill if you could provide me with a verbatim request (including the sign header) I could try to see what's wrong. The strange part is that there's nothing in the logs for that specific period, not even at the http proxy level.

silverpill

@mariusor I can't provide the full request, but I could say that it had RSA HTTP signature attached.

The inbox was https://federated.id/actors/8b740680-ccb4-4265-82e7-4ac2ca402750/inbox
And the response was 201 Created with empty body.

Here is my unsigned Follow activity:

{"@context":["https://www.w3.org/ns/activitystreams","https://w3id.org/security/
v1","https://w3id.org/security/data-integrity/v1",{"MitraJcsRsaSignature2022":"mitra:MitraJcsRsaSignature2022","mitra":"http://jsonld.mitra.social#","proofPurpose":"sec:pr
oofPurpose","proofValue":"sec:proofValue","sensitive":"as:sensitive","verificationMethod":"sec:verificationMethod"}],"actor":"https://mitra.social/users/silverpill","id":"
https://mitra.social/objects/0188b5b0-829e-aadd-be8d-a5f484fceb34","object":"https://federated.id/actors/8b740680-ccb4-4265-82e7-4ac2ca402750","to":["https://federated.id/
actors/8b740680-ccb4-4265-82e7-4ac2ca402750"],"type":"Follow"}

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