Hey @rosano – before you go much further – I’m assuming you’re just “guessing” with any email-like string that ends in
@fission.codes and then popping over to Fission Auth?
Technically usernames are
@fission.name although that isn’t exposed anywhere. The “right” way to do this is to use webfinger on the domain fragment, and ask the corresponding server how to auth an ID.
That’s roughly how federation will work, although there may be some UX niceties with that.
Thinking this through some more, we might also be able to lean on IndieWeb stuff here. If I type in
email@example.com and “delegate” to Fission as
boris.fission.name, that could work too.
I looked it up, and as I suspected, remoteStorage does use Webfinger. Hmm. So, yeah, I think I can make a
.well-known on my own
bmannconsulting.com domain and just plug whatever I want in for the following values:
remotestorage I think specifies OAuth for their IETF spec, but from your POV – you just basically want a known way to say “ask Fission for auth for this user”. I’ll see about putting this on my server and we can experiment with what makes sense.
In any case – very cool to see app #2 in place here!