pull down to refresh

This is worth a read. It reminds me a little of Eric Hughes' and John Perry Barlow's manifestos.

Aaaaah thank you so much man.

reply

If there is a consensus of CO2 being a problem it is for a reason. Yes. It is a big problem. This question in 2023 doesn't make sense. It is going to be worse for next generations, a massive problem and they will hate us for this. We humans knew about the problem for decades and we did nothing. Now it is too late. We must face the consequences.

We can try to mitigate it a bit, that's all. We cannot reverse it anymore at least with current technology. We needed new nuclear technology decades ago. Fusion is advancing super fast but not fast enough.

You are living a mass extinction event at high speed.
In other words. Yes. A big problem.

reply

This is brilliant. Nice [proof of] work. But your curse is that it doesn't surprise me anymore when you drop this kind of gold.

reply

SERVER(subscription) + (home)SERVER + LAPTOP(personal) + LAPTOP(dev) + TABLET(read) + PHONE(iOS) + PHONE(Graphene) = I♥️TECH

reply

The problem-behind-the-problem here is: is it possible to have the consensus defined as a written spec. This point is surprisingly controversial because, compare with e.g. internet protocols like TLS: they have a written spec to which all clients adhere. Even there, it's not cut and dried, there are lots of minor details and extensions where there at least could be a server-client mismatch and connections get dropped. But here's the difference: bitcoin's consensus requires byte-for-byte and bug-for-bug 100% compatibility between every peer, it is not a question of pairs of nodes agreeing temporarily, it is a question of every node everywhere and always agreeing. It's possible that neither written specs, no matter how thorough, nor well written code, can meet that standard (a perfect practical example is the 2013 chain split, which was not caused by any of the C++ consensus code per se, but by an unforeseen behaviour in the database software used. Not intentional but unintentional consensus dependency).

ETH from the beginning chose to base things on a written spec, and to my mind this was not wrong, but I am pessimistic that it actually changed anything. If there is an actual open-to-interpretation thing that happens, you're kind of better off having one overwhelmingly used client, as it's a de facto tiebreaker on the debatable thing. The counterargument is, if the overwhelming client has a consensus break that's clearly just an error/bug, then it's nice if there's another client everyone can switch over to as an emergency.

reply

Took almost two years from activation for taproot to gain some traction. I am only sharing because i found it interesting. I dont have any agenda. Have a nice day.

https://imgprxy.stacker.news/3Dmi85PQdhTg42fes1w8aW-cAuoLs8Xs6PBiBPFMWLY/rs:fit:600:500:0/g:no/aHR0cHM6Ly9pLmliYi5jby9jSnRDamY5L2ltYWdlLnBuZw

reply

I even tried Shazam, but it thought it was Beethoven 😂

reply

I was topping off posts to hit the nearest 69 but realized it might discourage tipping from people who don't want to ruin the number. Now I have it set to a 30-something and tip 1-5x+ depending on the joy the post brings or if I like the poster.

reply

Dropping by to say thank you @k00b for stacker.news. This community is amazing.

(Just read https://stacker.news/items/182682)

reply

Watchtower Swaps in case you're looking for a matching partner to watch each other's node: https://lightningnetwork.plus/watch_swaps

reply

Congratulations! You are going to do a great job, so don't worry to much.

Best advice (and hardest to follow) I received was this:

Let them fall down, kids bounce.

Keep them from killing or maiming themselves, but otherwise a few bruises from falling down stairs or even breaking a bone is okay.

reply