Yes it is, it hacked Artifactory to get to Hugging Face.

They are not.

Developing modern 0-day zero click RCE exploits chains like those developed for iOS is far more complex than hacking to generic company servers

It's completely different scale of difficulty factor. Not a single documentated case of of any AI tool developing such exploit exists

There is a reason why those mobile 0-day exploits are sold and bought on exploit gray market for as much as 10-20 million dollars each

Why?

I think T-shirts are automated, that's why they're so cheap. Because it's a very simple construction.

They are a simple construction, but I'm not sure I've seen any evidence that their construction is automated.

I'm sure they can't automate shirts because the super cheap ones somehow always are Made in Bangladesh. If they could use less human labor they would make them somewhere else.

I believe socks can be fully automated and are mostly made in china.

There is a startup called Unspun that wants to make many types of clothing production fully automated by weaving the complete end product in place. Similar to how socks are woven today.

The current way to make a "finished" clothing product is called "whole garment knitting". Only two companies make machines that can do this; designing the garments is a pain with the current software stack. Most clothing is "cut and sew" -- you make a simple sheet of knitted material and cut and sew a garment out of that sheet. It is wasteful and heavily reliant on cheap labor.

Only worthwhile when you have low competition and a lot of sales in the market. By default, Americans get the same car prices that Chinese people get.

Which pissed off American car companies so much they banned imports.

Lockheed has refused to share missile plans with Ukraine on the grounds that Ukraine could make better missiles for cheaper and ruin Lockheed's business.

If they had said national security grounds, it would be understandable. But they didn't. They said American manufacturing is too inefficient and the only moat is keeping the designs secret.

That doesn’t change the fact that it’s minimum wage for the location. Doesn’t matter if they earn more than a highly skilled professional in a different country, it doesn’t change the skill set.

FWIW though, I rarely had bad experiences with airport staff. They are just trying to do their jobs in a hectic place and don’t intentionally make our lives difficult.

That it's a near minimum wage job is not actually the fact though. Even the minimum starting salary for an entry level TSA position is higher than the highest minimum wage of any city/county/state in the US. The median TSA salary is also a hair above the median of full time salary in the US.

For the most part I agree most are at least neutral though. I.e. they are there because it's a job, not because they hate people or love people and this job was the way to do that. It's just the ones that do tend to really stand out for people.

TSA are not general workers, they're not the subject of this thread. We mean baggage loaders, ticket booth operators, the people managing the boarding, etc. They're making about as much as they could've made in Amazon warehouse. So their attitude is about the same as at Amazon warehouse. And for their employers, that's okay because it's not like they're going to lose any business due to bad customer service. Commercial flying is the worst it's ever been, and yet there are more passengers than ever before.

Probably the lowest paid job where you have to wear a full uniform and people’s lives depend on you (at least, that’s the expectation)

If you have a central database why do you need atproto?

To stream dns changes from site owners to dns servers. If you want to change a record, you post the change on atproto. DNS servers everywhere just subscribe to the jetstream. That way anyone can run a fast, local dns server which is kept up to date automatically.

How fast can I change my DNS records?

How fast can you post messages to Bluesky?

You could however choose to maintain a fork. If you had time. Few people do.

So change it back when you have a dodgy driver to deal with

You could even generate a bloom filter for every block, and when you have a full block of bloom filters, write them out to an index file.

My personal idle walking-with-dog kind of design was a linear binary record file with regular marks letting you resynchronize where you are (and stamp cryptographically) with minimal seeks, and separate indexing files with bloom filters and the like. If the indexes are corrupted or deleted, they can be reconstructed from the main log, main log is single-writer/multiple-readers with no locking in any form necessary, and easier to survive kernel/hw failure

systemd is not a collaborative project. It is Lennart's personal cathedral project and you can take it or leave it. That's fine for Lennart, the question is if it's so bad then why are the rest of us taking it instead of leaving it?

Probably because the overall impact is not as bad as extremely vocal people on GitHub and HN would have you believe, and more people like systemd than dislike it.