ssb-ngi-pointer/a2a-spec-archived

https://ssb-ngi-pointer.github.io/a2a-spec/

a2a-spec-archived's Issues

Migration

I think the migration needs an ack after main feed messages and before delete. This should only be sent once the receiving end has properly stored messages on disc.

OS assigning a default app for SSB URIs

There's a problem with this spec that may be a deal breaker.

Say you install app X which handles SSB URIs, and so far it's the only app in the OS that supports SSB URIs. You click a few SSB URIs and the OS automatically opens app A and somehow it becomes the default app for this URI scheme. (Operating systems have slight differences in how they treat this)

Then you install app Y which also handles SSB URIs, and you would like to do A2A rendezvous starting in app X, which means that X displays the SSB URI button, and you click it, expecting that it would open a popup asking you whether you want to go to app X or Y, but actually it would just handle the SSB URI in app X, because that's the default handler for this URI scheme.

Before implementing A2A, we should make proof of concepts and test out it would work in the following operating systems:

• iOS
• Android
• Linux
• macOS
• Windows