https://support.mozilla.org/en-US/questions/1121195

this issue might make me sit down and build a modified firefox with this trash disabled.

almost every time i open coracle.social after a few seconds the banner comes up and i never want to enable it.

github's support for ssh signatures is incomplete. my yubikey PV key with its *-sk suffix isn't recognised.

looks like my signatures are unverified but https://github.com/mleku.keys contains the key of the signature.

idgaf because i'm going to obsolete github just like i'm going to obsolete btcd.

this is the powah of maca and cacao

today, i was so charged up that i powered through 2 hours of making it so i can generate taproot addresses from private keys without importing btcd.

then i noticed that i could have omitted the taproot address generation function and the btcd dependency would have vanished.

i chased that thing like a hungry dog after a bone, gnawed it until it was all swallowed and then sat there grinning like a staffordshire terrier.

haha.

in the process i now have some essentials that never need btcd again:

chain configuration for mainnet, including all the official checkpoints, genesis block and its coinbase.

there is a couple of odd things in the mix that may need updating some day, but probably not, so this is one little step towards btcd elimination.

lol, i think they are for disabled folk.

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

these are maybe the prettiest things i've ever seen in my life.

currently having a minor battle with go modules.

i have pushed up a new tagged version, that appears to be in conflict with an old tagged version cached in the go centralised module cache system.

i have two options:

1. mess up my tags with another tag that is different so the module cache doesn't see the old version that is wrong

2. stop using the centralised module cache.

guess which option mleku chooses?

been working with this dude for a bit over a year now and he is a total wiz at this stuff. the size of his docker images is unbelievable.

nostr:nevent1qqs2djrs00fzcpgeczhtghcx6lxacpq795k3usp27knk58609uy6despz9mhxue69uhkumm9wd68ytnrdakj7qg4waehxw309aex2mrp0yhxgctdw4eju6t09uqsuamnwvaz7tmwdaejumr0dshsz9mhwden5te0wfjkccte9ehx7um5wghxyctwvshszyrhwden5te0vyhxummn9ekx7mp0qyt8wumn8ghj7cn9wehjumn0wd68yvfwvdhk6tcpzamhxue69uhky6t5vdhkjmn9wgh8xmmrd9skctcpz9mhxue69uhkummnw3ezuamfdejj7qgkwaehxw309apx2an09ehx7um5wgcjucm0d5hszxthwden5te0v9jjuur4wfcxcetjv4kxz7fwvdhk6tc88yrwd

beginners always have to go through a process of burning new accounts until they get the hang of a system. i have at least two ghost keys.

this is the kind of thing that we need, not yet another stupid client.

can confirm that the zap does not resolve an LNURL in any sane amount of time. pls fix nostr:nprofile1qqsvqc9nrl3thv97f5unh37yp2qgfz39hrcwpuuzedd5nsmm7arkedqpr3mhxue69uhkx6rjd9ehgurfd3kzumn0wd68yvfwvdhk6tcpzemhxue69uhksmmv09kxzmtz9ehkumrfdejj7qgswaehxw309asjumn0wvhxcmmv9ueyjx0t

fixing actual problems rather than making a bazillion new clients is what people's energy should be going towards. 👏👏👏👏👏

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.

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

that one was pretty obvious

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

i only just realised that the reason for the name 'damus' was 'nostradamus'.

should have been adamus. or just DAMMIT.

the best.

because it makes all the noisy normies stay at home and be quiet.

hopefully this means days of constant rain for us in Madeira :D

i doubt the TSA has as much business with the buses tho.