Notices by silverpill (silverpill@mitra.social), page 65

@Hyolobrika The mentions in your post are broken, is this because of the dream you had?

@alex You may want to look at it. This is not the first time, might be a bug in Rebased or Soapbox.

@Moon @helge They could use "stars" in UI but federate Like's to make interop with other platforms easier. Maybe this incompatibility in intentional, but I don't see the point

@helge

>Powered by Forgejo

Here is the good news: the work on federation seems to be progressing

https://codeberg.org/forgejo/forgejo/pulls/1680

I'm not sure why they use Star activity instead of Like, but it's better than nothing

@teknomunk https://www.w3.org/TR/vc-data-integrity/#resource-integrity

@teknomunk If reference to media file is did:apkey URL, it can be translated similarly to object IDs.

Instead of encoding content hash directly in the URL, one can specify it in the object that represents media attachment:

@teknomunk I'm not particularly fond of IPFS either, but what are other options?

I think IPFS URIs can be useful even without IPFS node, as a more widespread alternative to urn:sha256

@tallship

gemini://git.skyjake.fi/

In markdown:

Auto-detection is not implemented because the markdown parser we are using can't be configured to detect gemini links

@teknomunk I'm currently in favor of IPFS URIs because IPFS folks made an effort to bring them to the Web (there's a browser extension that can open them, IIRC they even work in Brave browser out of the box).

@giacelvecio @tallship @evan @mikedev Oh, a post with two quotes. FEP-e232 in action

@teknomunk

DIDs are primarily for describing how to verify digital signatures.

For media you may use other kinds of URIs, for example urn:sha256 that you mentioned before, or IPFS URIs, or magnet URIs

@teknomunk

>You do something similar in FEP-ef61 with did:apkey and /.well-known/apkey except for still using the did: scheme in the field values.

Yes, with the current version of FEP-ef61 you can replace DID URLs with corresponding .well-known HTTP(S) URLs.

But I want to keep pure DIDs until I gain a better understanding of this FEP by implementing it.

>Are there any Content Addressible DIDs?

Technically did:key is content addressable :)
Maybe also did:pkh

https://misterupkeep.github.io/did-ipns-spec/

@astrojuanlu @smallcircles @FenTiger @grindhold @jrashf I think this is a good proposal https://github.com/mastodon/mastodon/issues/24079

@jenniferplusplus I don't know why the authors of MIMI decided to create a new standard. But for Fediverse the advantages of native end-to-end encryption implementation are:

1) one protocol is easier to implement than two
2) an opportunity to use MLS standard from the start

@alex The work on AP data portability is progressing steadily. You will be able to have decentralized identity and an inbox too.

More Instant Messaging Interoperability (MIMI)

https://datatracker.ietf.org/doc/draft-barnes-mimi-arch/

The architecture document describes a federated system (with clients and servers), so it is a good starting point for designing E2EE in Fediverse. The architecture also seems to be compatible with FEP-e61.

MIMI specifies its own message format, which we probably don't need because we already have one. However, it might be a good idea to copy some parts

@juanro49 No, I get "too many redirects" error

@iwojima @iwojima I tried to follow this actor and my request was successful (200). It didn't send an Accept back to me though

#Mitra v2.5.0

https://codeberg.org/silverpill/mitra/releases/tag/v2.5.0
https://codeberg.org/silverpill/mitra-web/releases/tag/v2.5.0

@Moon

https://www.w3.org/TR/activitypub/#actor-objects

>Actor objects MUST have ... outbox

@alex @mint

@alex Yes, mitra.social had incoming requests from facebookexternalua, but at some point they stopped and I can't trigger them anymore