taproot is nothing, it changes only a signature verification algorithm. everything else is external to bitcoin. taproot tweaks are just a way for a receiver to tag a payment inbound as being related to another thing.
segwit, on teh other hand, has provably enabled some serious bullshit that has been basically nonstop for the last year.
anyone know what this is about? https://github.com/nostr-protocol/nips/commit/37f6cbb775126b386414220f783ca0f5f85e7614
also, because you mentioned NIP-02 i went to look at the repo and found this: https://github.com/nostr-protocol/nips/commit/37f6cbb775126b386414220f783ca0f5f85e7614
the nonsense today just doesn't let up. something looks a bit off about this repository to me.
pubkey not admitted? doesn't this mean that something in the relay has blacklisted the key?
yeah it does seem like a little more info is warranted but web devs like to quit their error handling at "something went wrong" since it's assumed all users have no idea what goes on in the background.
oh yeah, it could also be my VPN. i appear to be coming from the data centre where mleku.online is also hosted. i had problems before with alby because of my vpn service with russian owned IP addresses in bulgaria and moldova.
i'm gonna hazard a guess that this is a technical glitch, possibly all those relays are on the same data centres. 500 errors mean misconfigured or broken web server/reverse proxy.
it could be technical, because i know that sooner or later relays have to start being fussy to maintain their ongoing and escalating running costs for such a poorly designed protocol.
but it could also be that i said some things that certain relay operators and their friends don't like. like what i just said in the previous paragraph is an example.
i'm just making sure that if i do get memoryholed that people know it's happening.
censorship resistant they said.
i hope to some day in the future fork and fix these projects. for now just going to chip away at it whenever it is needed.
physiological sighs are a good one too. i haven't been practising it lately, need to get back to it.
yes, i did all that because it's needed for nostr. the rest of btcd code can be avoided if nostr is your main target.
Lightning is not so easy to avoid the insanity. https://pkg.go.dev/github.com/lightningnetwork/lnd/lnwire
check the version and date on that.
they haven't fixed this, yes i filed an issue, about a year ago, and if you naively try to import lnwire, for, things ilke, you know, millisats units, hoooeeee. lol! have fun staying extremely frustrated at go mod tidy.
LND/BTCD devs need to be shamed for their terrible custodianship of the main Go codebase.
thankyou to all who zap my sometimes cranky and sometimes ridiculously rambly and often stupid posts and comments, i now have paid for my VPS hosting for my NIP-05 service for mleku.online from the romanian VPS https://cryptohost.org/ who accept lightning. so i can pay it directly in my browser via btcpay.
ah yeah, it also covers my VPN service as well. ~11500 sats for a month of their most minimal VPS, ~3.7 euro.
sheesh. today is a day of stupidity.
good thing i've got other things i should be doing *nudge nudge* *geddonwithit*
i made a few things to get around needing to import their pile of crap repository and its dependency hell at https://github.com/mleku i mean, decred. come on.
oh, an iPhone user. sorry, i don't have a cure for that disease.
Rust is promoted by Mozilla and 90% of shitcoin projects are also working with or adopting it, so that is irrelevant. not to mention what a terrible design it has for memory management, for a minimal benefit compared to Go and a huge complexity in learning compared to C++.
the btcd/lnd codebase is a mess, and an embarrassment to any competent programmer. see my previous comment regarding the state of it, and my experiences with trying to contribute to it.