Nostr Web Client

Sometimes I fear that nostr is going to suffer death by a thousand cuts, self imposed, due to ...

- inconsistent data in relays

- improper handling of replaceable events

- ridiculously long lived caching that ignores replaceable events

- inefficient bandwidth utilization

- rush to partial implementations

We can fix this. But to do so requires staying focused on projects and features, vs abandoning them when they get 20-30% of the way there.

If someone could work on the following projects I'd appreciate it: Flockstr, NJump, Coracle.

#dev

Reply to this note

Please Login to reply.

Discussion

cloud fodder 1y ago

I been getting on the coracle train 🚂🚂🚂 choo choo baby

BITKARROT 1y ago

Nobody is working on flockstr or coracle anymore??

Nice and Kind Vic 1y ago

Zach built the initial flockstr last year. I convinced him to change the license to open source. His main focus now is flare.pub for video. The last updates in https://github.com/zmeyer44/flockstr/commits/main/ were over 2 months ago in early January.

Coracle is being worked on, but the calendar area is not. https://github.com/coracle-social/coracle. Sometimes I can only see events when I log out, and because of the inconsistencies with relays I get different results. Otherwise its filtering to just my events. Coracle default mode has poor contrast in the calendar section making it difficult to read the events.

Neither Flockstr nor Coracle calendar events understand that locations can be URIs. A minor inconvenience to users to copy them vs hyperlink.

NJUMP has massive caching problems where things dont update. Once its been cached, its stuck for months at best, or forever at worst. This is bad for all replaceables and of course kind 0.

BITKARROT 1y ago

Okay. Does this have to be done in shitty react, ugh. I’ll drop by chat sometime this weekend as i thought it was all hashed out, could def use some of these cal features myself

ᴛʜᴇ ᴅᴇᴀᴛʜ ᴏꜰ ᴍʟᴇᴋᴜ 1y ago

it also requires people starting to think about pruning back the specification because it's gotten to be quite a jungle, and not a neat garden like a protocol should be

really helps a lot when you design protocols to use a set of simple motifs repeatedly to mean the same thing in different contexts, different thing, but same intent... like nostr:npub1ye5ptcxfyyxl5vjvdjar2ua3f0hynkjzpx552mu5snj3qmx5pzjscpknpr just drew my attention to NIP-10 and how i'm supposed to add a heap of other silly things to e tags to signify a reply, and how that reply doesn't parlay to other dialectical things like kind 4 DMs

and don't get me started on the underspecification of NIP-42, and the utter crapness of NIP-44, and the how the fuck does a newbie do this of NIP-46

not to mention the lack of PROPER TITLES FOR NIPs that would help a lot - i have given these things all proper names in my nostr library because i can't stand reading codes and having to mentally translate them all the time to common terms that they should be labeled with in the first place

bevo 1y ago

Great work Vic. Thanks for all the work you do for the space. It’s greatly appreciated by all here now and the millions to follow. 💜🧡⚡️

Jeremy Almond 1y ago

Ya scaling seems problematic. I’ve tried a few different clients and every feed takes at least a few a seconds to load. Some screens will literally just hang. Worse than the early days of Twitter w/ the fail whale. Is this everyone else’s nostr experience? #asknostr

freecritter 1y ago

It’s early days. Relay configuration can help this.

Emperor Kuzco 1y ago

I use Damus on iOS running 5G and it has much better load times than Primal.

Tekkadan, ゲロゲロ! 🐸 1y ago

ChatGPT 3.5 and I will get right on that.

sperry 1y ago

did Zac bail on flockstr for ordinals, 😂