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

Another work-in-progress preview of Akawin. This video shows how the user will be able to quickly add columns such as their timeline, notifications, and content feeds. Search and filtering will make it easy find and follow whatever you’re looking for.

https://nostr.build/av/nostr.build_d29216f951e592eb3bd51acee458e95e8be6861ca326b3558c7b8ff750f4a574.mov

Interesting. There should be a better way to make it interoperable that works for the user.

https://www.nytimes.com/2023/03/06/technology/gen-z-instagram-facebook.html

Replying to Avatar RMX

Nice✨

Thanks. A lot of work but it was worth building from ground up instead of forking an existing client.

One of the problems with invoices is that they can only be paid once. We could have a zap invoice that could be for a set amount and allow multiple people to pay it. A cross between zap (tip) and invoice (fixed amount). The payments could be public or private using Will’s spec.

🎧 "Dos Oruguitas" by Sebastián Yatra #sundayplaylist

https://tidal.com/track/204864354

Replying to Avatar PABLOF7z

Nostr connect needs broader support; check out how seenless the experience is using it on https://nostri.chat.

The fact that nostr connect doesn’t run in an extension is great because it transparently spans to non-browser apps

#[4]

Totally agree. Onboarding new users to keys and safe key management is important. Its a tough problem to solve for new users. Chrome extensions in general are hard for users and Alby is super confusing.

Nostr web apps need a good new user workflow, and short video explainers, and super simple key manager.

I like the way streaming services let you login on the tv by using a QR code and your mobile device. It needs to be super easy.

I agree. I just think it is a constant issue of people believing they’ve been censored, throttled, etc. when it’s actually a technical issue that is not understood. Either resolve the issue or explain it better to the user.

I personally think the default should be don’t show it and for those who really want to see it loads. I like how IG has an option to hides the likes to a post. If a user clicks on a post where the counter is hidden they have to count it themselves.

Yep, the issue is with the expectation created and trying to duplicate the centralized model.

Maybe we shouldn’t do that or recreate a focus on follower counts.

An idea I had for UI would be to show no counters for following and followers. If a user clicks on followers just display “Here’s a sample of 500 (or whatever ####) followers we found. Get to know them.” Show those. 🤙🏼

Not necessarily. Just as your note was likely written to multiple relays. It can build it so that there is redundancy and resiliency. There are other models for git. Replacing the collaboration and community tools of GitHub is where nostr adds value.

Another preview of Akawin … at launch users will be able to easily create custom multiple columns using keyword search and filters for specific for media links, following network, and reactions. So you could create a column for just music links shared by your friend network. Sorting, more filter, and expanded network options will be added.

Maybe some huge multinational company using his name will fund a proper museum. 😄

🙏🏼 Thanks. Very soon. The team is finishing up and we’ll launch it around the middle of the month.