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à!
Discussion
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 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 😎
#YESTR
cen.com/wp-content/uploads/2022/01/clapping-gif.gif
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'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.
programmers are terrible at documentation, it is really best if semi-technical folk do this anyway, so i'm excited to hear about this initiative
not saying programmers shouldn't learn how to write tho
I'm also just tired of the commie committee stuff, where I have to go beg people who aren't interesting in a topic and/or aren't informed of the topic and/or have me muted or ignore me, to come evaluate my proposal on a topic. Only the people who give a damn and want to talk should even be in that conversation, but all of those people should have a low barrier to entry to join the conversation or submit a counter-proposal or a new version.
Anything else is just stupid control freak bullshit.
Hey, check it out. Click on the NIP-01 link, to see how it works.
Not all of the links work, yet. I'll put in initial entries where they're missing, tomorrow, as I have to go finish something for school now.
https://wikifreedia.xyz/nip-event-register/dd664d5e4016433a8c
I meant, all of the links work, but I need to copy-paste some of the NIPs from the repo into an initial wiki entry.
nostr:npub1cpstx8lzhwctunfe80rugz5qsj9ztw8surec9j6mf8phha68dj6qhm8j5e I see you and nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft are neck-n-neck on the NIPs. 😂
🍿
nostr:npub1m3xdppkd0njmrqe2ma8a6ys39zvgp5k8u22mev8xsnqp4nh80srqhqa5sf could you do me a favor and add your zettelwiki events to the table? Want to see what it looks like when someone else edits it. Or do you have to copy it or...? No idea. 😂
oh sooooo cool that you're doing this
non-hierarchical NIPs was the germ idea that led me to make wikifreedia
my version of nostr now links to this registry
The link doesn't seem to work.
I love it how NIP-56 describes an “1984” event as “reporting” 😂
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
Yeah, tricky. We started out with one repo and now we've got like 11 and a complex build process. 😂
But it's so nifty, fr.
yeah, my code, my hosting, my neat short imports 😁
also, i very much want to separate my Go code from the rust and shitcoin stuff that is associated in the monorepo
complex build processes are not in my repertoire, i chafe and chafe and chafe until i have simplified them
i intend to make nostr clients in the future but only after i've redone a GUI DSL i made for gioui.org which i can use to literally deploy one codebase everywhere (ios, android, mac, linux, windows and web) - i have had a couple of short bursts trying to finish that job, the upstream broke my library so much but i will resume that work in the future
one language, all platforms, front and back end, compiles in 5 seconds, that is what i'm talking about, and that it isn't industry standard says that programmers like to doomscroll while they compile and get paid for it