Can't we come up with puzzles where at least something of value is created when the puzzle is solved (and a tremendous amount of resources is not wasted)?
The use of the word “we” is curious. You didn’t come up with the puzzle, you didn’t “waste” the resources. The purpose of the we is to appoint yourself judge and arbiter and to steal yourself into the in-group. Just post your judgement: you don’t like that someone else did something you don’t like with their resources.
At the risk of sounding snarky: It wasn’t. It does however, answer the question. “We” do not need to change our allocation strategy whatsoever because “we” didn’t allocate any resources towards this and “we” aren’t the arbiter of what others can or cannot do with their resources.
We can and do, all the time. And all puzzles are a "waste of resources", really.
I'm not into crypto and I do think Bitcoin is stupid and wasteful, but I don't find it "sick" or all what upsetting that this kind of puzzle exists, though I think some smart contract-based Ethereum puzzles could be much more interesting, demanding solutions to more interesting problems that don't directly relate to the blockchain itself. Imagine a smart contract with a pot anybody can pay into that pays out to whoever could crack a particular previously unsolvable problem. Basically a public bounty. The only downside is that it has to be a problem that can be validated algorithmically.
Why should “we”? You can hear “we should/must” from all corners here but then remember it’s an US start-up’ers forum with people who plan morning meetings for email regexps.
Bitcoin may be an inefficiency, but is it the? Most everyday things modern first-world people do are equivalent to burning oil and shredding trees for little to no reason. You just can’t see it as clearly as in PoW crypto.
> puzzles where at least something of value is created when the puzzle is solved
What puzzles create something of value when they're solved today? A puzzle is typically a thing you do for fun and entertainment, not something you try to solve for the purpose of creating value.
I guess you're thinking more about logic/mathematical puzzles and alike? Would make sense in that case, but that's not the only type of puzzle.
That wouldn't be a puzzle, then. It would some kind of engineering challenge. A puzzle starts by knowing the answer and then putting some circuitous path between it and the player, that they have to figure out how to navigate. It's inherently wasteful to construct puzzles.
The sibling comments are all correct that you're special-pleading the criterion that a puzzle create something of value.
But, as it happens, this one does: it offers economic incentive to develop more efficient attacks on elliptic curves. The curve Bitcoin uses isn't widely used outside of it, but that doesn't mean that an efficient attack on Secp256k1 wouldn't apply elsewhere.
Is this modest as positive externalities go? Probably yes. Could someone with a better attack on the curve just empty wallets? Not necessarily, and probably not: the point of the puzzle is that the entropy has been deliberately reduced to make it crackable with brute force, so, say someone worked out a factor of four improvement: that isn't going to get you into the Genesis Wallet, but it substantially lowers the price of claiming some of the puzzles.
Also, being a cryptographer and being a thief are unrelated professions. Some people might be inclined to both, but I would guess that most are not.
What's missing a bit here is debugging and tuning for >100 Gbps throughput. Serving HTTP at that scale often requires kTLS because the first bottleneck that appears is memory bandwidth. Tools like AMD μProf are very helpful for debugging this. eBPF-based continuous profiling is also helpful to understand exactly what's happening in the kernel and user-space. But overall, a good read!
While the article provides guidance on utilizing standard software and services to construct a basic video upload platform, it lacks deeper insights into advanced scaling techniques.
Is there already a ChatGPT Plugin out to summarise blog posts?
tl/dr: "The key message in this text is a call for accountability following the decision to downgrade JeanHeyd Meneide from keynote speaker at RustConf due to disagreements with his blog post. The decision was perceived as disrespectful and cruel, lacking in appropriate organizational procedures. This has highlighted a larger systemic problem within the Rust organization and prompted the author's resignation. They call for a full investigation, a greater focus on accountability rather than diplomacy, protection of individuals from such unjust actions, and the implementation of safeguards to prevent similar incidents in the future."
The claim made at the time was that the titles were not from other people and were in fact caused by the model hallucinating after the input query timed out (or something like that). Obviously that sounds a little suspect now, but it might be true.
That's a lie if so, if you look at the Reddit threads there's no way those were not specific other users histories as they had the logical history of reading browser history. Eg, one I saw had stuff like "what is X", then the next would be "How to X" or something. Some were all in Japanese, others all in Chinese. If it was random you wouldn't see clear logical consistency across the list.
I have reviewed the logs for our video CDN and out of 150,000 sessions, only 48 were identified to be using IPv6. These sessions were identified by the user-agent Roku/DVP-12.0 (12.0.0.xxxx-xx), indicating that the recent update to the operating system now supports IPv6.
I wonder if it's just a bunch of old and outdated Roku boxes causing problems? They probably work off of a ~3-5 year support cycle like phones but are updated even more infrequently by endusers (why should they if it's still working for them?).
I have a Roku 3 (these came out in 2013) which I regularly update. The support cycle is fairly long. I think they did stop supporting some Roku 2s at one point due to a new feature the old hardware just couldn't support.
