pull down to refresh
72 sats \ 4 replies \ @justin_shocknet 19 Aug \ on: What creative ideas have you been rambling on? Design
Converging nostr as transport and nostr as identity together in shockwallet, we've kept social out of the equation while the transport-level protocols were iterated upon, but now the next frontier is platformization, which relies heavily on identity.
This touches a lot of stuff of course:
- Identity implies hooks into the broader network, necessitating things like an ingestor and indexers with a human readable name registry that scales
- Bridging the gap for normies whom expect to simply use an email or share identity within organization context creeps the scope substantially, ex: Sanctum.
- Conventional cloud services like CDN ex: Lightning.Video
- An integrated platform opens the doors to more demanding users, users that require traditional UX and automation that glues non-traditional components together seamlessly
This all must be done in a way that respects the constraint of self-custody and decentralization that distinguish it from yesterdays platforms. It's constrained by unique network effects that must be leveraged to bootstrap the utility. It's constrained by legacy tech stacks that are a gatekeeper to distribution. It's constrained by the fact that many ideas must be conveyed as one idea.
"Art lives on constraints and dies of freedom."
I'm surprised by the ecosystem you have been building and how you wrap it all together. One service help the other. Where CLINK fit in this ecosystem?
reply
Good question, because of I think about it in the context of the diagram, it sits almost exactly in the bullseye
CLINK, by being a lightning tool, would seem to be closer to wallet and pub... but its design and greatest strengths are how it fits into applications built around nostr identity that would be comprised of the other components.
I think of it as the glue that enables the other parts to work together
reply
I think of it as the glue that enables the other parts to work together
That's good metaphor. In this case, is SMART another product? Any ref we can learn more about?
reply
For the moment it's mostly an idea, I've got a private repo I iterate on an implementation with background cycles and see what sticks. So far it's shaping up to be an ingestor and indexer with an api layer.
It's complicated by relay subscription and connection maximums, backfilling vs. live subscriptions deltas and more... so sharding has been a fun challenge.
This is outdated, but one of the first docs I wrote on it just to gather feedback: https://github.com/shocknet/smart
reply