mleku log, unix date 1698650570

getting back to the gitr, i am offended at the presence of decred in the go.mod indirect imports, and the presence of btcd at all, since it is the taint that brings this taint.

thus, my mission today, should i choose to accept it, is to purge btcd from signr.

this message will self destruct whenever nobody caches it.

signr_0_SHA256_SCHNORR_ce88ac2938a03c48_npub1mlekuhhxqq6p8w9x5fs469cjk3fu9zw7uptujr55zmpuhhj48u3qnwx3q5_nsig1rh2crg0gsq4lcjt2dvl9twstrnm0fst7h63cesj89xca2hjacgvd4s074uya9mq9r6rgx3sv5lmg8p35dp8ffn2k7zn3unz44hya6uq6qqe0k

Reply to this note

Please Login to reply.

Discussion

haha. nostrudel.ninja converts my npub into a link.

two quirky things in nostrudel now.

just to remind, the other feature is that for the _@domain.name as my NIP-05 specifies for mleku.online, the link it generates goes to the path https://mleku.online/.well_known/nostr.json rather than https://mleku.online which my namestr would bounce you to https://github.com/mleku

the reason for the evil taint has to do with taproot signatures.

i already started trying to pull in all the necessary things and was lazy and just copying whole sources in the chain of things but this approach quickly led to even moar evil infesting my SSD so there is going to be a more surgical approach, just to find ONLY the pieces required to access the taproot stuff. i don't need to be able to process the whole damn taproot spec just to work with the plain signatures.

also, just want to observe that within 2 levels of indirection i was bumped into imported source code from prior versions of btcd in the current version.

linking code together between two different tagged versions was NOT the intent of go modules, but unfortunately, it has enabled the growth of go modules cache to `node_modules` proportions which also means that when i tried to build some relevant thing on my tiny 7gb hdd VPS almost a gigabyte of storage was eaten by the go modules cache.

this does not happen with my work. idgaf how much fancy terabytes of SSD storage you have, poor bastards in tajikistan don't have it and that makes you an oppressor.

mission completed ser!

https://github.com/mleku/signr/blob/master/go.mod

3 new commits were required here:

https://github.com/mleku/ec/commits/master

which copied over precisely only what was required to enable the use of taproot addresses without importing btcd.

hilarious, actually, because now i go back and check the thing that pulled all this mess in, i could have removed it and not had this problem.

but now i can do taproot address generation from a nostr nsec and just add your tapscript hash to the function et voila, all without touching btcd.

this will be important later, i'm sure of it.

nostr:nevent1qqstwcfx290jj009026tmcmu20vcexdrlful6lzv24yfq3f3x97gd6spzpmhxue69uhkztnwdaejumr0dshsz9mhwden5te0vf5hgcm0d9hx2u3wwdhkx6tpdshszrnhwden5te0dehhxtnvdakz7qghwaehxw309aex2mrp0yhxummnw3ezucnpdejz7qgkwaehxw309apx2an09ehx7um5wgcjucm0d5hszxthwden5te0v9jjuur4wfcxcetjv4kxz7fwvdhk6tcprfmhxue69uhkummnw3ezuurvv43xx6rpd9hzummjvuhsz8rhwden5te0vd58y6tnw3cxjmrv9ehx7um5wgcjucm0d5hsz9thwden5te0wfjkccte9ehx7um5wghx6ef0qythwumn8ghj7un9d3shjtnyv4m8xarj9ehhyee060qmd6

signr_0_SHA256_SCHNORR_e7c96e47419b31fe_npub1mlekuhhxqq6p8w9x5fs469cjk3fu9zw7uptujr55zmpuhhj48u3qnwx3q5_nsig1yhapd4lp7jly08l28zjg9qtfxepmhl8jewh5z9t72vvhg0msqklr2k57qwc0t9760rj4pqf08pxs7un9mwpntnr5a97txl297zw9gsg0jy252