@silverpill
Developer of ActivityPub-based micro-blogging and content subscription platform Mitra. Working on Fediverse standards: https://codeberg.org/silverpill/feps
Relays (1)
- wss://relay.ditto.pub – read & write
Recent Notes
I don't know, does it create problems for NodeInfo clients?
The additional relation type in this JRD was introduced in FEP-2677: Identifying the Application Actor. As far as I can tell, adding links is not against NodeInfo protocol specification, but if additional links cause issues, we can discourage that practice in FEP-0151.
The additional relation type in this JRD was introduced in FEP-2677: Identifying the Application Actor. As far as I can tell, adding links is not against NodeInfo protocol specification, but if additional links cause issues, we can discourage that practice in FEP-0151.
is that the reason mastodon & friends used it at first?
Ed25519 is a newer crypto, EdDSA was first mentioned in draft-cavage-http-signatures-11, 2019. As far as I know, ActivityPub servers were already using RSA at that time.
Mastodon got a working implementation of a thread collection (context). I'm adding it to the list of implementations in FEP-f228: https://codeberg.org/fediverse/fep/pulls/745
#fep_f228
RE: https://mastodon.social/users/MastodonEngineering/statuses/115854312836282687
@nevent1qy2...
#fep_f228
RE: https://mastodon.social/users/MastodonEngineering/statuses/115854312836282687
@nevent1qy2...
@nprofile1q... Yes, I can see it too
@nprofile1q... Yes!
+1 for writing a FEP, I would contribute to that effort
require ed25519, recommend rsa-v1_5_sha256
I think it should be the other way around: require rsa-v1_5_sha256, recommend ed25519. Since RSA is already used, implementers can start with RFC-9421 and add support for ed25519 later.
As far as I know, Mastodon and WordPress implemented RFC-9421 but not ed25519.
tootik
It's developed by @nprofile1q... (he's on a tootik instance, you can test your implementation there)
require ed25519, recommend rsa-v1_5_sha256
I think it should be the other way around: require rsa-v1_5_sha256, recommend ed25519. Since RSA is already used, implementers can start with RFC-9421 and add support for ed25519 later.
As far as I know, Mastodon and WordPress implemented RFC-9421 but not ed25519.
tootik
It's developed by @nprofile1q... (he's on a tootik instance, you can test your implementation there)
@nprofile1q... @nprofile1q... This is not possible directly in Mitra, but you can follow hashtags on FediBuzz relay: https://relay.fedi.buzz/
@nprofile1q... @nprofile1q... There is already a lot of overlap between different platforms. They are mostly differentiated by how default client looks.
@nprofile1q... Maybe. Did you encounter this error when processing a post or a profile?
I'd like to try to do it on my instance
I'd like to try to do it on my instance
@nprofile1q... This is actually a bug on their side, because ActivityPub IDs are supposed to be URIs, meaning that they can't contain non-ascii characters.
It was fixed, though: https://akkoma.dev/AkkomaGang/akkoma/issues/820
Perhaps this instance runs an old version of Akkoma?
It was fixed, though: https://akkoma.dev/AkkomaGang/akkoma/issues/820
Perhaps this instance runs an old version of Akkoma?
@nprofile1q... Interesting, what do you need it for?
@nprofile1q... I think this could be changed with a custom theme. It's not difficult: https://codeberg.org/silverpill/mitra/src/branch/main/docs/custom_themes.md. Do you want me to add a CSS variable for avatar roundness?