In Bluesky the app is really located on the server and the client is just a view. This is more like how traditional clould apps works as opposed to how Nostr works with its thin server and thick client.
Honestly the Nostr model is struggling. We see it with all the server stuff you need that apps like yakihonne, primal, Damus, and nos do. In order for the client to be fast, get aggregated data like reaction counts and follower calculations, most importantly notifications.
nostr:note1n6yd040m3w9lz076qmmtky504up3lt9v3ae04s6x333nvf974pmsjnsw8s
Replies (14)
Dunno... nostr:nprofile1qqs24yz8xftq8kkdf7q5yzf4v7tn2ek78v0zp2y427mj3sa7f34ggjcpzamhxue69uhhv6t5daezumn0wd68yvfwvdhk6tcpzpmhxue69uhkummnw3ezumt0d5hszrnhwden5te0dehhxtnvdakz769wywf is working quite well for me, and it doesn't need any "server stuff". 🤔
Btw, follower counts are a shitcoin... It's not important "how many" npubs follow someone, but "who" follow someone. And this is related to the viewer, of course.
Web of Trust here would be so useful.
🫂
what do you mean? nostr:nprofile1qqsraldwhvwcjgltmxwfu7kw8dqef2692yhzheuurd7k3kfy8cxjdqgpz3mhxue69uhhyetvv9ujuerpd46hxtnfduq32amnwvaz7tm9v3jkutnwdaehgu3wd3skueq93uc7e doesn’t run any special server stuff to my knowledge, just plain relays.
I believe it's spelt thicc client
I'd clarify: afaict Amethyst actually uses right now some "server stuff" for notifications, but I think nostr:nprofile1qqsyvrp9u6p0mfur9dfdru3d853tx9mdjuhkphxuxgfwmryja7zsvhqpzamhxue69uhhv6t5daezumn0wd68yvfwvdhk6tcpz9mhxue69uhkummnw3ezuamfdejj7qgswaehxw309ahx7um5wghx6mmd9u2mk7fe is looking to remove it and replace it with nostr:nprofile1qqst4dr6ttrw6s28squnwwuj5vsvsly33h7r4nsuzz3f8nf3wjsmk9cprdmhxue69uhkummnw3ezuumpw3ehgunpd35kztnrdakj7qghwaehxw309aex2mrp0yhrq7rrdpshgtnrdakj7qg4waehxw309aex2mrp0yhxgctdw4eju6t09uan9ak9 (kinda) app.
he is saying that is the problem, i still think its doable without it. we already have reaction stats in nostrdb and will have them in damus android/notedeck soon
Pokey notifications are great.
You could do intermediaries or precaching servers, but tbh there's a something nice about the way Nostr loads, it's slower not 100% accurate via time lines and content isn't delivered in specific ways.
I've honestly not thought about metrics like views, likes, zaps etc. and it's sort of freeing not to be clout chasing in that way
While I personally agree with you, I don’t think Nostr could get big like that because the masses will view it as janky and broken
nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s don’t you run a notification server that crawls the network and also one of the largest relays.
I think we need either extensions to relays or a new kind of aggregate data server in Nostr plus some changes to the nips to make changes and sets of data, etc….
i don't really need to run those, but i still think its smart to run at least one relay for your users just so you can do notifications
nostr clients are just views into the chaos, but the art lives on the canvas. pixels persist when paid, reactions just flicker.
https://ln.pixel.xx.kgYeah most won't move. People still use Facebook
If you want to get Event Counts from relays there already exist: NIP-45
https://nips.nostr.com/45In general, I'd agree with you. I prefer server side programming. and I have this type of client side... but when you start looking at authenticating with Nostr server side... its not straight forward without high level of trust. if you think of a server token without the private key, you'll need something on the client anyway. I mean, if you do make a good server side login auth system that works with the browser extension and its secure. I'll be happy to look at it and try it.
