Hacker News new | past | comments | ask | show | jobs | submit | 4death4's comments login

Reducing variance in a random outcome still has value. For instance, you might have the money to cover an adverse outcome, but if you could guarantee you wouldn't need the money, then you could park it in an illiquid asset (e.g. some type of investment).

So 99 of them could crack a password in 1 year? That is easily obtainable and not secure at all.

If your password is only 8 characters. I go with a minimum of 14. That means 99 years turns into heat death of the universe... Or a pipe wrench.

It doesn't work that way - and if it did - it's absolutely acceptable in most, if not all systems. A year to "break something" is absolutely considered secure in risk management of larger systems.

How does it not work that way? Password cracking is infinitely parallelizable.

Technically yes - but when it comes to attacks not really. If someone wants it, you have much easier and faster techniques.

Also in the NYC area. There seems to be a major shortage of blue collar labor: contractors, carpenters, plumbers, electricians, etc. the cost of home renovations is truly staggering due to this lack of supply.

So I work in tech but am pretty well-connected to the trades within my family and friends group. The major shortage in every trade is in helpers and laborers. It’s not the case that they need people with journeyman-level technical skills, are willing to offer lucrative TC, and simply can’t hire for the skill set.

They can’t find unskilled/semiskilled labor willing show up to a job site every day for $25/hr cash. Even 10 years ago this wasn’t a problem. The issue is that nobody wants to offer market-clearing wages and benefits because it cuts into the owners’ distribution.


We're asking businesses to make additional payments to their employees' landlords. If rents were lower $25 would be a good wage to live on, but given the cost of housing, we're all paying out to landlords, even homeowners.

Even if the copy the header, they can only perform a replay attack, which is an improvement over leaking an API key. Also, you could include a timestamp in the signature to limit the amount of time it could be replayed.

Sign a nonce.

Yes, but isn’t lead getting into your bloodstream worse than pollen? I mean oxygen gets into your bloodstream via inhalation…

Which plant produces pollen at PM2.5 tho? Pollen usually isn't entering your bloodstream through your lungs, its too large.

Pollen particles are quite fragile and tend to break up into PM2.5 and smaller, especially during rain events. See for instance the reference below.

https://doi.org/10.1016/j.aeaoa.2022.100177


In addition to pollen, there are spores from both mushrooms and ferns. Both of which are common cloud-seeding particles and can often be PM2.5

Most pollen is captured at pm10 or higher level. PM2.5 tends to be created by humans

Crossing the blood brain barrier exacerbates not only asthma but other vascular/heart and related diseases, including diabetes, as well as lung diseases.


Worse in what way? Lead is a long term neurotoxin, but pollen triggers the immune system and makes you miserable. Both are bad but in different ways.

It’s really unclear to you why a long term neurotoxin that leads to lifelong disability is worse than allergy producing pollen?

It isn't clear until you are suffering from allergies, and notice that old people who used to chew on lead fishing weights are not all that bad off. Most people with high lead in their bodies don't realize the issue nor to the people they know.

> used to chew on lead fishing weights

Chunks of lead just aren't that bad. https://doi.org/10.2146/ajhp060175 lists common sources of lead poisoning, and none of them are lead weights.

Common sources involve things like airborne lead powder (from grinding or smelting), lead compounds dissolved in food & water, paint, and lead in soil.


I don’t really consider making an API call as “logging in”. The term sounds really out of place other than in a few specific contexts.

The term “Identify” is a lot better in this regard.

It’s already universally used in IAM, where the other half of the puzzle is also clear and free from ambiguity: “Access”.


Identification and authentication are different, though. You identify yourself to a website as a specific user (e.g. using a username) and the website in turn authenticates your claim, i.e. verifies that you are in fact the user you claim to be (e.g. using that user's password).

If you go that route .. your OIDC provider authenticates your claim. The website just trusts some specific OIDC authorities which you must use to create your identity.

If the website in question is using OIDC, sure.

And the third half, “management” verbalizes the action therein.

Also, IAM has a cryptic assertion of ultimate authority: In Hebrew, . . . hayah carries the added weight of representing God himself: Yahweh, “I am.” [0]

https://hebraicthought.org/meaning-of-gods-name-i-am-exodus/


Identity/identify may or may not have anything to do with Login, or Authentication...

KYC (know your customer) are about removing the ambiguity between you user and their identity....


What could be a difference between identification and authentication? In my understanding they are completely synonymous. I frequently use an IdP (identity provider) to authenticate for web applications.

Know your customer is something that started in banking and is leaking everywhere.

Identity is who you really are. Be that you as an individual or as a corporation.... In the case of your bank they have a copy of your ID, your SSN, for them identity is what established the account and auth lets you work with it.... AWS might know some members of your company (either by corporate or individual card) but might not know your identity (as an individual) and yet you can still authenticate, because you have been authorized by an identified customer. I can transact with crypto as an authenticated user and NOT be identified.


In some circles "identity" is a term of art. For instance an identity provider maps credentials to user accounts. Those may or may not map to a government-numbered human.

I think authentication is about proof of identity. Identity can mean a lot of things imo. Applications identify me all the time without me giving them any proof of who I am. This happens in meatspace all the time too. People project identity and we make assumptions about what we observe. We don’t necessarily ask them to verify this identify through mutually agreed upon terms.

KYC is not so much about removinh ambiguity. It's about risk mitigation and proof. Not only about a specific user, but also the connections of a company or a person. There is also a lot of rules and laws behind against AML and PEP checks.

Access doesn’t cover everything though. But identify seems good

I think they mean use both - identity in place of login/authenticate and access in place of auth

Yeah, but access to me feels like access to records. Not necessarily permissions to do certain actions (in general or to certain records)

Iirc, Java or J2EE used “Principal”, which I found super confusing


Principal is Identity not access.

Indeed. "Logging in" implies some kind of long lasting session. And logging in conceptually only requires "identification" (e.g. via a username) but not necessarily "authentication" (e.g. via a password)

Identification is not necessarily via a username, people can identify you via just knowing how you look or your voice, the method doesn't matter.

IMO…

To “log in” is to convert the username/password pair (or API key, or whatever) into a smaller token with an expiration. Doesn’t matter of it’s put in a cookie in my browser, held in memory by some other API client, etc.

Aside: Why bother even doing that? Because every time you transmit the credential, there’s the possibility of leaking. We would rather leak the token that has an expiration.


Everything is interconnected. People who commute to work need a car. If parking is unavailable, then commuters cannot live there. If workers can't live there, then property taxes are lower and less money enters the local economy. You can't apriori say what impact these parking policies have.


> People who commute to work need a car

Quite a lot of lower income workers can't afford to commute by car. Breaking that "need" relation is the #1 priority for people trying to design lower-car cities.


Clearly there is a limit. Otherwise, you could circumvent all copyright by saying "The contents of Harry Potter and the Prisoner of Azkaban is <insert novel text here>". While technically a fact, it's protected by copyright.


There’s definitely an element of evolution: domesticated animals have evolved to have human recognizable emotions. But that’s not to say they’re not “real” or even “human.” Do humans have a monopoly on joy? I think not. Watch a dog chase a ball. It clearly feels what we call joy in a very real sense.


> things that are easy to do in the main implementation might be very difficult to do in yours.

The author mentions this when they talk about the ease of implementing new features in an interpreted language vs. a compiled language.


Hm, this is true, but I think it's worth pointing out that this is more general. The article was focusing on how JIT is harder than interpreting, whereas neither model in parent's post is inherently more complicated.


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

Search: