Hacker Newsnew | past | comments | ask | show | jobs | submit | bhaak's commentslogin

> They weirdly[1] frame it around cryptocurrencies and mempools and salvaged goods or something [...]

> [1] The whole paper is a bit goofy: it has a zero-knowledge proof for a quantum circuit that will certainly be rederived and improved upon before the actual hardware to run it on will exist. They seem to believe this is about responsible disclosure, so I assume this is just physicists not being experts in our field in the same way we are not experts in theirs.

The zero-knowledge proof may come across as something of a gimmick, but two of the authors (Justin Drake and Dan Boneh) have strong ties to cryptocurrency communities, where this sort of thing is not unusual.

I also don’t think it’s particularly strange to focus on cryptocurrencies. This is one of the few domains where having access to a quantum computer ahead of others could translate directly into financial gain, so the incentive to target cryptocurrencies is quite big.

Changing the cryptographic infrastructure we rely on daily is difficult, but still easier than, for example in Bitcoin, where users would need to migrate their coins to a quantum-resistant scheme (whenever such a scheme will be implemented). Given the limited transaction throughput, migrating all vulnerable coins would take years, and even then, there would remain all those coins whose keys have been lost.

Satoshi is likely dead, incapacitated, or has lost or destroyed his keys, and thus will not be able to move his coins to safety. Even if he has still access, the movement of an estimated one million BTC, which are currently priced in by the market as to be permanently lost, would itself be a disruptive price event, regardless if done with good or bad intentions.

If you know which way the price will go (obviously way down in this case), you can always profit from such a price move, even if Satoshi's coins were blacklisted and couldn't be sold directly.


> Given the limited transaction throughput, migrating all vulnerable coins would take years ...

How? I just googled: about 55 million addresses with bitcoin in them, about 144 blocks per day, about 3000 to 5000 tx per block.

In something like 100 days all the coins would be moved to other addresses.

I gotta say it'd be hilarious if to speed up that migration-to-quantum-resistant-addresses process, the Bitcoin community were to finally allow bigger blocks.

EDIT: I take it if the network had to have full blocks for 100 days, then "shit would happens". Maybe they should force an orderly move: e.g. only addresses ending with "3a" are eligible to be moved in a block whose hash ends with an "3a", etc. to prevent congestion?


A benign use of this mode is developing on their own public repositories.

https://github.com/anthropics/claude-code


Gemini Code Assist has a free tier.

You log in with your Goggle account.


He’s talking about minifying CSS colors and I’m not sure if it is what I think it is.

Do CSS minifier really adjust the colors in the CSS files to get better compression rates or to reduce the number of rules in the CSS?


The author’s minifier now does so, yes. I think you’d have to research further to decide if they’re the first to do so or not.


It depends on the minifier (SVG optimizers do this too), but yes, they may reduce the precision of colors. I checked and esbuild will turn lab() into a hex color if possible.


Peter Thiel might be smarter than that but I’m not sure about the other ones.

Look how Musk treated the Twitter devs or Bezos any of his workers or Trump anybody.


They're all quite intelligent. And they're world class experts in saving their own bacon. Doesn't mean they have any ethics though nor any emotional intelligence after decades of being surrounded by toadies and bootlickers.


Smart is not equal to intelligent.

You can be very intelligent but have a blind eye on some trivial things.

I’m certain that some of them think they are untouchable (or even just are well prepared). We will only see if that’s really true if shit hits the fan.


We all know they have bunkers and we roughly know where they are. I got suspended on reddit for threatening harm to others for saying that a couple weeks back. But I don't think we need to raid the bunkers in your TEOTWAWKI scenario, their bodyguards will do all the heavy-lifting once they realize the power balance has shifted. But I also don't expect a SHTF scenario, just a slow creeping enshitification of living standards instead of actually implementing a UBI.

And then the survivors who band together to rebuild community instead of chasing some idiotic Mad Max scenario will ultimately prevail. And yes, they are blind to that other option because they wouldn't end up on top.


That's a general problem with procedurally generated content.

Remember that wave function collapse focuses on local optimization. The algorithm can’t take a step back and look at the whole map. That’s why you won’t get a sensible road network. Rivers are only slightly better when the follow height gradients.

What you can do, and this is also a general advice for procgen, is to mix in some templates before WCF runs. Often, a bit of post-processing is needed as well.

The templates can be hand-designed, or generated with simpler procgen code. Place a few towns on the map, connect them with roads, and then let WFC fill in the gaps to create a more interesting landscape.


Which is based on the board game of the same name.

https://boardgamegeek.com/boardgame/370591/dorfromantik-the-...


The other way around.


Oh, wow, TIL. Both were released in 2022 but the video game already had an alpha release in 2021.


I‘m pretty happy with a self hosted Joplin.

Markdown, cross platform and good support for todo lists.


Joplin is quite good; I still keep it around for longer form writing. For everyday note taking I switched to logseq about a year ago. They're in a weird phase technically (in tye midst of a huge rewrite id the persistence layer) but it’s the first PKM app I’ve used that I’ve really gelled with.


If you just commit AI generated code without even looking at it it doesn't matter how many years of engineering experience you have.


A competing format that is understandable to probably everybody.

An ISO 8601 date is also comprehensible to anybody even if they never seen it before and have to figure it out themselves.



I said date. Not time, not timestamp, not period, not week, not range, not ordinal date.

Just date.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: