skysight-inc/HackerNews huggingface dataset:
From https://www.irs.gov/statistics/soi-tax-stats-irs-data-book:

"During Fiscal Year (FY) 2022, the IRS collected more than $4.9 trillion in gross taxes, processed more than 262.8 million tax returns and other forms, and issued more than $641.7 billion in tax refunds."

So 5.7B is about .1% of the IRS's transactions that year.

That's also less than it could possibly cost to deploy and maintain Worldcoin.
Same finding.

That's why that sentence in the article "but almost every technology company uses it." should be rephrased to "but almost every technology company do not need it"
Mine are still randomly generated, but using the diceware method. Best of both worlds, really.
Scanning the comments here and I don't see anyone addressing the elephant in the room: PATENTS.

After a bit of searching, it's unclear what degree of "patent risk" comes with JPEG XL. JPEG historically was subject to patent troll lawsuits until the patent expired in 2006.

Please note that it's not enough for there to be a "royalty-free reference implementation" of JPEG XL, even if it's licensed with Apache 2.0, because you can't be sure from a glance that the Apache license patent grant includes all relevant patents. If you care about open source and free formats, you should look for two things: a comprehensive patent pool transferred to the standards body AND a royalty-free patent license to anyone with no strings attached.

The game here is that companies with potential claims over some techniques used within codecs have an incentive to withhold their patents from the official pool until years after adoption. Then they sue the biggest users of the codec (like Google) for obscene sums of money. That's why ALL of the patents used in a codec must be assigned to the standards body for open licensing, and you have to be SURE that none are withheld. This is difficult.

AVIF (and it's standards body, the AOM) was created in part (I believe) to solve this very problem. All the major tech companies are members and they've effectively agreed to a patent truce with regards to codecs.

This is arguably the most important commercial concern in distributing a browser for free that includes codecs. If you ship unlicensed codecs, some random company can crawl out of the woodwork 5 year later and sue you for a billion dollars.

In my view, AVIF only needs to be competitive with compression and quality. It patent risk is so low that it is the obvious choice. AVIF is truly open, there are multiple implementations, and its reason for existing is to solve the codec patent problem.

Source: I was near the activities within Netflix that helped found the AOM.

Disclaimer: I'm not a lawyer and this isn't legal advice; also I'm several years out of date w.r.t. JPEG XL specifically, so I'd be happy to be corrected about the relevant patent risk. Maybe someone has better info?
I’d be interested in this as well! To answer your question, I imagine a list of tasks available to work on which I can pick up tasks from whenever I have time.
The Star Wars universe is fictional. Do you honestly believe that the author from our universe who came up with this name was not aware of the (Earth universe) meaning of the word 'jizz'?
It still will be the future though unless he's getting radar'd at the exact moment he is reading the sign, which is highly unlikely.
Are you even a Linux user if you haven't built your Linux From Scratch?
1. By payload size do you mean record size? They're ~1KiB
2. Flush interval was 100ms, the agent defaults to 250ms though I believe.
In principle, yes. In practice, one occasionally has to choose the least immoral option. That does not invalidate the principle.
Glad to hear this, indeed we think there's opportunity for some more cutting edge tooling in the TS ecosystem.

We absolutely want to add a caching layer. Actually, we think middleware is where a lot of the value of the framework will come: it enables a whole bunch of features, e.g. sending errors to datasets for labeling, caching, user throttling, analytics, A/B tests, ...

We're likely going to build the serving module next which will cover this.
Intel deactivated avx512 in non pre-production. Did you mod your bios, or were you affected as well by this?
This goal reminds me of "The Room-Temperature Room" from Community [0], maintained by an elite secret society of air-conditioning repair technicians.

I think part of what I love about that clip is the (exaggerated) idea that there are all these everyday amazing things we don't usually think about, precisely because lots of human work and genius has gone into eliminating noticeable problems. Things that aren't exciting or glamorous or sexy, but dangit it'd be cool if they were.

https://www.youtube.com/watch?v=VxxYqE4Gil8&t=0m45s
1 in 4 new cars sold in California last quarter were EVs, an all-time high
> Besides, if borders had anything to do with it, it was never UBI in the first place.

Yes, it would; neither form of the “U” in UBI includes free of borders in the sense used in the term, and reinterpreting that way and pretending its what the term means is just lazy equivocation.
> I'd put money on there being many more rich Londoners in desirably located flats than same price house

I know that, but that's not what most londoners believe.
1. A dove soft toy, that can tuck its wings:

- stencil: https://github.com/azriel91/dove_stencil/

- wings tucked: https://github.com/azriel91/dove_stencil/blob/main/photos/20...

Made this because one of my friends said she liked things with character, and I knew that a handmade soft toy wasn't "enough", and so letting it tuck its wings was that character.

2. Many ambigrams (words that when rotated upside down, read as the word). These ones are names for friends / acquaintances

- blog: https://cards.azriel.im/

- different names: https://cards.azriel.im/2018/09/kevin-fiona.html

- colour inversion: https://cards.azriel.im/2018/01/carlo.html

I still make them occasionally, just haven't updated the blog

edit: ah it's not markdown, links were codified
Isn't that the subject of this entire thread?
I find it kinda wild that we are seeing article after article of people dismissing this without actually experiencing it first hand.

We also can't ignore that in every image shown, it appears they are using a virtual screen that is far larger than what most people likely have. meaning the text will be larger. You could argue that this is to fix a flaw with the hardware but it is also something that you are able to do when you are not dealing with a physical limitation.

Regardless of that because I am not going to pretend to understand a lot of what is in this article, it is way over my head. I feel like the thing that we keep ignoring here is that this is not meant to be a great success right out the gate. Apple knows this with how they are pricing it and how they are talking about it, including it being a "pro" version first. This will be a niche device while the hardware catches up with what the software can do.

But ignoring that eventually the hardware will be able to do this just fine and not building the software now would be stupid on Apple's part.

I think it remains to be seen what exactly this hardware can and cannot do, but more importantly what we are looking at 2 or 3 versions down the road. Unlike basically every other company that has tried to to make a product like this, Apple has a track record of not shutting down projects and having "hobby" projects that take a few generations to finally hit their potential.

Once the hardware manages to catch up, is smaller, etc it feels kinda nieve to think that we would remain stuck to monitors for computing. Is it guaranteed? no of course not. But I would not dismiss it yet based on how this guy is talking in the comments about the future. We saw a lot of the same dismissal of smart phones for most people's computing needs.
They may still use some sort of event/message system. Kafka is lower level than other sorts message queue systems and requires more work to get correct (dedupe, ordering, retry logic), but has great performance. It's often easier to choose a different messaging system though.
I think the focus on the $/GB is wrong. The main goal of Kafka is providing certain processing guarantees and connecting consumers with producers of events.

What Kafka is not for is dealing with enormous number of events or enormous amount of data. Not that it is particularly slow at it (actually, quite fast) but I see a lot of people needlessly try to push more data and events than they need and then complain they have problems.

One easy trick to deal with enormous numbers of events and amounts of data is batching. Just batch some number of events into a single event so that a consumer can pick it up in one go. Removes a lot of cost of transferring the event.

Too much data to transfer? Don't be stupid and try to transfer those huge documents through the Kafka topic -- there is no need for this. Just upload them to S3 and pass through a reference. Or even better, take 10k events, extract data, zip it up, push to S3, and THEN pass a single event that describes 10k large events.
(Not the same commenter) HWInfo64 can report your CPU power consumption. Some digital power supplies can also give power for specific parts, like corsair iCue compatible PSU's
Things are perhaps a bit different now than when Torvalds and Tanenbaum debated the issue on comp.os.minix over thirty years ago.
> There must be vetting at multiple levels of the process, or these use cases are negligent at best and malicious at worst.

You've got it exactly.

The problem is modern AI systems cannot be vetted because neither their creators nor their users actually understand how they work (yes, the mechanics are understood, but the emergent properties are not).

I believe we need regulations that prevent the use of unauditable technologies in a bunch of key industries, including banking, law enforcement, healthcare, etc. Basically anywhere where a person's rights may be violated by these systems.

We actually fought this same battle not too long ago with photo radar systems due to issues with their accuracy, and the result was mandated transparency (at least in some jurisdictions). These new technologies just supercharge the problem.
I mean that behavior is literally HN incarnate, so you might be exhibiting exactly that in this comment.
Didn't that happen from someone leaving a sink on or something, causing flooding and then the UPS batteries to short and explode?

I was there when someone at AWS accidentally unplugged an entire region.

Shit happens, it doesn't matter where it's hosted. People act like the cloud is infallible or something. You're literally sending lightning bolts worth of electricity through bricks of metal. Anything can happen.
That’s … reductionist, any voter that attempts to find a representative for a non-party line cause gets gaslit by rapid partisans about hating women or a marginalized group because its not their top cause guiding all voting decisions.

voters dont have control of their representatives either way
What's to stop Confluent/Kafka from simply implementing a feature like this themselves?
What are your thoughts on Fuchsia? Not QNX but definitely got billions behind it (until Google kill it that is).
Hi there, this is Aparna, COO of Zoom. We’ve updated our terms of service (in section 10.4) to further confirm that we will not use audio, video, or chat customer content to train our artificial intelligence models without your consent. Please take a look. https://blog.zoom.us/zooms-term-service-ai/
I was under the impression us-east-1 launched in 2002 or 2003. AWS was certainly a thing in 2004, at least.
> An interface which is self-documenting.

I wanna see you find the right dialogue windows in the control panel.

Would you know how to enable/disable IPv6 from your head?
How much (out of that $150 e.g.) does the developer get and how much does GitStart keep?
We are teaching math to kids "because it's important and is everywhere". Mostly kids believe us and do learn it in school...

Yet do we use that much of the math in our lives ourselves? Do we even have that much chance to apply the approaches and solutions we learned?

Most of the math is outsorced to devices and ready-made solutions. A lot of those internal details are too complex to EL5.

So if a kid did really crack the math at his grade, then instead of expanding it further, I'd rather try to find ways to apply that knowledge in life. Spot the uses around, make uses in projects. See how that math is fused in physics, well, really around us.
> That should rarely matter, because multiple users have to flag a submission or comment for it to become actually flagged.

That's what I thought. If you don't mind taking a moment, is there any rational reason by your reading why the linked article would deserve multiple flags on HN?

This may be conspiratorial thinking on my part, but if I was part of an influence voting ring, I would want to make this type of article disappear. If that's the case then the voting (flagging) ring might have just outed themselves to the admins, no?
rms is only seventy, unless you have information to the contrary we should expect him to live another few years yet!
That's one way to affect the gender ratio of your student body.

There's also a way to do it that doesn't involve giving one gender a boost in admission. Instead (1) try to get more people of the desired gender who are qualified to make it without a boost to apply, and (2) try to get more people of the desired gender that are accepted by multiple schools to decide to go to yours.

That's the approach Caltech took. When I was there in the '80s it was 85% male (it is 54% male nowadays). That was annoying and distracting for everybody. They made it a priority to get more balanced, and the approach was to work on the pipeline.

When I, a pretty average for Caltech male, was offered admission they sent me a letter and told me the deadline to accept and how to do so, and that was pretty much it. If I had picked another school Caltech wouldn't have tried to get me to change my mind. It would have just been "tzs didn't accept...offer that spot to the next kid on the waitlist".

If I had been a female, they probably would have sent a faculty member to visit me and my parents at home and try to convince us that Caltech was the place to be.

Same on the pre-application side of things. They'd send people out to meet top female high school STEM students and try and convince them to apply. For males you had to be really special to get that kind of recruitment.
This looks really cool. Does your API also support follow up questions and a longer conversations?
I was going to post the same example of cobalt in the Congo.
The French came up with a poignant term for this: "Autobesity"[1]

[1] https://www.theguardian.com/world/2023/jul/11/paris-charge-s...
The implications of this ruling are mind boggling. Simply doing business with someone who is committing a crime, even if you didn't know, is a crime by this logic. By extension any business using Salesforce is also now engaged with a criminal enterprise and thus criminals too.

Interestingly enough the BackPage prosecution was headed up by Kamala Harris to make it look like she was doing something about sex trafficking. I wonder if her finger is on the scale. It's all so stupid. She's good at that.
I’m of the impression that it’s relatively easy to sue, but that the municipality will just settle for millions and not fire the police officer lest they incur the wrath of the police union.
I've got an unfinished 8-inch mirror that I spent a month of evenings grinding... Someday I'll get around to polishing and building out a cargo-bike-collapsable structure for it.

A cool thing about DIY telescopes: You can get better results than a commercial mirror, because you can turn your time into quality at a rate which is not economically feasible for manufacturing.
> We already see skills atrophy around things like UNIX

Don't worry about Unix skills, worry about your AI skills. The first is only getting more automated and the second is growing and expanding fast.

> running on infrastructure that nobody understands

AI is good at writing docs, summarising, monitoring, rewriting - there is no reason the code base should be opaque. Also, we will be much better at picking up new skills quickly - force of habit, we will be better at grocking things with AI.
There won't be UBI. There's work and death. And if AI truly replaces us, it's the latter. I'm not trying to be cynical I'm simply being blunt about how systems work.

You and your environment have to "click together" so you live. In the wild, this means mostly surviving cold, hot, stay dry, find things to eat, and not be eaten.

In society, however, it means being useful to the system somehow, so you get access to other useful things the system makes, like air conditioners, housing, and food, ways to get around etc. If you're not useful to the system, the system may pretend it cares for you, but it doesn't really care for you. This is not up to the morality of the people in charge. It's up to the system. The system elects the people and tells them what to care about. The system is quite resilient. It can withstand certain amounts of welfare, corruption, crime, and so on. But only certain amounts. If you cross those certain amounts, what happened in 2020 with COVID handouts, and the subsequent doubling of prices of food, and so on, happens infinitely and suddenly money is worthless paper. Like Zimbabwe. So if you have somewhere else to run where they're not as stupid as Zimbabwe, you can be useful in that new place and live. If you have nowhere to run, as with a global UBI, you die.

Of course, people won't just lay down and die, they'll just have a revolution like the Bolsheviks did, and speak about how everything will belong to everyone, and of course resources will concentrate to those on top again, instead. With AI however, the overall trend would be you don't need the masses as much, so you don't need to placate most of them. They stop being useful. So revolution after revolution, new people will sit on top and promise it'll be different this time, in a smaller and smaller population.
94% of asians, 73% of whites, and 37% of blacks pass the "063 Mathematics" subject matter test. That's an absolute # of 24 blacks passing, yet every year the state's new black math teachers count is 100+.

https://www.doe.mass.edu/mtel/annual/2022resultsbycategory.h...
Is there a reason you're so intent on being a killjoy? Is there really an important point being made here? Don't worry, they do not falsely believe that they invented and built AWS.

This story is basically akin to someone who works at a restaurant saying that one day a celebrity came in and ordered a hamburger, and a photo was taken with the hamburger that ended up becoming famous, and them saying that they made that hamburger. It's just an interesting "I was a small part of something that became big" story. But thank god we have you here to make sure that that person doesn't go around telling people they built AWS.
Yandex co-founder Arkady Volozh updates bio, Russia shrinks to marginal mention
Oh, interesting, people created a GNU clone of Mach, removing the licensing problem that all but killed the project early on its life.

For the ones not in the know, Mach is an OS designed after the idea of "the network is your environment, not the computer" where it should make little difference if the resources you are accessing is on your computer or not. And "resource" here is really generic, meaning things like files, login information, printers and other periferals, CPU, whatever.

For some reason (maybe related to costs and licensing), people never adopted the idea... and insisted on reimplementing it with unreliable hacks and lots and lots of problems on top of every other OS out there instead of just having it on the OS itself.
There was recently an article about distributed systems that showed up here. (Harry Doyle: Christ, I can't find it. To hell with it!)

And the author made a very interesting point about message queues. Simply, any problem that could be resolved by a message queue could be resolved by load balancing or persistence, and, therefore, messages queues were actually kind of a bad idea.

There were two basic issues.

The first is that because of the nature of message queues, they're either empty or full. The second is that for many of the ways that queue are used, the unit putting the request on the queue in the first place may well be waiting for the response related to the request. So you've just turned an every day synchronous request into a more complicated, out of band, multi-party asynchronous request.

If your queues are not empty, they they are filling up. And queue capacity is a two fold problem. One, is that you simply run out of space. But, more likely, referring to the earlier point about waiting for a response, is that you run out of time. The response does not return fast enough to manage your response window to the unit making the request.

This is a load balancing problem. If the queue is filling you simply don't have the capacity to handle the current traffic. It's also a mechanically simpler thing to send out a request and wait for the response than to do the dance via a message queue.

The second part is that if you're throwing items onto a message queue, and you "don't care" about them, that is it's a true "fire and forget" kind of request and direct response time is not a concern, then what does the queue gain you over simply posting it to a database table? If the request is Important, you certainly don't want to trust it to a message queue, a device not really designed for the storage of messages. Messages in a queue are kind of trapped in no mans land, where the easiest way to get to a message is to dig through the ones piled in front of it.

They're interesting insights and worth scratching your chin and going "Hmmm" over.
> To add to this, unless you are compiling your kernel specifically for your machine, your kernel is going to be a bloated compromise of the set of drivers that your system is most likely to see. That means that you will have dozens, if not hundreds of drivers compiled into your kernel which will never need to be used.

I imagine there's two pools of Linux users: those that compile their own kernel, probably with only the drivers they use; and those that use distribution kernels, which have a small set of compiled in drivers, and a huge initrd with all the drivers. Neither one of those groups ends up with all of the drivers loaded into memory: the compile their own have a small set, the distro kernel people end up with only the drivers they need loaded; both groups have a relatively small kernel footprint.
Thanks for the recommendation. Unfortunately I do mostly prog / metal stuff these days and while the occasional synth sound can be had for free, a lot of my sounds come from either Helix Native / Neural DSP for guitar / Kontakt for drums. I'll take a look at LMMS.
It's easier to maintain a very fine-level of control, but only if users are prepared to invest the time and effort to keep themselves up to date on the software that makes up their system. Sure, that is probably assumed to some degree as part of being a power user, however alternatives like Arch and nixOS are capable of providing similar levels of configuration with a little more ease, at least in certain places.

> but once you've got it setup it's easier to maintain.

In general, this is not the case compared to more out-of-the-box distros like Debian, where upgrading is simply a matter of "apt update && apt upgrade".
Good point!

Also some cultures also show far less care than others (despite feeling the same way)

A lot of my Asian friends do not pro-actively jump into slack to not look stupid, but the moment you get on a pairing call with them the perception changes quickly as they are not as shy in a smaller group.
It's called a Chromebook.
I mean, n=1 of a guy that had a good experience -- n=roughly 28,000,000 with no health insurance at all. These don't seem like two sides of the same coin in my view.
That's lovely--really elegant lines.

Also, congratulations!