Why is nostr so quiet?
If you have Pixel 6 and can't wait for the rumored patch tomorrow you can instead opt-in to QPR3 Beta also with the March 2023 patch level. Read the release notes and "top open issues" to decide for yourself if it is worth being stuck in beta until June.
"March 20th" is rumored from a screenshot of a customer service rep. Even if it is made available to the public tomorrow, there there is no guarantee you'll get it immediately from OTA as providers also need to approve of updates.
The beta known bugs don't look too bad to me.
My primary concern about being stuck in the beta stream until June would be it is time consuming to apply patches multiple times per month. Otherwise I'm not too concerned about running the beta and seeing new features months before other people.
https://developer.android.com/about/versions/13/release-notes
Even if providers don't approve the OTA, you can download and sideload it.
The big question IMO is whether all 14 vulnerabilities are fixed, or only a subset...
There was no notice
No, you didn't give us time to move on. There was no notice of the close down.
You did say you might do it in the future, and I was exploring my options to move in case you decided to do so, but since I had zero notice, you deprived me of the ability to do so.
Accidental loss is one thing. Intentional violation of trust is another.
Sure. There's no perfect protocol right now. All of them have serious tradeoffs/flaws.
Actually, when I made that note, it showed me including the images at a specific position (the bottom). So IMO it's just a bug if some clients move it to the top...
So he's implying the holocaust was justified???? Not even holocaust deniers go that far, do they? Crazy
It more illustrates that NVK is not trustworthy. It's by design and well-known that Mastodon instances have a level of trust involved, and that's fine as long as your host doesn't violate that trust.
Nah, not gonna blame all nostr for NVK's rugpull, despite the sentiment I tried to express to him on how bad it was.
The bigger issue for me is the practical overhead. The machine I'm using for this right now only has 6 GB RAM (even before the hack, I didn't expose my main workstation to web stuff).
It is licensed under the MIT license terms. It is not, however, for sale, which is how they presented it. They also did not comply with the MIT license terms either.
I want to make public my concern about "NFTs" which are being sold utilizing my name. Recently, a picture of code I wrote was sold at auction for .41 BTC. It was advertised as my code in the listing and presented to the public for sale and profit. Let me be clear – I was not involved with the creation and sale of this or any other "NFTs". I have not consented to the use of my code or my name for this purpose. Instead, 3rd parties are marketing my name and my code for their own monetary gain. Worse yet – they are creating confusion in the marketplace to the extent that the auction “winner” contacted me and stated: “Think I won your auction? 😊”. Stop using my name to mislead the public so you can make a quick buck. It’s wrong.
The public should also be aware that the seller and/or auction site offered me a donation of 90% of the auction proceeds “should I choose to accept” it. I feel this is a clear attempt to: (1) bribe me into silence; and/or (2) obtain my consent after the fact. I will not accept such payment at the expense of the public who are being misled. I will not accept any such “donation”.
Due to the misrepresentation involved and actual buyer confusion, I strongly insist upon 100% of the auction proceeds to be refunded to the buyer.
I felt obligated to speak out, not just for myself, but for other Bitcoin devs who are being placed in similar situations. The amount of money we have been offered as “donations” for acquiescing to what is taking place is considerable. I do not condone it. I do not consent to the use of my name or code for this grift. I want the public to be aware of where I stand.
I want to do whatever I can do to limit the damage which will inevitably be caused by this confusing and misleading behavior.


For a second I thought you said Mel Gibson 🤣
I wouldn't assume my nsec is safe at this stage. Kinda difficult to not have it hot. It's going to take some effort to secure.
Getting closer. Once he's arrested, I can start to go into details.
NIP 57 doesn't support BOLT12 though, does it?
Last I checked BOLT12 required an experimental opt-in even from CLN?😣