hzrd149's avatar
hzrd149
_@hzrd149.com
npub1ye5p...knpr
JavaScript developer working on some nostr stuff - noStrudel https://nostrudel.ninja - Blossom https://github.com/hzrd149/blossom - Applesauce https://hzrd149.github.io/applesauce
hzrd149's avatar
hzrd149 1 year ago
Another small feature coming in the next version of #noStrudel image
hzrd149's avatar
hzrd149 1 year ago
I think I'm going to let myself get distracted and build a framework like this image The goal is to separate the data fetching layer ( relay subs / outbox model ) of nostr web clients with the UI layer. This might help with debugging and might make it a lot easier to build UIs since all events are stored in a single place Currently in noStrudel the events are spread across multiple "timeline loaders" and "profile loaders". this sometime leads to the UI not being able to find an event that another part of the UI was showing ( i.e. thread unable to find events shown in timelines )
hzrd149's avatar
hzrd149 1 year ago
This isn't noStrudel ๐Ÿ˜€ image
hzrd149's avatar
hzrd149 1 year ago
NIP-45 (event counts) is so powerful when you have a local relay...
hzrd149's avatar
hzrd149 1 year ago
Nearly 90% of replies to my notes are spam. kind of sucks I've been listening to everyone talk about ways to fight spam, or use the WoT to filter it out etc But because noStrudel is a web client I have very limited bandwidth and processing power, only enough to calculate WoT out 2 levels. so most spam prevention techniques would be too heavy for a web app. Plus the app would still be downloading the spam, which isn't ideal. All of this has given me an idea. What if the app worked without needing to configure any relays? ๐Ÿค” I don't think this would solve the spam issue, but it would at least show a lot less since the app wouldn't always be pulling from free relays All that said this was probably the funniest one. apparently Lyn speaks japanese image
โ†‘