I was wondering how they were able to add a description, which isn’t usually possible for link submissions.
2,699 karma · joined March 20, 2013
I was wondering how they were able to add a description, which isn’t usually possible for link submissions.
Manning has a decent solution to this. You can browse the entire book, but only a small section of it at a time is “descrambled” in the live view.
On more than one occasion I’ve used this to look up some specific topic, which was immediately viewable (and unblocked me on that problem), then gone on to purchase the book because I know it’s high quality and I’m likely to refer to it in the future for other reasons.
Every LN transaction is literally a bitcoin transaction. Usually these are not broadcast to peers for settlement on the base layer, but the latest transaction always can be broadcast, just like any other Bitcoin transaction.
I don’t follow other L2s closely, so maybe this differs from Ethereum and its derivatives. But the Bitcoin Lightning Network is 100% Bitcoin.
If I hand you a paper bitcoin wallet worth a certain amount of satoshis, that’s still bitcoin. You rightly shouldn’t accept it because I know the private key and could rugpull those funds from your control. If there were cryptographic assurance to prevent that rugpull, owning that key becomes as valuable as the underlying asset.
Your flawed explanation is like saying the dollars spent on a Visa card aren’t using US currency because the transaction isn’t immediately settled in the eyes of central banks.
Edit: To be clear, there’s no credit involved in the LN transaction. I only used the analogy as a layman’s example. All LN transactions are fully collateralized and can be settled to the base layer at any time by either participant.
Your initial description seems accurate, but then you erroneously claim this has nothing to do with bitcoin.
Please explain how the Lightning Network loses most of the benefits of Bitcoin.
You have misunderstood since the beginning, because this is how it’s worked since the initial spec was proposed in 2015, years before it was actually implemented.
Here’s a book you may find informative: https://github.com/lnbook/lnbook
The Lightning Network literally consists of Bitcoin transactions.
There are custodial solutions that serve each layer, but that’s orthogonal to the network itself.
The Fed is trying to stop them at all costs.
Bitcoin already has second layers: the Lightning Network, Stacks, and bridges to other blockchain systems.
A silent drone could be much creepier...
I’ve been using i3 (w/gnome integration) on Silverblue, so I’m wondering how this will compare.
BFR was the code-name for Starship, short for Big Falcon Rocket
https://en.m.wikipedia.org/wiki/SpaceX_Starship_development#...
For the strongest guarantee of non-repudiation, there’s OpenTimestamps:
https://github.com/nostr-protocol/nips/blob/7d792055372ce1af...
Then clients and relays SHOULD act as if the referenced event is deleted. This is different than MUST, probably because there’s no way to guarantee it happens. It’s also possible the delete event doesn’t make it to everywhere that received the initial event.
https://audiveris.github.io/audiveris/_pages/handbook/
I haven’t tried it but my first thought was to use something like tesseract OCR, and I found this optical music recognition (OMR) project from there.
Flatpak is the preferred app packaging format, and Endless maintains its own collection of curated apps in the App Center.
I think it’s straightforward to install anything from Flathub as well, but it’s been a while since I last checked.
Thema is mentioned there, as “the presumed successor to grafonnet,” but that hasn’t officially been confirmed and it sounds like bigger changes might be underway. Discussions are also happening elsewhere, like their Slack, but that link is the most complete overview I’ve found.
In some of the discussions where the community is trying to figure out how to future-proof current dashboard definitions, Grafana Labs has also recommended this Python tool (unofficially I suppose) by Weaveworks, called grafanalib: https://github.com/weaveworks/grafanalib
You make such a great point that I’m going to rename it: paradox
Thank you, Lithium!