Silberengel @Silberengel - 6d
nostr:npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku just realized that you're API is a substitute for the Event Publisher and Console on Nostrudel. Nice.
mleku @mleku - 6d
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
Laeserin @Laeserin - 6d
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
