> 1. Used the public reconstruction to obtain the recovered RTL/constraint structure, including the 11×11 region map and the fact that it is a two-stars-per-row/column/region, non-touching puzzle.
> 2. Then independently wrote and ran my own exhaustive solver against that recovered constraint system.
Looks like it did not actually solve it, but instead it just found an existing solution at https://github.com/NotCleo/GDS-to-RTL and verified parts of it?
I have no doubt that modern agents can solve challenges like this even without external help, but you should at least briefly look at the output before posting it online!
Nothing to understand. Straight up hallucination. I could have sworn I read that they used a novel architecture where the model is dense but you could select specific layers or something at inference. reread the announcement: just said MoE. Corrected my brain's weights so thanks.
It's a spectrum. I don't think that they will be able to sell t-shirts using a drawing you've uploaded. But it will probably allow them to defend themselves a bit better if they get sued for selling the data for LLM training.
Quoting just one of the smallest one feels a bit... charged. There's small tradeoffs among all of them when you account for weight.
For everyone else here's the full list:
Switch 2
Battery capacity: 5172mAh, approximately 1% smaller than current version (5220mAh)
Weight: Approximately 411g, around 10g heavier than current version
With Joy-Con 2 controllers attached: Approximately 548g, around 14g heavier than current version (approximately 534g).
JoyCon 2:
Battery capacity: No change.
Weight: each 2g heavier
Switch 2 Pro Controller:
Battery capacity: 897mAh, approximately 16% smaller than current version (1070mAh).
Weight: Approximately 228g, around 7g lighter than current version (approximately 235g).
N64 Controller:
Battery capacity: No change.
Weight: Approximately 234g, around 1g heavier than current version (approximately 233g)
GameCube controller:
Battery capacity: 525mAh, approximately 5% larger than current version (500mAh).
Weight: 215g, around 5g heavier than current version (210g).
Sorry I should have specified that is the pro controller, typical use case is a docked switch and the controller is used while on a couch or some such.
Literally the worst case scenario for dramatic reduction in battery life.
The console one seems the only relevant one. I'm a casual gamer, but the joycon running out of battery doesn't feel that annoying to me. That 16% has a much smaller impact on the JoyCon than on the main device.
Odd take. 99.99999% of citizens will never travel to China, so it matters not that the Chinese govt holds their data.
A local company losing the data screws everyone. Palantir getting the data screws everyone, because while foreign, that data will eventually be fed into global systems like VISA, Mastercard, etc, and affect your travel in numerous countries that will be outsourcing their systems to Palantir.
I'm not sure what "travel" even does here. Possessing citizen's info opens possibilities for influence ops, blackmailing, unfair advantage in business and much more. And non-democratic countries are always better at these games, cause they need not be afraid of the next government leaking, investigating, selling whatever they did.
Meanwhile gov't losing info on one citizen screws said citizen, but losing all of it screws the gov't itself, and generally rebalances power in favor of citizens. Which one may say isn't bad.
You can't predict the future. By your own reasoning, you can't say with any degree of certainty that it will never matter if China has a citizen's data just because that person will never travel there.
> Worked for 12m 36s
> Solved
https://chatgpt.com/s/t_6a9aed0b09988191b0f2850dee056b48
Edit: It didn't independently solve it.
> 1. Used the public reconstruction to obtain the recovered RTL/constraint structure, including the 11×11 region map and the fact that it is a two-stars-per-row/column/region, non-touching puzzle.
> 2. Then independently wrote and ran my own exhaustive solver against that recovered constraint system.
reply