skysight-inc/HackerNews huggingface dataset:
> I disagree. The rich person may be more comfortable, but they are no more free. Confinement is confinement.

Is level of confinement the only thing that defines slavery?

Assume the rich person and the poor person want the same thing. The rich person can acquire it. The poor person cannot (or can only do so by risking force in response).

All else equal, the rich person can do strictly more things. How are they equally free? The definition of freedom is usually something along the lines of "the ability to do things". The rich person can do more things, they're freer.

The term for what I'm describing is sometimes "freedom from want" and is a commonly considered to be a freedom/right when discussing freedoms if you look beyond liberalism as it was in 19th century. The idea being that while liberalism does a decent job of ensuring that the government doesn't oppress you, it does nothing to ensure that other people don't oppress you. Granting some standard of living to everyone ensures that you can't be taken advantage of because you have no better option, no one can treat you worse than the living standard the government provides.
I assume this would only work if you want to never get a loan or say a new credit card - or anything of the sort that relies on that history.

Heck - maybe wouldn't even work for renting?
Yes, it's concerning, but let's be realistic about this. I'm surprised HN readers are so surprised by this! On a scale of Room 641A (https://en.wikipedia.org/wiki/Room_641A) to carriers divulging location when you enter somebody's phone number (https://news.ycombinator.com/item?id=17081684), I'd say this is 2/10 bad. This really has nothing to do with employers colluding and trying to keep salaries low. Instead, it's just a way for businesses to verify your salary, given they have your SSN, DoB, and address.

First, it requires your SSN, date of birth, and home address. That a) means that prospective employers aren't able to view it (since you're not divulging your SSN in order to get an offer letter), and b) given these three pieces of information, requesting your salary is probably one of the least malicious things somebody could do. They could steal your identity, open up credit cards (some credit cards allow you to now get a virtual CC number before the card is shipped and confirmed), open up phone lines, SIM jack you, etc. Getting your salary data (given you have somebody's SSN, DoB, and home address) is likely one of the lowest things on the list.

Second, salary data is fairly public anyways. For example, if your company is of any reasonable size, they probably employ people on the H1B visa. Salary data is public already. Here, for example, is Airbnb's salary data: https://h1bdata.info/index.php?em=Airbnb&job=&city=&year=202....

Third, there are legitimate reasons why this system exists. If you're applying for a mortgage, how do you expect them to verify your salary? You can submit paystubs, but those can be faked. Same with bank statements. The only way for a bank to verify your salary is to actually call your employer. And if a bank calls your employer to verify your salary, and they have your DoB, SSN, and home address, it's pretty likely your employer is going to tell them anyways. Even if your employer only confirmed / denied (as opposed to providing a number), they could just repeatedly call and binary search it. (This probably wouldn't surprise the employer, since you might be getting quotes from multiple mortgage companies at once.) Given that mortgage companies, banks, and other finserv firms need to verify your income and employment history, it's not entirely unreasonable for a centralized database to exist, and for it to be guarded by what should be secret (SSN, DoB, address).

That said, the problem is that the US is too reliant on SSNs. If you prior on (the US treats SSNs as secret), being able to access salary data with it really isn't ridiculous.
That's some shady behavior though. The whole point of the law is to prevent companies from penalizing employees based on prior salaries. Wouldn't be surprising if Google was finding excuses to retract offers based on seeing that they "overbid" on someone's comp. If anyone has had suspicious stuff like this happen, it sounds like it'd make a great lawsuit.

Would be nice if some journalist(s) made a big stink out of Google finding a loophole in this employee protection law.
I feel like I would be a horrible person for mentioning what is probably the obvious.

I file comments like yours unders "Jesus, that white privilege must taste so fucking wonderful".

That's why you can probably find an amazingly large amount of people not in your acceptable pigmentation that don't agree with you one bit.

I think the Brampton school board just had a lawsuit that sums that shit up nicely.
Argentina central bank to use 'full force' to tame FX markets, source says
Either the MVP will take too long to build or you’ll find out that you ended up over-engineering certain parts of the system and drown in complexity and tech debt.

But this tradeoff doesn’t need to exist anymore. We’re seeing cloud architectures start to converge more and more, around tools like gRPC and kubernetes.

I feel like I live on a completely different planet than this person, because gRPC, kubernetes, and schemas that generate schemas is NOT how I would improve velocity or scale. I appreciate the article though, it was a good read.
Yes, Equifax's ciso was clearly super competent.
Major NLP tasks are biased against women
For those who are surprised/outraged from a privacy perspective- the employment verification/background check/etc space is very VC hot. YC and its affiliates are surely investors in some players in this space? Maybe https://www.ycombinator.com/companies/checkr ?
I find the key to this is documentation.

Outlining clearly that you disagree with this approach, the risks involved and suggest an alternative but in the end you’re happy to build it as they suggest.
You're right, I wasn't clear in my parent post and have edited it. Basically the standard lime I've heard is that this is some kind of competitive trade secret / proprietary secret formula that they don't want other companies finding out. No one has once said "we'll tell everyone but our employees in order to keep labor costs down".
Sorry, to clarify, I meant in terms of whether any aspect of compensation can be legally used to influence how much non-salary compensation a company offers to a candidate.
Pardon my rudeness here, but personally: popularity metrics count for jack and shit in my view. I give not a fuck that one of the top #3 protocols of use on the net has a highly predominant mode/client that it's used in.

I'd much rather evaluate by how open & extensible a protocol is, how much innovation is possible. Even if it's 0.000001% of internet users who have tried https://delta.chat/ , so long as they are not hindered, I think it speaks enormously well to the innovation/frontiers-ing/diversity potential of email. We don't need diverse ecosystems: we need technical ecosystems which are potentially diverse, which could be innovated upon. Email continues to constitute a protocol that is nearly too simple to fuck up, a protocol that can be put to many, flexible, varied uses, far beyond it's original idea & conception, in a way that the big giants can hardly stop or prevent us from enjoying.

Oh sure, we might invent new systems that don't run at full potential while interoperating with the big giants, but innovation can happily continue on & emerge at the edges, and perhaps eventually popular demand will insist the giants do change.

Again, a crude return to rudeness, but evaluating technology by it's adoption metrics is a horrible, cruel, & senseless way to evaluate things. If we did want to come down on email, I'd say that specifically the highly automated, unfixable, unresponsive non-delivery shit-show (doesn't even show up in spam) situation that is fairly often encountered by host-it-ourselvers is the one truly damnable twist-of-the-knife the giants (Google in specific, you evil cruel heartless piece of shit fuckers) puts upon the world, that obstructs healthy growth of email.
Ask HN: Is anyone getting intermittent bearer token fetch errors on Salesforce
I in no way suggested that, please don't pretend I did. We have plenty reason to assume she wasn't.
Having hopped jobs every 1-2 years for the last decade, I don't think I've ever been honest when asked my current salary. Never bit me. It would be quite shocking (would it be legal?) if an offer was rescinded based on this data.
They asked for almost no information to get this data. If you just go find the data leak where everyone's name + SSN is - and then tie it to someone's current address then that's all you'll need.

Only things I noticed you needed to request info was: first + Last, SSN, DOB, current address
It would actually be very hard to build a RTOS using async functions - and the current use of async/await on embedded Rust is indeed not about RTOS, it's just embedded code.

The reason for that is that the point of a RTOS is providing guarantees: A certain task should be guaranteed to run within a certain time. To provide that guarantees, the RTOS needs to support preemption and prioritization. That allows it to schedule a certain task even if another task is running for too long. I'm not aware about any RTOS which makes use of cooperative multitasking.
Rich Harris has this "stick it to the man" attitude which I thoroughly enjoy. In his case "The Man" is React and Vue. He shows some back and forth between himself, Evan You and Dan Abramov in one of his videos. Evan You called it SvelteScript in not a good way. This is all part of the competitive fun.

My biggest beef with Rich Harris is that he doesn't credit Lars Bak and the small team at Google for doing incredible work speeding up V8. Google saw nodejs take off and realized they had to make V8 faster, so they put a lot of money into doing so. Unfortunately the virtual DOM took off before V8 got super fast. Look up "you don't need a virtual DOM" for confirmation.

I believe it's one of the reasons Microsoft threw in the towel and adopted Blink. If you can't beat 'em, join 'em.

Harris also doesn't give any credit to the reactive binding work that came before him. He acts like he used a spreadsheet and had the bright idea to make a website that way. I have a strong sense of fairness so I don't think a designer/dev working for newspapers should take the credit from the geniuses at Google who made it possible. I think it's quite possible that he doesn't know any computer science but he's a gifted amateur.

Im looking at Shadow DOM components myself, but it's quite possible I might use Svelte. It's a nice tool, but it's not the magic beans that solve all your problems like no one ever before.
My point, as stated originally, is that "web3" and all the hype around it in its current form will require less (practically none) permission for users to interact with it than the existing web paradigm we are familiar with.
How is this even legal? How do we make this no longer possible? It seems like we need a new law to stop this unapproved sharing.

Did we ever agree to this?
We use Nix + Bazel. Nix builds the base image with Python and whatever else we want. Bazel layers our actual Python app on top of it. No dockerfiles at all.

Example: https://github.com/jvolkman/bazel-nix-example
Plenty of free roaming chickens on Maui
It's basically Conway's law in operation, just that it crosses business boundaries in this case.
I remember that would be kind of an issue like 15-20 years ago -- not sure why, but switching out from a 3D game to the desktop would take forever (I mean I can imagine a bunch of reasons -- ram was expensive, hard drives were slow, swap was more of a thing, processors were single core, graphics cards had terrible drivers, etc etc -- the reasons are too numerous for me to nail it down).

Nowadays on any reasonably performant system, it would just possibly pop the start menu up for a second, and then you'd click on the game -- everything should be fine outside of super competitive situations. Hitting start was always a rare event anyway, but now it's been degraded from a rare catastrophe to a rare minuscule inconvenience.
Thank you for the link! :)

Sorry for not including it in my post.
Even when I said "we are all doing it" you choose to assume I was too firstworldly to have an opinion. Trust me, I know very well how we Argentinians use crypto. The country monetary policy is a mess and we don't like to pay taxes. You can tell yourself whatever heroic story helps you cope with the cognitive dissonance, I'll still find it amusing.
Exactly this. There's a reason using past salary history in employment is illegal in California.
I found that a good way to pick a framework or make architecture decisions is to borrow ideas from ATAM [1]

In a nutshell: specify some important scenarios based on your requirements; for each scenario make a list of desired quality attributes and a way to measure them; use this combination of (scenario, quality attributes) to evaluate each option.

It’s a simple and obvious method, but for some reason is barely used.

A critique to the article: the evaluation criteria doesn’t seem to take into account any real scenario. For example why 15kb? Are they planning to serve people with very low bandwidth? Is the speed of the FCP more important that time to interactive (TTI)?

Regarding frameworks. A difficult metric to measure is hiring: if you are planning to grow your team, a popular, nice to use framework is another point to attract talent (eg choosing Backbone,jQuery,and CoffeeScript may fit your quality attributes but in 2022 is not very attractive for a job description).

[1]: https://en.wikipedia.org/wiki/Architecture_tradeoff_analysis...
When I submit the myprivacy.equifax.com validation it hangs at "Processing..." indefinitely. #AbolishCreditAgencies
Dan Abramov is fairly responsive on Twitter. I'd ask him.
While salary data is available on h1bdata.info - I never found it showing RSUs or any equity of the like. Whereas this clearly shows how much I am getting from RSUs. It didn't show any equity stake but - holy crap - it was disturbing that my RSUs showed up so obviously. Very easy to figure out how much I was awarded.
I love this idea, it's fantastic! ADHD unite!
The 16" has 4 USB-C, but the 13" basically means you're going to use power for one and possibly a display with built in port or a docking hub. If your display can also provide sufficient power and act as a dock/hub that could all work with one. I use an LG display which provides power but not the full wattage that the MacBook Pro wants so end up using two ports.
If you verify with tax returns, it would be easy to borrow money from a friend and count it as income every year just for loan qualification. And then borrow more money from a bank, wait 6 months for seasoning, and use it as down payment to buy real estate.

And if the loan gets sold to the government, it needs to meet government underwriting criteria and the lender has no free will. Especially for residential mortgages: No private business cares about 3% interest on a loan, they sell those to the government and make money on the origination fees.

If you get a hard money loan, they'll only ask for tax stubs but you'll also pay 10-12% interest. If the buy is really good sometimes they don't even care about taxes or ability to repay - they get your equity if you default so who cares if you make a dumb decision? It's mainly the government loans where they really try to avoid defaults.
Might as well do it so you can freeze it, they already have the info
It is so fucking frustrating to explain to anyone who works as a manager in a call center that the only real thing you can count on being able to understand in your IVR system are actually just DTMF signals. For whatever reason, it seems to be impossible to explain that B, P and V all sound the same on a noisy connection when it's part of some account number. It's impossible to explain that no one knows what "alphanumeric" means and that fully half of Americans have reading comprehension below a 6th grade level. And that using terms of art, jargon, and acronyms will be extremely frustrating for users when encoded in an IVR system, since human call center workers will always clarify, but clarification in an IVR system can't happen in a natural way - you either have to anticipate that the person won't understand and waste the time of half your users, or find some impossibly elegant way to say "I'm going to use terms you don't understand, barge in by asking me to explain if you don't understand a term."

The absolute zenith of an IVR system would require no human interaction with a robot and would correctly answer questions unprompted and route to human customer service without prompting or asking anything, and would never require a person to enter the same information in a call twice. What we get instead are systems that are primarily designed by non-experts whose sole metric is making the phone calls go away, but only pills can actually do that.
Not just Equifax.

There are any number of consultancies that collect salary (and other compensation/benefits) data from many companies and then share that information with all their clients.

It's used as a method of putting downward pressure on salaries without explicitly colluding.
Dang, look at the context. I was simply repeating his self-assessment back at him, and trying to flip it with a positive message that one's circumstances of birth do not define one's potential - unless you let it (mental prison). I feel like you've taken the exact opposite reading from what was intended.

That said, when people don't understand what you're trying to say, the fault lies with you. I'll try to rethink how i can phrase this kind of thing. I was trying to challenge in a positive way but it obviously didn't come across like that.
Users could also just not use these apps. Are they not also culpable?
> It doesn’t make sense for a user to...

Famous last words of many a unemployed junior developer...just sayin'.
Well I'm pretty sure I did consent to it, at least.
An annoyance with Debian postinstall scripts during package upgrades
Get some time with the boss. Share what you accomplished, ask them what they thought of your work.
Also used DRF in prod, the serialization in particular is super slow.

Also no asyncio isn’t great in this day and age.

Plain django, without DRF, just using JsonResponse is pretty great TBH, has all the batteries for things like auth and testing. Although having it be async would be a huge plus.

I recommend checking out pydantic and using that to enforce a schema for endpoint responses. Also much easier to understand (imho) than DRF’s serializers and you get static typing for free!
> . It's because then my day job became hammering scope until the problem could be solved with CSS so we didn't need to write any Superset of JavaScript at all.

CSS is the least of your problems, wait until your career gets to the point of 20+ developers.

And by "compiler errors" I don't mean TypeScript, that is easy peasy ... I mean Angular.

And even that is easily sorted if you know why it's complaining and how to fix it.
Does the system not ask for SSN to pull this data? If yes, how did Google get your SSN?

Disc: Googler.
Yes of course, that is their obvious goal. Desiring ever more power to assure safety is one of the common motivations of authoritarianism in general. It's incompatible with a free society where power is distributed throughout many independent parties.
I actually feel it would be successful because it exactly fits the ecosystem. A lot of Java code is classical threaded code. E.g. the majority of Java servlet code, and older web frameworks. Those would all immediately benefit from Loom in terms of resource utilization and scalability.

Of course Java also has some frameworks like Netty and things built on top of it - which won't benefit. But I feel like even though those are great from a performance point of view, they are actually more niche in the overall java world.
No, Equifax does not share companies' payroll data with job applicants or employees. Only companies have access to salary and employment data.
ive worked on vue and have been looking to dip my toes into ruby on rails, any tips?
Two-factor authentication in Rails 6.1 with devise-two-factor
I think they should get a Wikipedia page for this, it's too bad Wikipedia has its current notability regime :(
It's implication logic.

Employer sharing your data means you shouldn't think twice about doing the same.

Employer not sharing your data does not necessarily imply you can't.
Unfreezing is a relatively easy process. They'll send you a pin where you can do it online, or you can send them a letter. It'll take them about 7 to 10 days to unfreeze things
Unless you are very young (read: born after 2011) your SSN can be trivially brute forced if an attacker knows where and when you were born, because those details were (before 2011) mapped onto 5 of the 9 digits in an SSN.
interrupt-like things are used to schedule the next poll of the function. Polling doesn't happen randomly or within certain time intervals, but when an external event (via a Waker interface) tells the runtime to schedule the function again for polling.
Just pick a popular boilerplate, like create-react-app or framework like Next.js. Don't overthink it as this stage.

I like SvelteKit with Typescript a lot, but there isn't as big of an ecosystem as React has.
Tell HN: Code_connect: A subreddit to hangout, discuss projects and team-up
In response to a recent question[0] on HN regarding ways to connect with other developers, I created a subreddit[1] to hangout, discuss side-projects and to team-up on new project.

Please do provide suggestion to make it better.

[0] https://news.ycombinator.com/item?id=29794007

[1] https://www.reddit.com/r/code_connect
There's always answers like "I think $X would be fair, it's a little more than I'm making now", or "it's close to what I was making before", etc.
Do You Speak the Lingo?
Even if what you are saying is true, that will not solve anything for Bitcoin, which is the majority consumer of electricity for the crypto world
The explanation most likely is profits.
It is actually. And mental prisons are real, I was trapped in one for many years.

I'll stipulate that i have to tweak the way I say things as it's not coming across the right way.
If all employees share their salary information with each other, it becomes a headache for the employer. Each employee may quote the other person's salary demanding a raise.

This is the reason behind the "keep your data confidential" idea.
Yea, but it's Equifax, so they don't get the benefit of the doubt.
Two words: survivorship bias. How many people out there followed a similar strategy as the author, only to fail miserably?
Sounds like you don't have a good manager, if this wasn't being communicated to you and she had her boss deliver this feedback to you alone. You should talk with your manager about it and if you don't feel the relationship improves soon, my advice is to switch teams (at the same company) or companies entirely. If you have a bad relationship with your manager, it's going to be unfun to work there, and life's too short.
Are they sponsoring CES 2022?

https://www.ktnv.com/13-investigates/13-investigates-how-ces...