with the abrupt merging of a 12 hour old pull request by @fiatjaf that removes all of the authors from the plaintext of the NIP documents, and without having given the time for all of the relevant contributors to give theri consent, or lack thereof for this change, THE NOSTR has now become a closed private larp, and there will be a fork and breakaway project. i'm not starting said project, but i predict that this will happen within 3 months. i'm also now of the opinion that every single one of those who consented this are not trustworthy individuals, and being that most of them are app developres and major relay operators, i'm abandoning this platform. the appearance of the reject by pubkey notices yesterday and the removal of the names of NIP contributors was no coincidence. there is a coordinated action going on behind the scenes and the real people in control do not want it know that there is a management team behind this project. this makes it extremely suspicious and i'm done contributing to it. my pubkey is now being purged from my storage. THE NOSTR is just X-lite.

a little tl;dr on taproot, segwit and ordinals taproot is a type of HD key scheme where you have the parent key and then a "tweak" value. a simple taproot key can have no tweak, and its derived private key is the hash of the original private key, and the public key is derived from that. a taproot key with a tweak is where you concatenate the private key with an arbitrary string of bytes, in a similar way as a HD key derivation, but of course it can be anything, even the binary bytes of a compiled ethereum solidity script. it is not material to bitcoin what you used in the tweak, it does not interpret it. it is not material to bitcoin that there is any tweak at all, this is all inside the key generation and derivation process. it took me a while to wrap my head around it, because in the code it seems like all this derivation is important, but it is not. the receiver must have the private key and the "tweak" values in order to spend the received sats. the derived private key that generated the address is not normally stored in the algorithms, but it could be. TAPROOT IS JUST A SCHNORR SIGNATURE BASED KEY. segwit, on the other hand, the cryptography of it is not so important to how it works as the fact that it allows you to make transactions with extremely large amounts of arbitrary data, after opcodes like OP_RETURN. until 2021, nobody really seriously exploited this for anything much larger than about 20kb. then someone dumped a transaction using segwit with over 30kb of data in it, some 999 signatures or something, and lightning was broken temporarily because BTCD code had put a limit, that is not specified in the segwit BIP, as a protection against resource exhaustion attacks. then the light dawned to the shitcoiner community that they could drive up bitcoain fees and clog the chain by publishing huge transactions, so tehy cooked up scamms like Ordinals, to make their justification for making transactions with ginormous amounts of data in them, and the miners of course were ok with this because during the bear markets tx volumes are thinner and the block rewards are thus lower. shitcoiners and miners are who benefit from segwit. segwit was not essential for Lightning. it just made it a bit more secure. at the time, Schnorr signatures were an option that was discussed, but it was rejected. this was the wrong decision, obviously. i don't know how bitcoin is going to recover from the spamfest that ordinals created, but please.... it's not taproot that enabled ordinals, it was segwit.

just testing to see whether the relays are rejecting my pubkey today.

i think that we will soon see the formation of islands in the nostr network. removing people's credits from nips nodes suddenly returning reject errors that seem to be blacklisting pubkeys doesn't seem very auspicious for the future of this protocol. at least not the version that is being promoted by the rockstar devs with the highest follow counts. they can't sell this thing on the basis of censorship resistance if they themselves directly start censoring keys, and removing credits from the supposedly open, democratic specification documents. ever seen that done to ISO or RFC documents?

anyone know what this is about?

GitHub

remove all NIP authors. · nostr-protocol/nips@37f6cbb

Nostr Implementation Possibilities. Contribute to nostr-protocol/nips development by creating an account on GitHub.

the nonsense today just doesn't let up. something looks a bit off about this repository to me.

censorship resistant they said.

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

CryptoHOST.org

Fast and reliable VPS store. Accepting Bitcoin, Lightning Network, Monero, Litecoin, Dash, Ethereum, TRON, Solana, Polygon, USDT, USDC and Tether

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*