silverpill
silverpill
@jfietkau Mitra doesn't support FEP-044f, only [FEP-e232](https://codeberg.org/fediverse/fep/src/branch/main/fep/e232/fep-e232.md). AFAIK Pleroma devs also don't have plans to support FEP-044f.
I think all multicodec key types should be allowed, and specification should not make any of them mandatory. But it may include descriptions of several popular key types for implementers'...
+1 for `/native` or equivalent, it would be useful for identifying native assets on chains that don't have a SLIP-44 identifier. But I think CAIP-20 should not be withdrawn, because...
FEP-521a has been finalized: https://codeberg.org/fediverse/fep/src/branch/main/fep/521a/fep-521a.md The specification on which it is based is also stable now: https://www.w3.org/TR/cid-1.0/ (it is a W3C Recommendation).
FEP-ef61 'ap' URIs also have DID authorities, and we currently don't escape them. I talked about the RFC 3986 incompatibility with ATProto people, they said the plan is to standardize...
These URIs are easier to read and easier to work with when authorities are not encoded. I don't have a strong opinion on this, but I think it would be...
This might be related to https://github.com/actix/actix-web/issues/2736 But it is not completely clear what the recommended workaround is. Perhaps actix-governor should return a response instead of an error here: https://github.com/AaronErhardt/actix-governor/blob/5c5458b8b86890dc004eb2ee944a848965735634/src/service.rs#L119?
The lack of `Actor` type was also discussed in https://github.com/w3c/activitystreams/issues/633
>we need to fix our custom activities by adding proper JSON-LD extension references via `@context` This solves the problem for JSON-LD consumers, but they are a minority, and everyone else...
>My understanding is that the established way to manage conflicting properties is to define the `@context` within the JSON object, using JSON-LD formatting. That is [what is specified in the...