skysight-inc/HackerNews huggingface dataset:
Well, I won't contradict your personal experience, but I will say that I worked on gmail delivery for six years and if during that time it had ever come to light that any message had been accepted and not ultimately disposed of in some way, that would have been P0 and dozens of people would have dropped everything in order to root-cause and remediate that.
Does not work currently
There are also launches moveing forward or show up out of knowwhere.
As outsider I thought that uncured referred to essentially some form of fresh pork belly.

So it comes to the usual not using specific thing, but something containing it. Like no added MSG...
Sorry but I don't find many differences between large capitalist corporate hierarchical structure and the SSSR one. Do you?

Just stop subsidizing large businesses, revert regulatory capture and give incentives to start new businesses as coops for instance.

I get that most people have been brought up in the "greedy by default" mode, but that's no excuse to give up and just transact ourselves to oblivion.

Let's rediscover different ways of association.
Of course hahaha, but it is rather annoying to do so. Nevertheless, that's exactly what I did :D
Hmm. I think I've primarily experienced the really dark side of guess culture, so I appreciate your framing of it as a desire for understanding when it's in a healthy context.

I've experienced it in the contexts of narcissism and borderline personality, where the underlying thought is, "I am so obviously the center of the world that anyone with half a brain who's paying a whit of attention should to intuit my needs without my having to speak a word. If I have to speak, you have already failed." And anyone who failed was punished, sometimes intensely.

Ask culture, for me in that context, became about being able to exist as a separate person and express a boundary. I'd much rather put the cards on the table, find out we want completely different, even opposed things, and work from there, than deal with the power imbalance of one person's assumption that anyone who isn't reading their mind is an idiot.

It seems the virtue, as most of the time, is in the mean.
https://archive.is/KMM4Q
But US states can't regulate interstate commerce. So it's moot.
Microsoft pulls article recommending Ottawa Food Bank to tourists
It seems like a shorter session expiration time could help with analysis because you don’t have to worry about bugs that were fixed long ago. The longer the expiration time is, the farther you have to go back in history when thinking about how an old bug might have been exploited.

(Similarly for key rotations.)

This might affect how long you want to retain logs?
perhaps some signal that is only viewable locally, not globally.

The equivalent of the siren and lights on an emergency vehicle.

Wait...

Oh.
Of course HN works fine, if it didn't work fine it'd be fixed by now. "Working fine" is an extremely low bar for any site. As a developer you will still want to avoid quirks mode because it just makes your life harder for no reason.
Why do people keep repeating it... Python doesn't have a REPL. It has an interactive shell. Read-eval-print-loop relies on being able to feed what you print back to the read function. Interactive shell doesn't need the ability to print code: it prints whatever information a function wants to print (often times nothing).

In Python sometimes you can feed back the results of a function into some other function (when you are in the interactive shell), but usually they are nothing like Python code...
That's been my experience as well. EU4's Linux-native release has issues with scaling and cursors on ultrawide monitors. Proton version is flawless.

There's been quite a few cases for me, like Star Citizen for example, where games perform significantly better under Proton with DXVK than it does on Windows!
Earth overshoot day is not a serious movement.

https://www.newscientist.com/article/mg22029445-000-admit-it...
PostgreSQL Extension for ULID
Notably, SpaceX is making no visible effort to synthesize methane for their cans. The only gesture in that direction is an announced plan to buy a pre-fab methane refinery that could possibly be adapted to run Sabatier; but no hint at a solar farm to power it, or a place to put one. I guess they could build one across the border in Mexico? CH4 for Cape Canaveral is a separate problem. More likely the refinery will just purify mined LNG.

Solar and wind farms supplying international airports would probably need to send power via HVDC transmission lines. But, yes, the airports will need much more than just overage from the farms, and probably booster shipments of LH2 from farms in the tropics, besides. Imagine how big must be the project of refining, transporting, storing, and distributing kerosene to gates, today. Yet it is made almost invisible.
There's a "pirate" port of NTVDM to 64-bit Windows (from leaked NT 4.0 source) so it's certainly not technically infeasible: https://github.com/leecher1337/ntvdmx64
Clearly missing the point. The OP mentions DOS, so this was the mid-90s. OpenBSD didn't exist (Theo hadn't burned all his bridges with NetBSD yet). There were NO updates. You bought software, games especially, in a shrink wrapped box at a brick and mortar store. Most people outside universities did not have internet access. If you were an extremely privileged few, you could download small patches from a BBS or online service but this was extremely rare. You got what you got. The development model was different. It had to work under any circumstances. There was no "we'll fix it in the next sprint!" and push it to the app store. Developers had no way to contact their customers.

Regarding that hobbyist OS OpenBSD, where the developers care about nothing besides security, there were no proprietary application packages available. Most retailed applications in those days ran on SunOS/Solaris or HP/UX.
Really, the issue here is that security is never treated quantitatively.
At least in my experience - are there examples of quantitative security?

In some sense, the problem is that the goal is zero controls breaking, but of course, that also provides no information on security. Intuitively, it would seem that parameterizing security (in a diagnostically useful way) would also require a number of quite different measures. For instance, it matters who (how sophisticated and motivated) your attackers are. And some of the parameterization would be based on use - every time you force someone to type a fixed password, that password is more exposed. Combining all these quantities would just be Bayes-based.

I think an exercise like this could be instructive. For instance, short sessions mean more authentications and both usability and failure modes. But they also mean that an attacker would need to wait until the next session, or have a smaller chance of hitting a session. Again, these are quantifiable, at least in rough terms. And this kind of analysis does expose some additional questions: eg that short sessions make no sense without guaranteeing the security of the client system (ideally by reinstallation from known-good reference).

At least in my experience, "security people"
What Figma’s Dev Mode Means for Developers
I think it's less that people don't actually want to know than it is that people don't actually want to share. But I'm from the Midwest, originally, and that's just kind of how we are.

Expanding on this just a little bit... I think that, in the Midwest but I'm sure in many other distinct American cultural regions, there's a sort of shared, but subdued, understanding that each of us is uniquely going through some shit. We answer the way we do because we don't want to trouble others with said shit.
It's how "innovation" works. You get a new supposedly "cheaper" product that's like the original thing but cheaper because of questionable advances in either science or engineering.

That cheaper product isn't actually better in most cases, it's filled with poorer quality magerials and lab engineered chemicals.

The working poor then buy it because it looks like the original product. Except it isn't. Its filled with questionable chemicals and industrial processes that have an unknown effect in the human body.

See the replacement of lard for seed oils and how the obesity epidemic came from that. Beef lard which was once a cheap cooking oil is now an expensive premium product.

What ends up happening then is the original product becomes a premium
product and is priced accordingly.

Since America doesn't make anything, the only thing we export in significant quantities are food stuffs, especially meat. That meat gets sent abroad to places like China where they make more money than you and are able to afford the original product you are now priced out of.

So you end up eating grasshoppers and lab grown mystery slop.
The US can't paint a few BRT bus lanes. Good luck building effective dynamic routing systems.

We've had self-driving buses since 1875, they're called trams.
Hmm for this example I would be more inclined to use an output parameter rather than generics

func Request(req, resp any) error {
// send request (http, etc)
b, err := json.Marshal(req)
if err != nil {
return err
}
log.Printf("sent request %+v - %s", req, b)

// read response
if err := json.Unmarshal([]byte(`{"success": false, "error": "invalid login"}`), resp); err != nil {
return err
}

return nil
}

But I kind of agree it's nicer to use a return value rather than an output parameter. I'm excited to see what other new uses people come up with for generics!
Turns out the 16" Framework can have an external battery, they designed the connector to also support that.

https://www.theverge.com/2023/3/30/23612467/framework-laptop...
The Linux world would benefit strongly from having a much bigger commitment to backwards compatibility in foundational libraries. Obviously there is nobody who can force e.g. OpenSSL to keep supporting old versions or to provide them as wrappers over the latest version, or to force GTK to keep around working versions of libraries exposing all interfaces dating from GTK 1.0 onwards. But if we could have a project to do just that, that would be great. We all want people to move with the times and adopt new versions of their dependencies so security exploits can be patched, but right now if you're writing software for Linux, either you package all your dependencies with it (forever calcifying all security exploits), or you keep on top of all updates of everything you use, or your software simply won't run within a couple of years. The open source community lives and dies by the ability of users to run existing software. Effectively continually deleting open source software from existence, while windows keeps supporting every single program written since 30 years ago, means we're always falling behind in usefulness. There ought to exist an organisation dedicated to maintaining old versions of widely used system libraries either in their original form, or as wrappers over the new versions (to the extent possible), so that people can rely on their existing software. Since we're talking about open source, that would mean maintaining the development kits as well, so old source can be built on new systems. It makes no sense to just let all this work rot, it is our greatest treasure.
Yeah, humans leaving the planet and flourishing.
this is a gross oversimplification

anyhow is the most commonly used crate to have type erased errors(1), nothing more then that but also nothing less

this means when returned form a library a Result<_, anyhow::Error> _is often an anti-pattern_ (often not always!)

but if you write an application it's pretty common to have many many places in the code where you can be sure that no upstream code needs more fine grained error handling (because you workspace is the most upstream code) so using anyhow is a pretty common and convenient choice

Though it's not unlikely for anyhow to fade into being mostly unused in the future with further currently missing rustc/std features, through not anytime soon.

But luckily this doesn't matter, due to how `?` works you can trivially convert errors on the fly no matter which (well kinda, there is an unlucky overlap between orphan rules and From wildcard implementations in the anyhow crate, but we can ignore that for this discussion).

(1): It's basically a form of Box<dyn Error + Send + Sync + 'static> which also has thin pointer optimizations and (can) by default include a stack trace + some convenience methods.
Just one for each then:

https://www.reuters.com/legal/elon-musks-2018-tweet-tesla-un...

https://www.reuters.com/article/gawker-lawsuit-frankel-idUSL...

Or maybe you like tax evasion better:

https://prospect.org/economy/one-weird-trick-force-billionai...

And no, Thiel wasn't convicted of anything. But in my view this was a complete perversion of the law. And that's taking into account that I think everybody associated with Gawker is scum.

Billionaires should pay their taxes rather than avoid them (what a term, it's just a spin on having enough money to be able to buy your way out of paying tax like everybody else) and they should not be able to use the law as their personal attack dog.
There are little (to no?) situations where su has a good reason to check wheel.

You either have the password, or you don't have it. But not something in-between.

Outside of any ideology, in a scenario where you use su to become root, it's a very odd choice to link the wheel group to su;
because if you know the password to the "root" user, and you have physical or remote access to the computer, you can likely just login as root.

And if you can't, then it means you actually needed sudo su, not su.

Those who actually need to be root, usually use sudo instead of su.

In the other cases, if you just need to switch user, then no point at all to refer to wheel
> No; you simply abstract the underlying subsystem’s exceptions in your own types, the same way you do with any other type.

That's all very well as long as people actually do that. It doesn't always happen in practice. And even when they do, the abstractions are likely to be leaky ones.

> And yes, “railway oriented approaches” can absolutely do this.

How? Please provide a code sample to demonstrate how you would do so.
Basically, su vs sudo. Do you want any user to be able to become root, if they know the root password? Or do you want more control over the process?
Oh, where was this when I really needed it a few years ago...

I was playing an old MMORPG called The Realm. It's been live since 1995 and ran until just a couple months ago. It only knew how to run in 640x480.

I tried to write a program that would create a scaled up version, but it didn't work well, especially since the game would create child windows for certain UI elements. I was writing it in C, which isn't my strongest language, simply so I could call Win32 APIs more easily.
Apple employs “Release Managers”, where a single person is ultimately responsible for deciding which features ship in new projects.

Apple also, due to the hardware business, adheres to a release schedule where features must all be consolidated onto single branches (“convergence”), rather than letting individual teams ship incrementally.
No need to bring in a distracting discussion about private vs. public health system. In Europe the public health systems are doing terrible, too.

Things I've been told by doctors in USA and Europe: "Hospitals are full of obese and old people." "A significant chunk of the budget goes to a small fraction of extremely unhealthy people who keep coming back."

Boomers are getting really old and are starting to overload the system. Anything done to make them healthier counts.
I strongly feel this article misses the point and ends up at a harmful framing instead.

Consider the example in the article: "all the family members insisted we don't drive up to visit our grandmother and see the city instead, we did it anyway, everyone was glad we did".

Or the next example: "with guess-culture people isn’t as simple as asking people what they want to eat for dinner, because they will not tell you what they actually want to want to eat for dinner."

This person, imo, deeply does not understand what is happening in these situations. They have a model of other people as "wanting something but not being willing to say it", and then they solve the puzzle of figuring out what it was, and the other person appreciates it. But, IMO, those people didn't strongly want something one way or the other. They're resisting an unhealthy dynamic: that the writer just wants to know what someone else wants for dinner, but doesn't even want something for dinner themselves.

What others are doing by not being willing to explicitly state desires is they're refusing to play this game of telling you what to do. They're doing this because it really doesn't feel good for someone to repeatedly ask you what they should do. The asker degrades themselves by pawning their agency off on someone else, and spending time with them begins to feel like hanging out with a robot: soulless, scripted, perfunctory.

That is: when you ask for permission to visit your grandmother and then do it because people said to, or don't do it because they didn't, you haven't demonstrated respect or kindness or love; you haven't acted human at all. You've just performed a mindless duty. Whereas if you decide to do it yourself, because you chose to, then you've demonstrated something.

People are shirking at telling you what to do because they don't want to be part of an icky transaction where somebody constantly hands away their agency. They don't want you "guess", they want you to stop asking for their permission to exist.

edit: I realized there's more in the article about the workplace and it's wrong too! This is not healthy at work, but not for the reasons the article thinks.

A person who goes around trying to get somebody else to tell them clearly what to do, and never gets that and therefore thinks they're having trouble with "ask culture", is a drain on the organization, because the amount of work that gets done is often proportional to willpower. Or call it "initiative" or something.

If you're leeching off other people's agency to do anything, then you're draining their willpower and not helping much at all. Likely they're totally exhausted of it and don't want to tell you what to do anymore. Whereas if you start injecting willpower and agency into the system the whole organization will pick up and run with whatever you do (or course-correct if it's wrong, etc).
No, because the average crypto bro will get tricked into thinking anything is a good idea and secure when you mention 'blockchain'.
So it only requires 40% of all power produced by California, Oregon, Washington, and British Columbia combined [1]? For a few minutes? No problem then!

Jokes aside, I don't think there are any interconnectors on the planet that can handle that amount of power for even a split second, let alone the infrastructure to supply it for minutes at a time to a single location. The biggest grid interconnectors in the world cap out at a few gigawatts.

[1] https://en.wikipedia.org/wiki/Western_Interconnection
Very interesting. I think it's accurate, and I hadn't seen that perspective before.

I personally operate mostly in the ask culture. But if I meet you, I don't know if you're in the ask or the guess culture. And it seems to me that I kind of have to operate in the mode of the guess culture in order to find out which you are.
> Migrating the SMD flash/EEPROM chip shouldn't be too hard.

Well, good luck then.

> The discs spin up but the controller no longer communicates with the host

Now this is strange, if the controller would be dead then there would be no spin-up. If you hear the heads working than the controller is definitely not dead.

You tried to search forums dedicated to data recovery with your exact P/N?
$4500 USD to start. Wildly expensive for such a simple device.
The good thing is the game is already fun to play :)
> What is special about the 'wheel' group and what is su even "checking" in the first place?

By convention, "wheel" is a special Unix user group that determines who can use "su" and "sudo". Most "su" and "sudo" implementations allow the sysadmin to make their use exclusive to the trusted users inside the "wheel" group. In most systems, it's the default setting of "su", and optional for "sudo" (given as an example in /etc/sudoers).

> if someone has the root password, can't they change what groups they're a member of?

No. If "su" is configured to be "wheel"-exclusive, you can't log in as root even if you have the password, because you cannot use "su" - unless you have direct access to the system console that allows you to type "username: root", which is almost never the case on servers that disable remote root login.
This and when that person is a manager, yikes
The places where housing is the most expensive are the same places where people who cannot afford housing are forced to commute from somewhere else. Commuters don't get to vote in the place where they work; they have to vote where they live.
This, and some of those areas will be less likely to stay that way; flooding one year, drought the next. If it were consistently one way, it'd be easier to adjust.
Best way to block people on Twitter after this: delete Twitter.
It also can just come back down into the ocean, which doesn't really do anything useful if you're trying to grow crops.
Apple is not even on the same "giant" shelf as Windows, so the circumstances are not similar either.
A front engine car that acts like a mid-engine one? Capable of under 7 minute Nurburgring lap times yet street legal at the flip of a switch. This is a masterful piece of engineering that Ford will use to compete with Ferrari's once again at Le Mans.
Azure AD can be a bit Microsoft-themed and startups and their SaaS providers who are startups half the time often are in the gsuite ecosystem. AAD probably works but okta is easy.

Jumpcloud got breached badly recently. Okta has as well but their breach wasn’t the same.

Generally with IDPs, worth going with a gold standard that works well. Okta is that
I think its compelling, because in theory an animal has to convert biomass into a lot of tissue we don't consume or use. It will probably also eventually be possible to grow meat with highly desirable properties in terms of texture, fat distribution, etc.
Whichever has the best IntelliSense/LSP support for the top 5 TIOBE languages:)
>Step outside of the software bubble we’re in and I’d guess 80% or more people would prefer a world without Airbnb.

I have, and the ability to travel (affordably) seems fairly important to working class folks. The people I've seen complain about AirBnb are the same sort of people who sneer at Ryanair - definitely not "the masses".

Then again, things may be different in the USA. I've always assumed the 40 year old man who has never seen the ocean is some sort of a ridiculous stereotype, but who knows.
They would be Monsanto, Tyson foods, any Argo business, and pretty any company in this list https://indiebio.co/companies/#

Select food and Ag.
> Tesla is consistently in the top of EV drivetrain efficiency for their models

From your link this doesn't seem to be true. The short range, non awd model 3 has great efficiency. Other model 3s are also good but clearly not anything particularly far ahead as there are a bunch of other models from other manufacturers with similar or better efficiency.

Looking at other Tesla models makes it clearer that they aren't anything particularly special. Even the model y, which is basically model 3 with minor body tweaks is basically middle of the road, model s and x are even worse.