Also, Wikifreedia.
Oh well.
Sad to see that nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft and nostr:npub107jk7htfv243u0x5ynn43scq9wrxtaasmrwwa8lfu2ydwag6cx2quqncxg have deserted highlighter.com and habla.news
They held out so much promise
It’s back to Substack, I guess
#grownostr #plebchain
Discussion
Nostr is dying
Ha ha. Nah. Pablo has always been a release-and-abandon dev and the other guy is focusing on Chachi.
Just too many people working alone, so maintenance suffers. Same problem with Nostrudel and Jumble and etc.
I’m very surprised that they’d let great projects like habla.news and highlighter.com fade away 😒
They don't get paid to maintain things, they get paid to build new things.
Super lame 😒
Well at least Damus, Amethyst, and Primal are doing fine so far
Why is everyone so hung up on Nostrudel? Because it’s a desktop client?
The best threading and has lots of nifty tools.
Lol 😂
Only you dev / tech types seem to fuss over it
Us noobs are happy with Da-Moose
nostr:npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku just realized that you're API is a substitute for the Event Publisher and Console on Nostrudel. Nice.
I get FOMO about Nostrudel when you techies talk all this gobbledygook
But I think it’s a web only client 🤔
I use web clients on mobile.
Like a PWA?
I just use the browser, but it works as a PWA, as well, I think.
PWA just means the code to run the page is only loaded once, that's where stuff like nostrudel has that popup at the top of the page saying it's been updated so you load the new one
it means the page is an app, itself, and it never fetches the file containing the document again, it only fetches data to change the rendering
yes, it is that :)
but what's hilarious is you know that this swagger/openapi tech has been around over 15 years but all of nostr invents new broken versions of everything
also, because they didn't fund me to do their savet work on the relay i ended up having to learn how to do APIs properly and my current project this smarty pants vietnamese dude has this javascript database API like this and he had some library that let him just dynamically specify it and after some time searching i finally found out i can do the same thing and now i'm getting very soaked in HTTP tech and it all looks rather familiar in ways that are disturbing
disturbing because why was it not built this way in the first place
also i kinda know why... websockets and json are kinda like mainstream of Go dev
but they are kinda hated at the same time, that's why protobuf is now more popular for APIs but for web apps openapi is the way, just that it seems that it's taking quite some time for people to find huma
i guess it's that old trending algorithm problem on github instead of primal lol
Necessity is the mother of invention. I needed it built, so you built it, and now it exists. 🤷♀️
i knew it had to be built because i had such an atrocious experience with trying to implement the existing protocol as it is specified
it's really really complicated and basically the guys who made the first versions don't see the problem because they are past that hill, but because they don't listen to people who are trying to walk that path having problems on the road they are going to lose control of the protocol because the reasons for the lack of proliferation partly relates to the high cost of implementation due to the ridiculous vagueness of the spec
