Laeserin @Laeserin - 1y
And look nostr:npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku event kinds don't have to have stupid-ass NIP names, anymore. Just have to be the right person suggesting it. Et voilà!
David @mleku - 1y
i already made such a list, even has a function to fetch the strings from the kind numbers ah, speaking of better ways of doing things aside from nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn making changes to the relay chatter that has broken its ability to fetch events from #replicatr - testing only on #nostrudel master branch modified to only talk to one relay, it's working beautifully... i can even blow events at the relay from a fresh database and go to global on nostrudel and the page keeps filling up with more and more events, it's awesome so aside from making sure the #layer2 event storage is working, i can do fun stuff now like forking all the pieces of the codebase into their own independent sections, like how khatru, eventstore and go-nostr are independent pieces with the pieces apart i want to start work on writing a full set of documentation on it which i will eventually want to share to wikifredia or at least incorporate it into what has been done like your piece there i quite like this model of owning your own version, it means that people can compete to make better versions and everyone wins
But that would result in more organic innovation and a lot of people don't want that. Everything is so commie.
I like doing it in the Nostr Wiki because that lowers the technical barrier to entry and allows us to really "own" our changes and employ WoT to order/search versions, and stuff.
i think that we are in a transition now there will be much disagreements but the best answer will win because there is no company or person or group who really can stop the bulk of interested people doing what they all think is better soon we will have several competing implementations of nostr integrated and decentralised hosted git repos too, that's gonna change the picture i say, FUCK GITHUB FUCK MICROSOFT FUCK REGISTERED CORPORATIONS! we are gonna show the internet how you do it 😎
I'm going to dig up the NIPs I've seen floating around the Wiki already, and use their njump event address as hyperlinks, instead of the GitHub URL.
You mean, you want to split your repo up into a collection of repos, like nostr:npub1s3ht77dq4zqnya8vjun5jp3p44pr794ru36d0ltxu65chljw8xjqd975wz did?
yeah, it's hard to do it when you are building the parts at the same time though... but it's pretty stable now so i can split the pieces, the nostr library is pretty much rock solid now, the relay and the event store need more work i also want to separate the different event store implementations as well, so there is the badger one, and the abstract two level one with a concrete example form using two badger eventstores behind it, and later i can adapt some of the other stuff... but i also am not sure the interface is exactly designed right because the network connection and the query logic are not really properly decoupled in the relay, it may be fixable at that level though
