pull down to refresh

Lightning is Broken AF (But We Can Fix It) - Matt Corallowww.youtube.com/watch?v=s9KMRWkcwtE
2172 sats \ 23 comments \ @TonyGiorgio 7 Nov 2022 bitcoin
write
preview
related posts
10.6k sats \ 9 replies \ @tomlaies 7 Nov 2022

Can somebody give a tldrP

Edit: I think this comment got submitted several times which did cost 10k sasts. I think this is a serious bug if someone had more money on this account @k00b

reply
574 sats \ 2 replies \ @TonyGiorgio OP 7 Nov 2022

The TLDR is that there are some serious bugs for anyone that has a lot of money

reply
100 sats \ 0 replies \ @faithandcredit 8 Nov 2022

Funny how your comment applies to the tldr of the speech but also to the bug on sn that is now fixed

reply
0 sats \ 0 replies \ @kilianbuhn 8 Nov 2022

Simultanously we say that Lightning sucks for everyone WITHOUT a lot of money since the only channels that matter are big channels & thus a lot of channels cost a lot of money.

What is it then? For the rich it sucks or for the poors it sucks?

reply
150 sats \ 3 replies \ @k00b 7 Nov 2022

Sorry, I need to disable retries on mutations. This is a bug created by the DB being "overloaded" following an update yesterday.

I'll fix asap.

reply
151 sats \ 2 replies \ @k00b 7 Nov 2022

Fixed.

  1. the db issue
  2. we no longer retry automatically

Sorry again

reply
0 sats \ 1 reply \ @tomlaies 8 Nov 2022

Thanks for the sats back!

I was thinking if it could have been my keyboard/pc getting stuck. I've been thinking about it all day ...

  • Maybe there should be a timeout period between answering the same post. On the other hand the increasing prices are meant to avoid exactly that.
  • Another possibility would be to disallow empty comments or the same text twice (could even be handled in frontend only). But idk...
reply
3 sats \ 0 replies \ @k00b 8 Nov 2022

Afaict this wouldn't happen due to a stuck key. On clientside we synchronously disable the button, submit, and then clear the form.

reply
101 sats \ 1 reply \ @k00b 11 Nov 2022

This video is more or less a diff between what lightning is ideally and what it is today.

  1. nodes need to be online, so UX sucks on mobile-like devices
  2. watchtowers don't "watch" HTLCs for privacy reasons
  3. dispute txs are subject to mempool pinning attacks
  4. payment routing is hard mostly because channel balances are unknown and vary
  5. it's pretty nuanced, but lightning isn't very private in many dimensions
  6. channel jamming is a thing
reply
135 sats \ 0 replies \ @TonyGiorgio OP 11 Nov 2022

Yeah I think that pretty much covers it. Coupled with "and don't really trust just anyone to be your counterparty here"

reply
575 sats \ 0 replies \ @TonyGiorgio OP 7 Nov 2022

Probably the best talk that I saw at TABConf. Such a mic drop moment.

reply
560 sats \ 3 replies \ @thrown 7 Nov 2022

Privacy section starts at 34:43

reply
0 sats \ 2 replies \ @thrown 8 Nov 2022

It doesn’t look good Lightning Bros…

reply
2 sats \ 1 reply \ @shyfire 8 Nov 2022

This statement won't age well ;-)

reply
0 sats \ 0 replies \ @thrown 8 Nov 2022

i hope!!

reply
20 sats \ 0 replies \ @cokyjgz 7 Nov 2022

Very interesting
Thanks for sharing

reply
10 sats \ 0 replies \ @tomlaies 7 Nov 2022

Can somebody give a tldrP

reply
0 sats \ 0 replies \ @BITCOIN_CEO 8 Nov 2022

cba to watch, potato ass microphone quality

reply
0 sats \ 0 replies \ @someway09 8 Nov 2022 freebie

Oh wow

0 sats \ 0 replies \ @tomlaies 7 Nov 2022

Can somebody give a tldrP

reply
0 sats \ 0 replies \ @tomlaies 7 Nov 2022

Can somebody give a tldrP

reply
0 sats \ 0 replies \ @tomlaies 7 Nov 2022

Can somebody give a tldrP

reply
0 sats \ 0 replies \ @NorthKoreanHostage 7 Nov 2022

Can we just put this guy in charge of all the important stuff?

reply