skysight-inc/HackerNews huggingface dataset:
I agree that this would be a good solution. I'm merely bringing up that it takes consideration. Also someone will need to learn the Secrets Manager and also learn credentials management for CI/CD. It's probably at least a day of work if you're not familiar with it.

Don't get me wrong. I don't think anyone should skip this step. You need auth for your datastores.
> Whoever came up with the concept of "Hot-Desking" should be launched on the next solar probe as heat shielding.

Haha, this is the funniest way I’ve seen someone express rage in a really, really long time :)
Oh - this was not easy, or cheap, that's fer sure. Lots of over anylising here. It's art, ya know?
Have you even looked at the guidance? There's not anything nefarious here. Just imminently reasonable stuff like: "By default, many container services run as the privileged root user, and applications execute inside the container as root despite not requiring privileged execution. Preventing root execution by using non-root containers or a rootless container engine limits the impact of a container compromise. Both methods affect the runtime environment significantly, so applications should be thoroughly tested to ensure compatibility."

They then provide an example Dockerfile in an Appendix.

I've looked through NSA hardening guides for AD, Linux, and many other technologies. They're helpful and imminently reasonable.

Do the NSA and CIA do dirty things? Yes. Should you trust everything they do? No. But you probably should at least skim the hardening document before you completely dismiss it because of your distrust.

Or don't even bother to read the document. Just look at the works cited section, which tells you a lot about the content of the article. Works are cited from: Center for Internet Security, Defense Information Security Agency, Linux Foundation, MITRE ATT&CK, Cybersecurity and Infrastructure Security Agency, Kubernetes.

The guide talks about the following:

- Scanning containers for vulnerabilities and misconfigurations
- Running Pods with least privilege
- Use network segmentation to limit blast radius
- Use firewalls
- Use strong authN and authZ
- Capture and monitor logs
- Periodically check your configurations and do vuln scans

It then points to CIS Kubernetes benchmarks, Kubernetes Security Technical Implimentation Guide, and CISA.

Where's the boogey man?
Right it will be a pain to find them. But once you do it should just be a config change. The date of the DST changeover has changed a bunch of times, including being on DST for a few years straight in the 70s.

If it’s not already configurable then it had to be replaced in 2007 when we last changed the start of DST.
Terrible article.
My cat does not seem to be aware of the arbitrarily changed numbers on my clock being different than it was last week when she's hungry and ready for breakfast.
Invidious is fairly easy to self-host, see https://docs.invidious.io/Installation/#docker-compose-metho...

I don't believe it's very resource intensive (though the recommendation is at least 3GB of RAM), so you may be able to run it on localhost on your laptop, or you could run it on some cheap VPS.
County and city also have powers to decide their local planning rules, so it will not be simple would be guess to have state level rule.
Also it's good when courts enforce poorly written laws as a forcing function to have law makers (legislature) write useful laws. Sometimes the laws as written are nearly useless
It's not really stated explicitly but it mostly boils down to wanting to have the benefits of the place being a college town without too many of the inconveniences of the place being a college town.
What does this mean, in practical terms? Will DST become permanent?
The complexity of Vulkan or shaders has very little to do with the fixed-function parts of the GPU. The complexities of Vulkan are around the realities of talking to a coprocessor over a relatively low-bandwidth, high-latency pipe. It's not unlike, say, gRPC or whatever other remote call API you want. So you end up building command queues so you can send a batch of work all at once instead of dozens or hundreds of small transmissions. And then need to deal with synchronization between those. And then memory management of all that.

Very little of that goes away as the GPU becomes more programmable / powerful. Rather it gets ever more complicated, as suddenly a texture isn't just a texture anymore. It's now a buffer. And buffers can be used for lots of things. This complexity really could only go away if the GPU & CPU merged into a single unit, which isn't entirely unlike Intel's failed Larrabee as a sibling comment mentioned.

As for shaders, those are just arbitrary programs. The complexity there is entirely the complexity of whatever your renderer does, compounded by the extreme parallelism of a GPU. So this complexity really never goes away.

For your core question, the problem is that fixed function hardware is just always faster & more efficient than a programmable one. So as long as games commonly do the same set of easily ASIC-able work (like render triangles), then you really won't ever see that fixed-function unit go away. But something like Unreal Engine 5's Nanite is kinda the productization of the idea of doing triangle rasterization in a "software" renderer instead of the fixed-function parts of the GPU: https://www.unrealengine.com/en-US/blog/understanding-nanite...
Not the same argument. Not all outcry is supported by the same level of reasoning.

Time zones boil down to "for consistency's sake, we cannot have an infinitely granular way of setting time across longitudes" and people chopped the world into slices. At the middle of each slice, noon is supposed to be noon and is denoted with "12:00(pm)". This is a sensible compromise between clocks changing by the second based on GPS coordinates and the whole world having the same time. " noon is when we decide makes the most sense logistically" is not the argument here, it takes the nuance out. Noon is when, at the middle of the time zone, the sun is midway in the daylight part of the cycle. This is the crux of it, not simply "we all decided". We all decided because of something. there has to be a basis in reality, otherwise society is just shared delusion and things go off the rails quickly.
The thing is, they'd F up no matter what change was made to the daylight saving rules. At least this time we have the hope that it will be the last time we have to worry about it.
This is the mechanism that I had in mind. It's actually a really good one if you have lots of concurrent reads and few writes because there isn't going to be any cacheline ping pong. With a more traditional read-write lock, even the readers write to the cacheline holding the lock, and that's a shared cacheline so it's going to ping pong around. By contrast, the generation counter is read-only to readers.

But consider: the generation counter effectively acts as a lock that locks out reader threads while the update takes place. It also serves to lock out other writer threads.

So yes, one can call that "lock-free" if one really wants to, but I find it more honest to just admit that it's a custom lock with custom properties.
Dupe from last year: https://news.ycombinator.com/item?id=28050750
Normally would never say anything about a name… but really? Strype? You are aware there is a massive payment processor/trademark called Stripe right?
Ah, interesting, thank you. As far as point (b) goes, it seems to work pretty well: I can’t recall an occasion where I’ve had traffic blocked. (I suppose in practice not many applications use custom IP-but-not-TCP-or-UDP-based protocols.) So could that same thing not be a solution to e12e’s question?
Sorry, permanently from here on in, we will spring forward and fall back, in accordance with the "Daylight Saving Time" custom, or permanently year-round we'll be sprung forward and using the "Daylight Saving Time" clock setting?
Not sure about the morning-person thing, but permanent DST would mean that on the shortest days the sun would rise at 9:18am rather than 8:18am. I'd rather the sun rise at 8:18am to help me wake up. I don't have kids, but if I did I'd rather them be walking to school during twilight rather than the pitch darkness of night.
Can you elaborate on the Trickle-up Economy point. What do you mean by that? Why is it damaging?
Incredible, really great work. Loved it
This is true in a strict sense, but essentially no concurrent code works if you don't assume that writes become eventually visible to all other threads.

Consider something basic like implementing a mutex: once a thread unlocks a mutex, it is possible in theory that no other thread _ever_ sees the mutex as unlocked, and spin on it forever, but such a system would be useless.

In practice, general purpose CPUs have writes become visible as fast as possible.

You won't find this behavior defined strictly in memory models, because how can you? These talk only about ordering and eschew things like "global clocks" and even if you had such a clock, how are you going to put a numerical bound on the delay?

Most will leave it as a quality of implementation issue and specify that writes become visible "eventually" if they say anything at all.
Unpopular opinion, I don't know what's the deal with these small keyboards... like you're not going to be able to do work on that long term.
This will affect people in northern latitudes far more. For me it would be the matter of 8am vs 9am.
> the user now has the choice to use a pointer or not

But any benefits of the packing are gone whether I make a pointer or not.

And either way, no nested pointers are involved. We’re not taking pointers to options in either case.
One smaller use case that comes to mind is for immigrants like myself. On an H1 visa, you are only allowed to receive a paycheck from the sponsoring employer, so you cannot do contract work for cash (stock is ok), but paying down debt might be a cool way to accept "payment" for services.
Aren't you basically still replicating the clock change? Everyone who goes to, works inside, or drops children off at the school will be less productive, at greater risk of heart attack, etc.

If we were really accounting for physical realities, we'd change our schedules by a much smaller amount every week or even every day, as the sun gradually shifts over time, instead of by an hour all at once. But nobody wants to coordinate that.

I think the only logical thing to do is have permanent standard time...
Makes sense. Back in the day, AMD did massive layoffs and then started to go up.
Important question.

Here's our launch announcement with the full answer: https://about.system.com/blog/announcing-the-public-beta-of-...

TL;DR Because the biggest challenges we face in the world — from COVID to climate change — are systemic, yet our data and knowledge are organized into silos. I believe this fundamental incongruity makes it impossible to think, plan, and act systemically. As a result, we are stifled in our ability to reliably predict outcomes, make decisions, mitigate risks, and improve the state of the world for everyone.

So, we built System. A new way to organize data and knowledge into systems based on the evolving relationships between everything in the world. A shared tool for systems thinking — and, we hope, a springboard for collective action.

We share much in common with Wikipedia, are deeply inspired by what it does for the world, and hope to be used alongside Wikipedia. Our openness and CC license, our use of Wikidata as the source of definitions, for example, are common. But System aims to explain how anything in the world relates to everything else — based on statistical evidence. It is not an encyclopedia.
I've seen this problem solved using exterior stairs in the back of the building.
Count me as one of those against it.

I'm all for not changing our clocks anymore, but DST is stupid. If you want to get up earlier and have more daylight in the evening, great, do that. If you want to get up later so it's not dark when you leave in the morning, sure, makes sense. And if you want to change your schedule as the year progresses to adapt to the seasons, I'm with you.

The real problem is that we have this weird idea that our whole society has to operate synchronously. And hey, I get it, some groups of people do have to coordinate with each other. An assembly line won't work if people show up whenever. But most people aren't in that situation and even that assembly line doesn't have to be synchronized with all the other assembly lines in the country. Heck, it might even be a good thing if we didn't all drive to work at the same time...

We have to agree on what time it is so that we can coordinate, and as long as we're doing that, let's agree on something that's not a lie. If we're going to meet at noon, the sun should be straight over head, damnit.
Most of this guidance can be checked over by anyone with basic competency in the field, and cross referenced against documentation - in general a lot of the guidance from government security agencies is focused on solid and robust design principles (isolating things, not reusing things, turning off specific functionality that exposes risky attack surfaces, being aware of unusual or non obvious defaults).

Not running containers as root is accepted by pretty much everyone I'm aware of as a 'good move. Same for building images carefully and preventing filesystem changes at runtime. Same goes for using sandboxing, syscall filtering etc.

This is a bit different from giving you a series of black box parameters and telling you to blindly rely on them. (And even then, DES being hardened against differential cryptography shows that's not always a bad thing, though more recent examples show the opposite can also happen).
Google has history of banning company accounts because they have a contractor who has previously been banned by Google.
For Hangman, I started a game with the word as "panda." There are two "a" characters. The person who guessed "a" only revealed one of them.

The rules of Hangman are that every letter guessed reveals all instances of that letter in the word.
> If it’s not already configurable

It's not.

> If it’s not already configurable then it had to be replaced in 2007 when we last changed the start of DST.

Yup, both these systems are about 10-15 years old.
> Hopefully the welcome screen (post video) more clearly spelled out the product purpose.

Oh, if that was supposed to show on mobile, it didn't for me. Or maybe I closed the tab too soon since it said that no mobile experience was available and that I could watch the video instead (figuring that, after it finished, that was all for now).
> it should be possible for a society to agree on things just starting an hour earlier

How would that ever work? I can't think of a single thing requiring near that level of coordination that we are able to do. Automatically changing peoples closed seems infinitely easier.

I understand some people don't like it, but don't pretend there is another way to move everything around. People are barely willing to do it as is.
One of the most common misconfigurations I've seen is improper secrets handling. I'm glad to see it called out but I wish they would go into a little deeper detail on detection and remediation. Overall looks pretty good! I'm excited to have some baselines for K8s.
I think what pulls Millennials and Gen-Z together so much compared to other generations is the Internet. We're connected in ways no previous generation has before.
But it also means people are implementing modified ISAs (such as this CPU which has a non standard V extension) which sucks for compatibility.
I would love having more sun after work, but I don't know that it's worth the tradeoff of safety. On the shortest days the sun rises at 8:18am for me, so I usually start biking to work shortly after sunrise. On DST that sunrise would be 9:18am, well after my daily standup time. I'd be biking in twilight, if not nautical night. I already hate biking in the dark for safety reasons, I'd probably start driving more.
I appreciated it. I spent a little time looking at a map after reading it. The geographical, cultural and political relationships between India and Tibet are not discussed in the US as often as China-Tibet.

Threaded forums are well able to accommodate these kinds of small side discussions, too.
10 minute adjustment on the first of each month.
Also, it'll give that privilege to everyone else who doesn't work standard 9-5- it helps those who work 8-4, and 7-3. It doesn't help 10-6ers, but those are almost universally office jobs (who generally tend to have the luxury of windows).

It's quite difficult to understand just how much no sun in the morning sucks until you've had to live through it. On Standard time only, you'll go down into the artificial-light-only place in the dark, and you'll come out of it in the dark, for half the year.

Switching permanently to DST means this sector of the population gets an opportunity to see the sun after work before it goes away even when the sun sets at what would normally be 3:30-4 PM. They aren't going to see the sun in the morning no matter what anyway; they're waking up in the dark even if DST is permanent.

Sure, people will complain about the purity of "but 12 means noon", but most of our modern systems of measure have no human-scale base units and everyone loves those, so there's no reason why time should be based on that either.
Interesting note, many states already use standard time, such as AZ. But, it is against Federal law, for some reason, to use daylight time. Utah, California, and a few others have already voted to switch to permanent daylight time as soon as the federal government allows it.

The states that have this law waiting for the fed asked it to be reviewed.

I wonder if daylight time will be the new standard but your state can opt for standard time if they like.

This passed the senate today but it still needs to go through the house and president. I hope it’s smooth sailing.

Aside: I’m curious why states care about the federal law here but don’t in the case of THC legalization. I think it’s legal with (at least) a medical card in UT and CA.
There’s something to be said for the bodies circadian rhythm with the sun and the time their job or school dictates they need to be there
Especially when the domain is locked and you cannot get access to your account
Another faction would be the developers that have to deal with the time changing. Would just be easier to change at a personal level than changing time itself. Arizona doesn't do alot right but no DST is one big one they do. Times of work/events/appts/etc change, not time itself.
> Or should we just wake up our young children well before dawn and drag them off?

We already do this, FWIW. It's terrible for them but I guess we do it out of convenience for the bus drivers and parents. Changing clocks twice a year hasn't and won't address the problem, unfortunately.
... and another sub-faction that thinks time-zones are also a horrible idea.
There are still demarcations where we arbitrarily decide to switch over an hour. Seasons change, people live at different latitudes. Noon is not always "noon"
You seem to use these terms interchangeably - people who do the absolute bare minimum, mediocre-ly poor but not egregiously bad performers and sub-par, while I think they are all different.

Every employee is either sub-par, at-par or above-par. If you perform the minimum to not get fired, you are necessarily doing what's expected of you, you're at-par (maybe you wont get promoted but you are doing what's expected of you), and if you are doing more than you need to then you are exceeding expectations.

This thinking that you can do what needs to be done to not get fired, but still be under performing just tells me its a bad manager(s) with no clear expectation setting and communicating it and if anyone is clearly sub-par making sure its communicated early with clear expectations instead of a doing a mass layoff to try and hope fix it.
No government is telling me what time it is!
I already did and passed the recruiter interview, waiting for the online assessment part.
Specifically, the US national legislature is failing. /State/ legislatures have no problem passing laws, some really good, and some absolutely terrifying.
AWS launches “Cloud Quest: Cloud Practitioner”, an open-world RPG to teach AWS
The guideline was updated this month but released last year. That dupe link probably has a lot of relevant discussion.
Frankly that'd be better than the status quo. If there are a million the same games with a different word as title from the same company, it's easy enough to show this isn't legit. You'd have to do at least a tiny amount of effort and raise the cost of registering whole dictionaries.

Also, I'm not claiming to have a perfect solution for enforcement, just more generally that I wish we'd try to do something about it.
This is factually incorrect: claiming Chan Buddhists do not believe in reincarnation. On the facts, wrong.

The Buddha taught reincarnation and all major schools essentially follow his example. This includes Chan Buddhism. It may not be emphasized or really suggested as a topic for reflection - but if you are asking point blank "Do Chan Buddhists accept the idea of reincarnation after death, as the Buddha taught - or do they teach reincarnation as wrong view", the answer is "they accept reincarnation."

Source: look up Chan Buddhism on Wikipedia, or just Google search it. Not a single result affirming that Chan Buddhists teach the falsity of reincarnation.
I wasn't saying what you did was easy or cheap, but wondering if it might not be easier for you to have made it this way than programming it, or that despite being expensive to make might it not have been more expensive to build as software and if software would have been able to achieve the same things as easily.
There's a lot of developers that misuse/shouldn't use any powerful feature. If the solution is to give them a nerfed language, then you also nerf it for the users that would use the feature well in productive, useful ways.
Depression or Bust
Either you empathize with someone and succeed looking at things from their perspective. Or you are the jealous jerk hoping to see them fail.

There is no middle ground, chose who you want to be. Empathy is a lot of work and it hurts too!

If you did the first thought would be something like: "wow, that is hard. He/she must be grinding ways to fail and has to act upon each of them, plan their time and chose their actions carefully. Even if they get everything right success is not guaranteed or perhaps, if there is enough ambition, not even likely."

What the other wants to hear when hard things are on the schedule is a summary of their accomplishments and perhaps how this project is going to present exactly the challenge that should come after it.

Of course one should build walls to keep out the insensitive jerk. Avoid him if needed. Their world is so dull because no one ever shares that what makes them tick with them. A stamp collector will never share with them why he collects stamps. They will never become a stamp collectors.

The jerks world is static, without change and they think they prefer it that way. How dare you suggest there could be more.

But jerks they are by choice. It is no different from telling a homeless person they might never find a home. An unemployed person they might never find work. A beggar that they will probably starve. I think you will never be able to pay your debt. You will probably get back to drinking/drugs/smoking if you try to quit. etc etc

hey, I'm just being objective here! I'm a realist you know!
Lol I wonder how long until it gets scrapped
The sibling comments explain why the link contains sound advice, so I'll just add this: you are ultimately responsible for the security of your Kubernetes cluster, whether you get your hardening tips from william1964 on Stack Overflow, or the NSA.
Yes, Black Hats know about security.