Two things that I’ve never found a satisfactory design for in #jsfs (now #fzx) are identity/authentication and federation.

I’ve designed a few identity systems that can be implemented on top of #jsfs itself (or perhaps jsfs-x) but I’ve never loved any of them, mostly due to complexity and bootstrap problems.

I’ve drawn hundreds of federation designs (and implemented a few) but they all had limitations I found unsatisfying.

As I read the ActivityPub spec this morning, I got thinking… 🧵

"As tensions with Russia and Chinese continue or worsen, demand for the F-35 will likely increase, both from countries currently acquiring the aircraft and from those that want to purchase the JSF. #Finland followed #Switzerland and Poland by choosing to buy 64 #JSFs. NATO members #Greece and the 3Czech Republic have expressed strong interest in acquiring the F-35"
#us #nato #eu #war #conflict #ukraine #weapons #poland #canada #germany #f35
https://www.19fortyfive.com/2023/01/f-35-the-worlds-best-fighter-hell-yes/

...and with that, #fzx (formerly-known as #jsfs) is running on #solarpotato

I’m having this sort of epiphany around using a non-evil CDN product to build-out global #jsfs infrastructure and set the stage for introducing it as a next-generation application platform and antidote to “Web 3”…