silverpill

I've submitted CAIP-10 spec for monero namespace: https://github.com/ChainAgnostic/namespaces/pull/86/files CAIP-10 now allows up to 128 characters in `account_address`, so we can use full Monero addresses.

I also need asset IDs in my application, but SLIP-44 based IDs are already covered by [CAIP-20](https://github.com/ChainAgnostic/CAIPs/blob/master/CAIPs/caip-20.md) and I think that is enough. Here's Monero coin, represented as [URI](https://github.com/ChainAgnostic/CAIPs/issues/67): ```...

Perhaps you can generate activities on the fly, when they are requested? Or, alternatively, save them as JSON, and automatically delete after some time. I think in practice activities need...

Still relevant. I solved a similar problem in my own software by caching all outgoing activities (they are automatically removed after several days).

Sure, this is not urgent. I just wanted to prevent stale bot from closing the issue

+1 I'm working on a non-VC application where digests will be used alongside proofs, and having `digestMultibase` in data-integrity context would be handy.

>That way we can have a 1:N relationship with accounts, allowing an account to display N proofs The relationship between actors and proof subjects (DIDs) is "many to many". Each...

Pleroma now supports quote posts as well: https://git.pleroma.social/pleroma/pleroma/-/merge_requests/3921/diffs (unreleased). They use `quoteUrl` as the default representation (for outgoing posts), but accept FEP-e232 links and other possible representations like `quoteUri`.

@aumetra Do you support actors having more than one key? For example, RSA and Ed25519. That would provide an upgrade path for Fediverse. Implementations may start generating Ed25519 keys for...

Meanwhile, FEP-c390 has been superseded by [FEP-ef61](https://codeberg.org/fediverse/fep/src/branch/main/fep/ef61/fep-ef61.md). FEP-c390 still can be useful for linking cryptographic keys to actors, but it doesn't provide data portability. That problem was solved in FEP-ef61,...