Post

Zicklag
@zicklag.dev

I feel like space:// is a little too generic. Feels like we need the "at" in there somewhere. What about pat:// "permissioned authenticated transfer"?

0 reposts12 likes

daniel holmgren 🫠
@dholms.at

makes me think of the test i had to take in highschool lol hmmm "at" is so *slick*. and "space" gives me a similar feeling. tacking on letters onto "at" just feels a little clunky to me. i like psat/sat over pat fwiw

Paul Rohr
@pevohr.bsky.social

In your model, spaces are permissioned by definition, so only of those two words is necessary If "pat = permissioned authenticated transfer" is too stuttery for you, then definitely "sat" over "psat"

Paul Rohr@pevohr.bsky.social

Or "sat://" for "space-authenticated transfer" Also works as an in-joke for protocol nerds by evoking the differences between ftp vs. sftp vs. ftps

Paul Rohr
@pevohr.bsky.social

For something slicker, consider: "st" = space transfer, or "ps" = permissioned sync Both backronyms would actually convey something about what this protocol variant does that at:// doesn't Is it still a general-purpose transfer mechanism (like at), or a more narrowly-designed sync mechanism?

Tristie@tristie.org

I vote st:// for the AT space uri scheme because when i think of spaces I think of gathering locations, which a street is. st also doubles as a TLD which benefitted at:// and also it would give us even more metaphors than simply the atmosphere/sky.. such as neighborhoods & gated communities