Avatar
brianco
e8c1ca03a46d97184bfcd9125a5c9674a867bd1beaebe47c77d4eaec6c5ee874
permissionless product development. live and let live✌️

Akawin will be a multicolumn web client. Still working on it. We should have something to show soon. It’s all fairly basic now, but hopefully we’ll have some things of interest to contribute as we build. Our focus is on making a nostr web client that is clean, stable, and fast.

“To write Nostr applications and to use Nostr one must embrace the inherent chaos.” 🤙🏼✨

#[0]

Working on a multicolumn web client with lists. Couple more weeks.

How will option 2 work when notes get spread all over relays? Can notes and replies exist solely on a specific relay? Would it need to be a relay that has specific write/read permissions? Would a user’s profile show their full history of notes or would some be missing?

1.1.0 (2) 👀

Replying to Avatar RooSoft

Oh, you’re right…

Looking at https://github.com/nostr-protocol/nips/blob/master/09.md

The specs says: “Relays SHOULD delete or stop publishing any referenced events that have an identical id as the deletion request. Clients SHOULD hide or otherwise indicate a deletion status for referenced events.”

Maybe it should be called recall. There should be more transparency for the user about how it is handled by relays and clients.

Mashup apps and mutations that go beyond current any of the current social platforms will be one of the most interesting developments. Instant audiences for those apps will provide incentive for an ecosystem to evolve.

News organizations and publishers can escape walled garden gatekeepers and make their content available independent of a specific platform app.

Independent creators have the potential to more easily monetize their content and engagement directly.