I'm sure this all went through each of our individual minds as "what can possibly go wrong" when the move happened and we all fell into the trap of gaslighting ourselves that this would not happen.
Strong NACK on nostr. It's a badly designed, centralized, protocol that needs a significant redesign to be usable. While off topic for this mailing list, some of its many issues include:
Reliance on single-key, cryptography that often results in people having their keys compromised. This is a serious problem in the context of bitcoin-dev, where faked messages published could easily have market-moving results.
Inability to mirror relays: since nostr deliberately ignores the lessons of blockchains, there is no way to be sure that you have a complete set of messages from a given person, for a given topic, etc.
Highly centralized design: since mirroring relays isn't reliable, in reality nostr operates in a highly centralized fashion, dependent on a tiny number of relays that can't be easily replaced if taken down.
I zapped 2,370 CCs to this post, which I think might be a bug of some kind. I did try to zap 30 sats to it, and you can see that it failed and retried multiple times until finally succeeding. But somehow it also made me spend 2,370 CCs (my entire CC balance) on it.
I'm pretty sure it's not user error, because zapping that much would have required me to long-press and enter 2,370 into the field, which I'm 100% sure I didn't do.
Leading hypothesis is that saunter's attached wallet times out slowly, and because we have network error retry logic on the client, we retry as it times out, then those retries time out, which triggers the retry again, and so on.
I've disabled the retry logic on the client for anything that costs money. We are currently trying to reproduce to confirm this is the exact issue.
Big tech's downfall could be a blessing in disguise for decentralized platforms. As they falter, the power shifts to us, those who value freedom and sovereignty.
Platforms like SN could lead the charge in a post-tech monopoly world. Curious to see if the old guard can really handle this shift. Time to take the reins, folks. Let’s disrupt the disruption. 🔥
I'm sure this all went through each of our individual minds as "what can possibly go wrong" when the move happened and we all fell into the trap of gaslighting ourselves that this would not happen.
It happened. Sovereignty is a thing.
we were all witness to it, sn has a long memory.
#307922
The abuse of the term gaslighting needs to stop. It's getting as bad as the use of the word ironic.
Ironically i agree. sorry couldn't help myself.
Eh, I'm not proud of my comment. Glad you took it well. I need breakfast I think.
Coffee is on me ❤️
Thanks, you didn't have to do that :)
Move over to SN?
Best solution
Honestly they be better off getting a territory on SN. Given enough time they could run their own instance of it too.
Academic mailing lists have traditionally always been on mailing lists.
But a fun thought experiment.
This has now been reversed, and the mailing list has been restored: https://x.com/kanzure/status/1907622313547182541
https://xcancel.com/kanzure/status/1907622313547182541
Nostr?
From @petertodd:
source
@k00b @ek
I zapped 2,370 CCs to this post, which I think might be a bug of some kind. I did try to zap 30 sats to it, and you can see that it failed and retried multiple times until finally succeeding. But somehow it also made me spend 2,370 CCs (my entire CC balance) on it.
I'm pretty sure it's not user error, because zapping that much would have required me to long-press and enter 2,370 into the field, which I'm 100% sure I didn't do.
Leading hypothesis is that saunter's attached wallet times out slowly, and because we have network error retry logic on the client, we retry as it times out, then those retries time out, which triggers the retry again, and so on.
I've disabled the retry logic on the client for anything that costs money. We are currently trying to reproduce to confirm this is the exact issue.
I'll refund all zappers on this item. Looks like saunter's wallet triggered the bug perfectly well for nearly everyone that zapped it. Me most of all.
I think you refunded me more than what was lost. I got a 9,000 refund but only lost 2,370 to this bug.
Consider it a bonus for alerting us + extra for pain and distress. :)
Like I said, u lawful bro
It hit you the most because you had the most CCs I guess
This bug affected me too. Looking into it.
It should be fixed now.
I mean, come on.... What did they expect?
Maybe time for nostr or perhaps a SN territory?
https://media.tenor.com/MldnJTRX9xIAAAAC/who-couldve-seen-that-coming-sarcastic.gif
hopefully it gets cleared up, but there must be a better solution long term.
That didn’t take long. I thought that was an odd choice.
Color us all shocked
https://media.tenor.com/SQrK5znfHqEAAAAM/omg-no.gif
https://xcancel.com/SomsenRuben/status/1907498089667059733
Big tech's downfall could be a blessing in disguise for decentralized platforms. As they falter, the power shifts to us, those who value freedom and sovereignty.
Platforms like SN could lead the charge in a post-tech monopoly world. Curious to see if the old guard can really handle this shift. Time to take the reins, folks. Let’s disrupt the disruption. 🔥