arthurfranca's avatar
arthurfranca 1 year ago
I'm thinking of starting development on a new nostr web client to implement my ideas that always get bashed on the NIPs repo by the nostr gods. If you are seeing this in the middle of a million notes on a global feed and is interested in an web client that won't suck all your mobile internet plan in a day, follow me for news.. and for rants on nostr NIPs repo scene =]~. PS: any huebr there?

Replies (22)

arthurfranca's avatar
arthurfranca 1 year ago
I was thinking of lazy loading feed with manual refresh (also lazy loading threads instead of loading all thread notes at once like most clients do). No new live events until user manually refreshes.
1 replies ↓
arthurfranca's avatar
arthurfranca 1 year ago
Agree. When writing a NIP I think of implementation though its hard to spare enough time to actually implement it. Until now the way I wanted to help was just writing NIPs so others that had clients/relays would implement them instead of me. I did write some relay and client code though I need to inject some caffeine and complete the damn things.
1 replies ↓
hodlbod's avatar
hodlbod hodlbod@coracle.social 1 year ago
How many of your NIPs have been adopted and merged? I know Vitor has picked up a few, but most NIPs emerge out of developers solving their own problems, not other people offering solutions. I began my nostr journey by writing my own protocol. Fiatjaf dismissed me as an academic, until I gave up on my ivory tower and started writing real software - on nostr, because I realized I couldn't build a protocol on my own. I think he was right to do so.
1 replies ↓
arthurfranca's avatar
arthurfranca 1 year ago
I think NIP-27 and NIP-96 were very important to the protocol, although the latter was a real pain to get everybody on the same page and merge. It was also important to be there and nag about NIP-42 till @fiatjaf came up with the "CLOSED" message as a solution to most problems. I like unmerged inline metadata NIP that I think @Vitor Pamplona is still using and I will too but I guess nobody else is for now. Some things had to change on the protocol before being too late to change, even though I wasn't implementing anything at the time. I see your point though.
arthurfranca's avatar
arthurfranca 1 year ago
Not necessarily gonna pursue low-data usage at the cost of poor ux. It is more like taking advantage of knowing well how nostr works to not ship code that carelessly connect to more relays and asks more events than needed.
1 replies ↓
arthurfranca's avatar
arthurfranca 1 year ago
Time to apply all the theory learned at the University of NIPs. I completed the course with an average grade of 5.7 rounded to 6.
1 replies ↓
arthurfranca's avatar
arthurfranca 1 year ago
Great, I see you're building a web client too! Maybe If one of us manage to dethrone primal.net we can make a petition to change the nostr mascot from an ostrich to Blanka image
↑