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

retirement is covered by social security healthcare by insurance (offered by the state if you can't afford it yourself)

homes, etc is true though and we just need to build more inventory IMO. but there are tons of areas with affordable homes, they just aren't near the big cities like NYC or SF or LA


You can not live on Social Security, no way. If you don't have a job your not getting healthcare and even if your job provides healthcare. Its too expensive to actually use. Also you need to be living below poverty wages before a state will give you healthcare.


all of cryptocurrency relies on sha256 the fact that the space is huge, and just ignores collisions. seems to work fine.


There have been so many incidents in crypto that exploited broken assumptions about hash collisions.

Factually, X != hash(X). Sometimes you can make the simplifying assumption that X == hash(X), but only in well-defined contexts, subject to proper risk analysis; never in general, or as a presumption of a system that needs to be correct.


SHA-256 has, well, 256 bits of entropy. What I took issue with was the claim that UUID's 128 bits (well, almost, anyway) are overkill with modern advances in randomness.


This is actually what they're building. They publish ZK proofs over the biometric data instead of publishing the biometric data itself.


Their critical error is that there's a single, central authority that certifies that a person with a given set of biometrics exists. They didn't bite off the hard, but necessary, part where you figure out how walk an attestation graph and come up with a confidence level.

And they only do irisis.

And they're doing the ZK at the wrong point in the chain. Publishing the actual, raw, unhashed biometrics wouldn't be a problem as long as they didn't tie them to anything but a key. And that future-proofs you.


it's honestly terrible. ask it "write 10 sentences that end in the word apple" and watch it flail.


incorrect. RL = reality labs. the VR and metaverse stuff.


Yes, easily. We do this for the JS runtime at litprotocol.com


Cool! Can you link to it on Github or something? (is it oss?)


Free speech is free speech though. Either it's free or it's not free. You are arguing for "not free". I am not a fan of that ideology. This isn't shouting "fire" in a crowded theatre. This is restricting access to speech (code) simply because the gov doesn't approve of what the code does.


Let's say we, as a nation, through our elected representatives, decide to pass a law against trojans. Then let's say there's a site hosting a trojan repo, open to the public, and they refuse law enforcement's demands to remove access to the code. So the FBI goes through the court and gets a warrant to seize the site and prevents access to the code.

Would you stop the above chain of events at the very first link? Would you say: "We can't ban trojans because it's code, and code is speech, and speech is either free or its not?"


> when platforms kick off the people we don't like

Is not a comment on free speech or not. There are rumors of government sanctions for this specific case, but the typical deplatforming is more like getting kicked out by the bouncer.


i dunno what makes you think that. the iphone 13 mini was released alongside the other iphone 13's and is the latest gen. all signs point to apple releasing a mini version of the next iphone, too.


They already brought this back as an option you can set.


Can you say more about this or point to a source? I'm very curious to learn more about this!


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

Search: