skysight-inc/HackerNews huggingface dataset:
> That's a silly definition of "enough" to label as a fact.

There's no "factual" definition of "enough" as "enough" is subjective.

I'm also not sure what you're trying to argue. I already said that it can't be 100% for practical reasons and that the market actively incentivizes companies to aim for as close to 0% as possible instead. You pick 90% as an arbitrary percentage. So it might be 99% or 50% or 1%. But you're still agreeing that the measure for "enough" in this case is in relation to what the product of that labor can be sold for (after deducting the various costs). In reality that percentage is often much closer to 50% than to 90% - in many cases (especially so-called unskilled labor) it is closer to 1% than 90%.

A better rebuke would be that "enough" is normally about need, not revenue. Especially because it's nearly impossible to value the relative contribution to the bottom line for all labor involved (and in fact trying to minimize "cost centers" can lead to a rude awakening about this).

So if we define "need" as "enough to sustain a healthy existence in society and access to moderate leisure activities" (i.e. having a roof over your head, food in the fridge, access to medical care and transportation and enough spare change to spend on things like streaming services, books or the occasional trip to a nearby cinema, amusement park or restaurant) we can define a minimum monthly income and if we assume a 40 hour work week (which should be uncontroversial given that overall productivity has only gone up since its introduction and we need to provide some leisure time to accommodate family formation and the aforementioned leisure activities) we can translate that into a minimum hourly wage. Something tells me that this minimum hourly wage would be significantly higher than the legal minimum wage in the US, even if we don't actually consider the lackluster state of medical care affordability (note that I didn't assume public single-payer healthcare so Medicare/Medicaid is just a crutch to account for medical care being unaffordable otherwise at that level of income).

But of course the system is not set up that way. It's not about needs, it's about paying as little as you can get away with and this means that pay is proportional to power (i.e. C-level execs are paid a lot because they have a lot of control over the company and therefore "deserve" more even if all the value they "create" relies on the actual labor and competence of others) and the floor is theoretically infinitely low (i.e. you could realistically charge people to do labor for you, e.g. as a "training opportunity" to earn a meaningless qualification required to access other jobs) and ultimately the company needs to produce a lot of waste money (profits that are not re-invested in the company) that can be drained by its shareholders/owners (who ideally contribute literally no labor in return).
>You’re being dishonest here ... You can’t count temporary residents

Yes, you absolutely can. There are millions of "temporary" residents here needing housing, clogging transit and hospitals and schools and services. Millions. They don't not exist because they're inconvenient to an argument. And there are almost certainly far, far more than the government is openly acknowledging. Hospitals are filled with NOSTATUS (e.g. no legal right to be in Canada, and with no insurance) elders [0] that many of those temporary residents dragged to Canada, also with zero inclination for them to ever leave. The problem is exponentially getting worse.

And here's a cold, hard truth -- the vast majority have zero inclination of ever leaving. The whole reason there was an absolute explosion in temporary residents is the belief by many that this will be permanent some way or other. And history with this government is that it will. Just do a couple of protests, cry about how exploited you are, and it becomes a PR and are magical social capacity to absorb the world makes it happen. This government is already talking about granting permanent residency to people who once had a temporary residency which expired and they just...stayed. Because there are zero consequences or downsides.

> Every recent problem Canada is having can be traced back to housing cost.

It's a serious, profound problem, but no it isn't everything. Having more people competing for everything has consequences. It's impossible to camp. Parks are absolutely overwhelmed. Traffic is...worse than ever. Our mass transit is now absolutely filled with e-bikes as food delivery workers that fill basements in the suburbs flock to the city.

The thing is, untold millions are fleeing India and elsewhere not because of how great density has turned out. Recreating it here is not a goal most Canadians appreciate. It's okay for every bit of greenland not to be paved over. It's okay that everything isn't pushed to exhaustion.

[0] - A major reason Canada is pursuing mass immigration is the demographic problem of an aging population. The rhetoric falls apart when that young professional brought to Canada then chains in their extended family, dragging the average somehow even higher than it was before. Canada's immigration -- the purpose and rhetoric behind it -- is profoundly dishonest and has run on a playbook that anyone questioning it is just a vile racist and can be discounted. At least until the government pushed it to the point of disaster and that force field fell away. There are going to be a lot of really hard questions and answers about the various programs in the coming years.
m4a*. Or Opus.
> The endgame of intersectionality is -- gasp -- considering people as individuals.

I'm not sure I read your tone correctly but this is indeed what authors like bell hooks try to get at: being Black is one thing, being a woman is another and being a Black woman can be different from either of those things in isolation; ultimately our experiences are defined not by each attribute individually but the way they interact in combination. Any subset of attributes will always give you an incomplete understanding but they can still be useful lenses.

Charles and Ozzy do have a lot of things in common and they do have many shared experiences because of them and do experience many things similarly because of them. Of course those things are not all there is to them and e.g. being born into the royal family may significantly outweigh most of the attributes they have in common for many such experiences.

Modern feminist critique is intersectional because it recognizes these complexities and recognizes the limitations. But feminist critique explicitly challenges the systems underlying our society. Girlboss pop feminism did the opposite, an infamously inane example argument being that then-state secretary Hillary Clinton is underprivileged compared to a homeless man because she's a woman. Corporate DEI is a step up from this but still falls flat because its ability to critique systems is limited by being beholden to the corporate structures that allow for it to exist: it's essentially the "more female drone pilots" joke but without a hint of irony.

Again, that does not mean DEI can't do good things (e.g. being mindful of inclusivity can reduce artificial or cultural barriers to entry and increase representation) but it can't solve systemic issues because it can't meaningfully challenge the systems it exists within. This is what led to the tensions resulting in stunts like those at Basecamp or Coinbase where the owners of the respective companies decided to expel DEI and claim to create a "politics-free" workplace because the people involved in their DEI projects refused to stay in the comfortable confines of feel-good corporate (literal) virtue signalling and got dangerously close to critiquing the structures around them.

You need to consider people as individuals but if you want to make sense of systems you need to pick subsets (plural!) of the attributes that define each individual. Where DEI falls short is that it usually by design is only allowed to pick a limited number of attributes and is even more limited in what systems it is allowed to look at. Wheelchair-accessible workspaces, yes. Racism towards Black employees by their peers, yes. Sexual misconduct by middle managers, yes. But anything that challenges the leadership or ownership structure of the company is too close to unionization for comfort.
Thumbs up, plus a well-maintained Makefile that I share among my projects. Never had any issues. Github matricx test runners ensure that everything works across platforms, Python and dep versions, ...
Yeah, I think a key point is that Salvatore Sanfilippo, the original developer, maintainer and principle contributor[1] for 11 years, was not a founder of Redis Labs. He joined as an employee in 2015 but resigned in 2020. Perhaps he has equity in Redis Labs, but it's not clear he stands to profit at all from this switch.

[1] https://github.com/redis/redis/graphs/contributors
Who are you to propose requirements onto people who work for free?
Half-seconded. I wouldn't claim to have fully understood how the Qt licensing model works (and I think it can be different if you do servers, or deliver binaries), but it's definitely worth checking out your exact use case, because I find developing in Qt really good.
I believe the term "nation state actor" is a term that means "country" but with the bonus of connoting that the writer is an armchair infosec wizard. This speculation is not valuable without adding information, otherwise it's just McCarthyist bluster.
There was a pilot onboard, right?

If I remember correctly they made the ship steer of course quite sharply. If the pilot dropped anchor and made the ship do that they might be in error.
> Release often, but don't break old code

That may become expensive fast
Greek geometers (e.g. in Euclid's Elements, Book 7) define a "unit" to be 1 and "numbers" (arithmoi) to start from 2. https://mathcs.clarku.edu/~djoyce/java/elements/bookVII/book...

But in practice there are a bunch of propositions/proofs where 1 is treated as a number just like any other.
In my brief time at McDonald's, I was paid the then minimum wage, $1.60 per hour. That summer, $1.60 would buy a bit more than five gallons of gas. By that measure, $20 per hour in California is about keeping up with inflation.

On the other hand, about 125 hours of $1.60 would cover a year's in-state tuition at a public university then. It takes more like 700 hours at $20/hour to cover California in-state tuition now.
I can walk out on the street and stab someone to death if I wanted to. This is surprisingly easy.

Just because something is relatively easy to pull off doesn't mean it happens a lot.

It's also not that easy to pull off because you need to have a project with relatively few eyes and a place to hide it. In this case: binary tests. But most projects don't have those.

There is no evidence for any of this, including that it's a nation-state actor. There's also a case to be made that it's NOT a nation-state actor as nation states use Linux and want a secure Linux. The NSA and such have somewhat conflicting interests here. We just don't know. It's likely we will never know.

All of this is starting to resemble the spy paranoia of the first world war. A few spies got caught and suddenly everyone was now a suspected German spy (including a general, if I recall correctly, who was detained for a while because he couldn't answer a question about baseball or some such).

I suspect that very soon people will start demanding maintainers put some of their blood in a Petri dish to be tested with a hot needle. Just in case.
But "other levels of government" are also getting the money from taxpayers, and money printing is constrained by its propensity to cause inflation, so in practice the amount of it that happens will correspond to the amount necessary to hit the Fed's inflation targets rather than scaling with the amount of government spending. Consequently any incremental increase or decrease in government spending would have to correspond to the same increase or decrease in tax collection, whether as the full amount in the current year or as future interest payments via deficit spending.
At least in the US, these have no legal basis.
Making critical decisions based on irrelevant data can be misleading and drastically affect your organization's performance. According to Toward Data Science, about 40% of business initiatives fail to reach success because of poor data quality. Data quality assessment is no longer an option; it is necessary to ensure that the collected data meets set standards and expectations.

Poor data quality is not just a misstep—it's a costly sinkhole; it destroys business value and, eventually, ROI. A Gartner research found that poor data quality is responsible for an average of $15 million per year in losses.

In machine learning, subpar data can derail a model faster than a single flawed line of code. This process dives deep into data, pinpointing inconsistencies, missing values, and anomalies.

However, multiple data quality assessment tools like MarkovML lay the basis for a thorough evaluation by putting data quality at the center of AI projects.

Data quality measures encompass accuracy, completeness, reliability, relevance, and timeliness. Ensuring data aligns with business objectives and represents the true state of affairs is crucial. Top methods for data quality assessment include data profiling, cleansing, validation, mapping, integration, and visualization.

These techniques uncover anomalies, correct errors, and standardize data for informed decision-making. In-depth data quality analysis involves statistical analysis, data profiling, and duplicate detection to maintain impeccable data quality standards.

The Data Quality Assessment framework serves as the backbone for informed decision-making and strategic planning. Designing or building a robust data quality assessment framework is vital for ensuring reliable and accurate data.

Read the full article https://www.markovml.com/blog/data-quality-assessment to learn How to Design or Build a Robust Data Quality Assessment Framework.
#DataQualityAssessment #DecisionMaking #BusinessPerformance #DataQuality #DataAnalysis #MachineLearning #AIProjects #DataProfiling #DataCleansing #StatisticalAnalysis
You probably still rely on trusting others a lot more than you realize.

If you really, really, didn’t rely on trusting anyone, I don’t even see how it would be possible to exist on earth.
AWS and Google contributed those under BSD license, being fully informed that Redis Ltd can commercialize like this.

It makes perfect sense for AWS and Google to fork immediately after the switch, but for contributions before the switch, there is no basis for AWS and Google to complain Redis Ltd, either legally or morally.
> But this suggests reimplementing xz/lzma.

If there is a known good copy of the repo from before the attacker had sufficient access to alter history, then that is an acceptable starting point.

From there you look at each update since and assess what they do to decide if you want to keep (as they are valid improvements/fixes) or discard them. If some are discarded, then later ones that are valid may need further work to integrate them into the now changed codebase. Similar to Debian assessing upstream security patches to the latest version to possibly back-port them to the version they have in stable, when there is significant disparity (due to a project being much faster moving than Debian:Stable).

As xz/xzutils is a relatively stable package, with very few recent changes, this should be quite practical. A full rewrite shouldn't be needed at all here.
Thanks for the kind words and the insight!
Yes and no.

A local GIT repo can be changed (including its history) however you please.
But once you have shared it with others you can't take that back.
If you try to, then others will notice that the hashes mismatch and that their HEAD diffs uncleanly.

I know the term is infamous here, but GIT is essentially a blockchain. Each commit has a hash, which is based on the hashes of previous commits, forming a linked list (+ some DAG branching).
>>Substantial portions of Redis were written by AWS and Google

Employees on their own time, or paid to do it?

So I'm clear though - if I wrote a SAAS product tomorrow that under the covers used Redis, I'm OK, but if I spun up a bunch of servers and offered managed Redis as a product, I would need to pay?
News just in: NSA et al. defeated after having to create a LinkedIn and Instagram profile for their agents.
> Especially in the EU, the definition of distribution of derivative works is typically so strong

Maybe I'm naive but how strong can it be? And is there anything that can't be solved by liberally decorating your software with links to the git repo of Redict?
The irony is that this would make a oddly effective way of having paid open source devs who for the most part just honestly improve projects. With the massive downside they undermine it at a critical moment.
Send me an email (in bio)!

I have so many ideas of stuff I think really needs to be buil and has huge upside potential but no one is doing anything about.

I would like to affiliate with your accelerator in any way
possible.
Is this like a Richard Stallman ideological thing?

(EDIT: Genuine question - I'm trying to understand if this is a license purity issue or something else).
On top of what you mentioned I also dislike the TSA-like response the OSS community is taking with this happen stance.

I have anonomously contributed to many projects because I enjoy my privacy. All of my founding projects have also been done with anonymity.

Because someone wants their anonmity and privacy does not mean they're nefarious, and I find it funny the group that takes to these principals most is negging on those ideas.
MS funded people and pipelines to analyze it. Jia Tan convinced them to disable the fuzzing that was designed specifically to find malicious behavior, using social engineering, and one MS engineer did find it.
At least for a Prius, it can be done by hand, even DIY. The battery only weighs about 100lb and doesn't require any special tools.

https://www.youtube.com/watch?v=oAHaYXBFnJo

OTOH, replacing the Rav4 hybrid's battery is apparently much more difficult and I couldn't find anyone doing that DIY.
This just isn't how the semiconductor industry works. You invest in leading edge and then you try to find demand for the older stuff. There's tiny margins for the older stuff- because the people choosing to use it are literally choosing it for cost reasons and there's no competitive advantage - they can shop around to any of the fabs. The capital investment is all done and you're just trying to make the most of the sunk costs.

It would also be a choice to basically not be a company in 10 years. The low end stuff is the stuff that was bleeding edge 10-15 years ago. If you decide to focus on that older stuff and don't chase after the bleeding edge then in 10-15 years you simply won't have anything competitive at any level, your company will basically be done - your 45nm process will be competing with TSMC's 16nm (which will now be old tech) and you'll just slowly move up and up out of competitive markets.
Well, I was in the ocean saving a person getting caught by such a big wave on the beach, so I do appreciate the power of the water here. But I think 3 m waves are quite normal on most coast lines in rough sea.

So my question was, why would a Tsunami of the same height be that much worse. And in comparison to the destruction of the earthquake in general here.
For some recent holiday I had my girlfriend burn me a CD of an album I liked. (Legally bought DRM-free)

I'd make her a mix CD, but there isn't much music we've listened to together.

In fact, when I talk to anyone about music, the result is often a mutual "Hm, never heard of them" followed by non-interest.

Music discovery is done independently and I don't usually want to get into other people's bands. I guess it used to be more social. I'm a late millennial, almost Gen Z. For me music is personal and not social. I listen to a lot of video game soundtracks.
As a true multi-platform user I don't have strong feelings if Windows apps, or KDE apps, or Gnome apps are better. I've not much experience with Macs, but it usually also worked out ok.

But yeah. Electron is usually bad, it gets worse if it's just a tiny app that you never interact with (all the problems, plus the RAM, for something that doesn't even need a good UI), and usually only tolerable for actively used foreground apps, if there was a ton of dev investment. Most hobby electron projects suck, if not for the the fact that they at least shipped something.
Yeah, I plan on paying approximately double (100% markup) if I'm ordering delivery on an app. That's why I only do it when I'm in a hotel room on a work trip and I don't have the rental car keys. Hotel food is not cheaper, not tastier, and I have way less options (I am a vegetarian).
It felt like a shame MD Data [1] didn't catch on - but with existing MO formats out there maybe there was no point.

I was also reminded today of Floptical [2] drives, which I vaguely remember hearing about (but didn't catch on either).

Finally, there is my personal niche favourite, DataPlay [3], which were just so small and cute.

[1] https://en.wikipedia.org/wiki/MD_Data
[2] https://en.wikipedia.org/wiki/Floptical
[3] https://en.wikipedia.org/wiki/DataPlay
Similar business model to short sellers who take a short position on a stock before publishing their “investigative” report on fishy financials, fraud, etc.
That seems to nail the "news" aspect, but missing the vital "wiki" aspect which is all about collaboration and user-edits, which I think the parent was hinting at.
It's why I actually always encourage app devs to charge for their apps, even open source ones. It creates an exchange of value for the author to feel valued and detract from these vectors.
I wouldn't limit that to OSS projects. How many of them managed to get hired and are working for Microsoft, Apple, Google, Oracle or Amazon?

In some cases they don't even need to introduce backdoors themselves but just review and spot bugs they don't correct or raise issues for but communicate to mothership. They could even work in team with having one building the backdoor and the other approving the code.

Most companies have more thorough processes to avoid this but that doesn't mean those processes are applied correctly everytime, especially if more than one malicious engineer is involved.
I'm interested in checking out Go.

Could you recommend a stack please?
* Testing - test runner, mocking
* Database - Typesafe queries, ideally as little abstraction as possible, migrations
* Web app framework
* Dependency injections (or do you prefer doing it manually over using a library)
Have to agree with this sentiment, and I'm surprised it's not getting more traction. If startups are like chess, they are like very low level chess because the game was just invented. Nobody knows what a blunder is yet, many will go undetected, and worrying about playing perfect chess will probably outrun your runway.
It's a weird collection of topics, all in the same dry style. Definitely AI.
Is there a tl;dw? That's an hour long video.
This makes more sense as an explanation.

Are there any instances where an SSPL license or similar is warranted?
Great work Sean, this is quite impressive. It seems you were previously an EM, but clearly very technical. I'm currently an EM and technical as well. I'm wondering what made you take the jump and decide to build this on your own. I'm in a different domain, but my industry seems stuck in a local-minimum that just sort of works well enough, and I have a lot of thoughts about what-if things were built in a different way. Can you share a bit more about your story and any advice in making this sort of jump successfully. I'm happy to take it offline (my contact is in my profile).
Also this can all be faked