I dream of an open board like the yubikey nano. This is very nice!

A founder I know is making reduced-pin Arm-based prototyping modules: https://www.bergsonne.io/

They're seriously tiny; basically answering the question, "What if mechatronic prototypes didn't need to be the size of an Altoids tin?"

While this looks novel, I don't quite get the expected usage pattern? Those boards don't seem any more easy to solder to than the chip itself

If you are talking about USB-A Nanos, there is https://tomu.im/, which is very nice and interesting.

I’m very familiar, we made Somu :) I meant USB-C.

Try a prompt that helps claude iterate until it can verify the result.

For example, if you tell it to compile and run tests, you should never be in a situation with syntax errors.

But if you don’t give a prompt that allows to validate the result, then it’s going to get you whatever.

Has anyone tried to "turn off some cores" (eg using multi-instance gpu feature) and see if/how that increases reliability?

If you have the opportunity, try out a zen5. Significant improvements.

See also https://www.numberworld.org/blogs/2024_8_7_zen5_avx512_teard...

Cool demo, but this is only log2(43 quintillions) = 65 bit security.

Kind of related is DiceKeys, with 192 bit security: https://www.crowdsupply.com/dicekeys/dicekeys

192 bits?

I must be missing something here, there are 25 unique dice that can be permuted, each can have six potential sides showing, and 4 potential orientations of the displayed face... So (25!)×(25×6×4) ? Isn't that more like only 93 bits?

Well obviously harder to scan from a phone, I think a deck of playing cards would be easier to acquire and store. Shuffling 27 would give you 93 bits, shuffling the full 52 would be ~226.

It’s explained in the link. I actually misremembered, it’s 196 bits.

Never mind, with the benefit if sleep I see an error in my math.

Still, I wonder if a similar thing could be done by shuffling a deck of cards, and then riffling the results past a good camera so that an app can recognize the sequence in order. Perhaps it would be vulnerable to common shuffling mistakes?

It's pretty upfront about being a novelty project done by a self-described non-crypto expert, and I don't see any assertions of it guaranteeing any degree of sufficiency/security or claiming any such NextBigThing(TM) hype.

Just because a paper is published doesn't mean it wasn't done for fun/the hell of it.

Yeah this is bang on. I messaged my old supervisor from uni about turning CubeAuthn into a paper and she suggested I submit the paper to that conf.

Link to Vitalik's post would be preferable, context is important.

As far as I can tell, it was something he said in his devconnect address, for which no video appears to be available yet.

Part 2: https://chillphysicsenjoyer.substack.com/p/my-uv-experiment-...

A robot that folds laundry.

Check this out. https://www.youtube.com/watch?v=HOoRnv3lA0k&t=1s

A couple suggestions:

1. Pay attention to the first 2-3 columns, the ones the user immediately sees. E.g. short or hidden id, short but readable name, useful next column (e.g. sales or views or whatever is the most useful data).

2. Put columns that need to be evaluated together close to each other. On desktop it's easy to see 2 numbers even if there's a column in the middle, on mobile it may require scrolling horizontally.

In summary, just focus on what people want to see at a glance and make it easier for them.

I'm just a user suffering the pain, this is an example of a table I need/want to monitor and it's very poorly done, I need total revenue = sum of column 5 + 7, on mobile it's a very bad experience due to column 6 in the middle, unnecessary width of some columns with repeated text, etc. https://app.vx.tools/income/BfgMdL4FaNHp5zZpD7WMYG5sZUrCWQPE...

There’s a picture at the bottom. I think the text there is a bit more clear (maybe?): you have a cubic surface and want to see if there’s any “straight line” that lives/lies on the surface. It turns out there’s 27 lol.