Bitcoin Dev mailing list deplatformed from Google Groups \ stacker news ~bitcoin

pull down to refresh

Bitcoin Dev mailing list deplatformed from Google Groups x.com/SomsenRuben/status/1907498089667059733

47.1k sats \ 29 comments \ @saunter 2 Apr bitcoin

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.

1000 sats \ 0 replies \ @Car 3 Apr

we were all witness to it, sn has a long memory.

#307922

100 sats \ 4 replies \ @kepford 15h

The abuse of the term gaslighting needs to stop. It's getting as bad as the use of the word ironic.

75 sats \ 3 replies \ @optimism 15h

Ironically i agree. sorry couldn't help myself.

3000 sats \ 2 replies \ @kepford 15h

Eh, I'm not proud of my comment. Glad you took it well. I need breakfast I think.

73 sats \ 1 reply \ @optimism 14h

Coffee is on me ❤️

0 sats \ 0 replies \ @kepford 14h

Thanks, you didn't have to do that :)

reply on another page

349 sats \ 4 replies \ @south_korea_ln 3 Apr

Move over to SN?

21 sats \ 0 replies \ @Car 3 Apr

Honestly they be better off getting a territory on SN. Given enough time they could run their own instance of it too.

100 sats \ 1 reply \ @SimpleStacker 3 Apr

Best solution

31 sats \ 0 replies \ @south_korea_ln 3 Apr

3 sats \ 0 replies \ @sime 20h

Academic mailing lists have traditionally always been on mailing lists.

But a fun thought experiment.

184 sats \ 1 reply \ @BitcoinIsTheFuture 3 Apr

Nostr?

270 sats \ 0 replies \ @ek 3 Apr

From @petertodd:

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.

source

21 sats \ 0 replies \ @nout 3 Apr

It should be fixed now.

110 sats \ 1 reply \ @petertodd 21h

This has now been reversed, and the mailing list has been restored: https://x.com/kanzure/status/1907622313547182541

0 sats \ 0 replies \ @nitter 21h bot

https://xcancel.com/kanzure/status/1907622313547182541

21 sats \ 0 replies \ @OT 3 Apr

I mean, come on.... What did they expect?

Maybe time for nostr or perhaps a SN territory?

100 sats \ 7 replies \ @SimpleStacker 23h

@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.

100 sats \ 5 replies \ @k00b 13h

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.

0 sats \ 4 replies \ @k00b 13h

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.

0 sats \ 2 replies \ @SimpleStacker 8h

I think you refunded me more than what was lost. I got a 9,000 refund but only lost 2,370 to this bug.

30 sats \ 1 reply \ @k00b 8h

Consider it a bonus for alerting us + extra for pain and distress. :)

0 sats \ 0 replies \ @SimpleStacker 6h

Like I said, u lawful bro

reply on another page

0 sats \ 0 replies \ @ek 13h

It hit you the most because you had the most CCs I guess

0 sats \ 0 replies \ @k00b 16h

This bug affected me too. Looking into it.

14 sats \ 0 replies \ @itsMoro 3 Apr

hopefully it gets cleared up, but there must be a better solution long term.

0 sats \ 0 replies \ @nym 15h

That didn’t take long. I thought that was an odd choice.

0 sats \ 0 replies \ @nitter 2 Apr bot

https://xcancel.com/SomsenRuben/status/1907498089667059733