🏷️ LabelMachine updated! @JeffG I took your great label taxonomy and implemented it in https://labelmachine.org/ I also thought it might be nice to change taxonomies, so this is also possible now. For my RDF friends npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn, @PABLOF7z, npub1dergggklka99wwrs92yz8wdjs952h2ux2ha2ed598ngwu9w7a6fsh9xzpc and @fiatjaf I added a special RDF label taxonomy 🫂 cc @arkinox npub1w80jzxf36fhwgyfp622m6s7tcl3cy5z7xva4cy75q9kwm92zm8tsclzqjv

#yondar and @arkinox trending in my feed. When #yondar dev meeting? 😀

10 years ago we started a little collective to bring #Techno music to the countryside where we are living. We were between 15-23yo. Today we own a little club, where we are going to rave tonight. Everything made and setup by our own hands. Never lent money, just good housekeeping with income of the parties we did. I'm so damn proud of all of us 🥲 #PoW

Confessions: The initial approach of https://bitcoin-library.org was not #nostr enough. Though everything was built on nostr, I did not understand nostr fully enough to built it the nostr way. It would have been hard for other clients to use the data, because it was all json-encoded stuff in some custom tag. What I was missing was #NIP-32. Nostr labels make it easy to annotate all kinds of resources and every client supporting it, can make use of the data. To experiment with labels I built https://labelmachine.org, which will supersede the bitcoin-library browser extension. I will add something like "Label Profiles" which will help the user to annotate Learning Resources, events or whatsoever. Then every other client can also use that data more easily.

Where are you discussing about labels @hodlbod, @PABLOF7z? I saw you arguing lately talking about nip-32 and talking about a rewrite. Would like to follow the discussion if you started something somewhere. Highly interested in this