Comments URL: https://news.ycombinator.com/item?id=47124615

Points: 1

# Comments: 0

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.

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

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

Comments URL: https://news.ycombinator.com/item?id=45600897

Points: 22

# Comments: 14

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...

Great point. I highly recommend crowdsupply for this type of project (extremely technical target customers), especially if this is the first campaign you run, as their team is helping much more on the nuances of running a successful campaign.

(I know this is not the place for ads, and I’m not affiliated though I run crowdfunding campaigns on all the platforms mentioned.)

Bare in mind:

- bandwidth will be high, say 20-25 TB/mo outgoing

- ram you might be tight, if you have the chance to grow to 384-512 it'd prob be better

- you'll need at least 2 boxes, one for mainnet and one for testnet. Testnet will be "less important" so you can still run a lot of other things on that machine

If I were you, assuming you find this interesting, I'd start a testnet node on your current machine, get practice with it, as I was mentioning keep running your other services. And then if you're convinced you just rent a 2nd machine on any of existing providers/your favorite location to run mainnet.

The whole point about passkeys is to replicate the exact UX of passwords (registration, reset…) but offer protection against phishing, by using public key crypto.

If you want a different UX, use a hardware security key. But these failed to reach consumer adoption.

And of course the FIDO2 standard didn’t specify (yet) a way to move passkeys around, so each implementation chose their own way to do vendor lock in. But this will be fixed in a few iterations.