skysight-inc/HackerNews huggingface dataset:
This is one of the more minor issues that puts me off getting an electric car at the moment. Why do I have to sign up for an account and download an app to charge my car? I can see the app being useful for being alerted when it's done, but that should be an optional thing.

It needs to be possible to just turn up, swipe your card and start charging (with some ability to limit how much you charge up). This needs to be as close to filling up at a petrol station as possible.
Pretty much this. I highly suspect this is just a matter of advertising chasing ROI.

Firearms, ammunition (if you can even find it), plate carriers, plates, optics, NVGs, holsters - all of it is selling for at least 200% what it was one year ago right now. Everyone running ad campaigns is seeing ROI > 3 and dramatically increasing spend.

Once bids rise to the point that ROI is normalized, we'll see less of this.
probably what's more likely is that with a democrat president, gun companies are pouring money into ads to really juice up already high sales.

(generally speaking, people rush to buy guns whenever the specter of gun control comes up, because they think that'll be the last chance they get.)
I’ve got an iPhone, it’s one of the most powerful computers I’ve had. Unfortunately it’s not super productive, mostly consumptive.
The Founder’s Guide to AngelList
The sax can be a demon to play properly, it will warm up over the course of playing so you will end up going flatter and flatter as you play longer but you can correct for that with your embouchure or alternate fingerings.

If you can re-tune (fourth line 'F') after you've warmed up the instrument. You do that on that F because it is roughly in the middle of the range of the instrument meaning you'll be off the minimum on the other notes. If you tuned it on the highest or lowest note the other end would be off considerably.

The sax is a wonderful instrument but it is definitely a finicky one, I've never found one that had all the notes in tune when played without corrective measures, and I'm not even sure that it could be done, the flexibility you get in making it go sharp or flat on purpose comes with the price of having to correct almost every note you play.
It's not GNU's `sudo`, it's under an ISC-style license, and is maintained by an OpenBSD developer, so it's closer to "BSD's sudo" (though OpenBSD has been shipping `doas` instead for a little while now).
Even in the literal sense revenue does not imply the absence of toxic waste. Indeed, historically speaking, revenue has been strongly associated with toxic waste.

I don't mind expressing this opinion. There is nothing anywhere in the GNU project which should be emulated, except the license.
I don't get all this, especially part 2 seems mathematically dense. But mainly I don't get the premise:

> but we won’t use any index gymnastics or explicit rank-2 tensors; just four-vectors.

For me the whole point of tensor notation is the power of indice gymnastics. I'd love to know the motivation behind this before spending time understanding.

My own notes on covariant notation on this subject: https://0x5.be/physics-notes/four-vectors.html
Nice finds. I would agree that that's more arguably a bug in libc than in doas, but also note that the startup code for any language has to consider this case. As far as theoretical operating systems are concerned, this is a consequence of the System-V ABI, so any OS compatible with it would have the same issue.

As for the integer overflow case, it's also highly unlikely to be exploitable, even if it were unsigned - the system would have to, as I'm sure you can infer, have tens of millions of rules before this was an issue. It's quite within the realm of reason, in my opinion, to declare this an acceptable trade-off. The rest of your explanation shows that even if this weren't the case, the bug wouldn't be exploitable.

Anyway, I like your comment, but I'd recommend a different moral to this story: in the space of 47 minutes you were able to conduct a reasonably thorough audit on the doas codebase. Wanna give that a shot for sudo now?
Does anyone actually end up paying the 47,500 a year for the drug or is this some sort of gimmick on the part of the drug company when they negotiate reimbursement rates with CMS or other payers?
Do you like smooth or blocky text?
I respect that podcasters are spending their time and effort putting together a program which I enjoy. The price I pay for that is listening to them talk about some product I don't give a shit about for a few seconds until I can hit the skip button. To me, there is a clear cut deal with no deceit.

Do you feel people should volunteer their time gratis to entertain you?

What Hacker News does with adverts slipped into the newsfeed is essentially the same as what podcasters do.
This advice applies IMHO.
https://www.cybertec-postgresql.com/en/postgres-scaling-advi...

"So, you’re building the next unicorn startup and are thinking feverishly about a future-proof PostgreSQL architecture to house your bytes? My advice here, having seen dozens of hopelessly over-engineered / oversized solutions as a database consultant over the last 5 years, is short and blunt: Don’t overthink, and keep it simple on the database side! Instead of getting fancy with the database, focus on your application. Turn your microscope to the database only when the need actually arises, m’kay! When that day comes, first of all, try all the common vertical scale-up approaches and tricks. Try to avoid using derivative Postgres products, or employing distributed approaches, or home-brewed sharding at all costs – until you have, say, less than 1 year of breathing room available."
What I really want is a way to define a graph of tasks and dependencies, and then execute it across n workers.

Something like

parq add --task-name wget1 wget http://example.com/foo.json
parq add --task-name wget2 wget http://example.com/bar.json
parq add --dependencies wget1,wget2 jq -s '.[0] * .[1]' foo.json bar.json
parq run -n 2 # executes wget1 and wget2 in parallel using two workers, then merges them with jq
How is it in practice different to something like:

cmd && cmd2 &

edit: From reading other comments I guess the difference is not mainly that it keeps running if the shell dies but that it allows you to easily append new stuff to the end of the queue
This is very much science - see https://slatestarcodex.com/2017/06/28/why-are-transgender-pe...
A balance-of-power strategy's effectiveness is not limited to foreign populations.
They don't tell you about it. That's the whole point ...?
That's acatually good to know. As I mentioned in another comment, faffing around with charging network accounts is one of the more minor issues that puts me off an electric car at the moment.

(We don't have off-street parking, that's our major blocker at the moment, and that our car is only a few years old).
> The $100/user/month model

It's not a high number of accounts before you can have a person dedicated 50% of the time to just running a local gitlab setup with any options you want. Including infra costs + on-demand CI/CD.
Even worse is that (here in Canada at least) we have infrastructure surveyed, its GPS coords recorded, then manually entered into CAD (or similar) drawings using a lot of guess work. Things like metal detectors are used to more or less guess that a detected object is in fact a gas line or something, GPS location is recorded, then someone plays connect the dots in CAD. It's unreal. So many opportunities to introduce error, and the initial locating of the underground object could easily be incorrect.

I know newer infrastructure is more diligently recorded, but there is a TON of old crap in the ground ready to be ripped up.
KotlinJS for React
That’d be far beyond absolute zero temp of −273.15° so must be a typo.
Poker is a lot like starting companies but I don't like the metaphor you use at all. The similarity is very simple. Both are extreme variance games. When you play a high variance game and lose, it's difficult to tell if you played poorly or got unlucky. Playing perfectly (GTO) in poker requires that sometimes you get stacked. Most people have trouble with this concept. The idea that they can do everything right and still not get a great outcome is scary.

Another valuable concept in poker is stack size. In poker, you should never play a hand in a game where you don't feel comfortable losing your entire stack. Similarly for running a company, you should try to make many small bets (or experiments) when the outcome is high variance. You shouldn't risk your company with every decision. Learning how to take lots of little risks well can even out the variance without ever putting you at significant risk.

There's a lot to take away from poker when starting a company. I don't think your article covered the important bits.
> installing mass surveillance

It didn't have to be installed, it was already, although in a pre-Snowden era, governments doing Internet surveillance was the conspiracy theory. My speculation is that more international traffic got routed through the existing surveillance infrastructure, causing a bottleneck that slowly got better.
"issues that, in 2021, effectively only C and C++ have"

"I'm not sure I can think of any other languages with «pointer arithmetic». Almost nobody else is using NULL-terminated strings. And so on and so on."

The thing is, at least a while ago, these were features that got C and C++ chosen for, precisely because they enable someone to go do things quick and dirty (mostly for "quick", with "dirty" only as an assumed consequence, but I've also seen both C and C++ for "dirty" alone plenty of times). We had safer languages (the one named after lovely Mrs. Lovelace, for instance), yet those options simply could not persuade the people that like it raw. Now we clearly have a stronger techno-political pressure lobbying for wearing straighter jackets, so at least it's interesting to watch.
No, this won't defeat CSRF attacks.

All this does is create a separate cache for each site, so that they can't infer that a user has already been to another site. It makes no changes to POST/PUT/PATCH requests to an endpoint. They will still be going there.
Not sarcastic. SUID root binaries are a prime target for hackers, and even I've used them to gain local privilege escalation in the past. For example authors of VEGA5000 payment terminal made pppd used for GPRS internet connection have a suid root permissions, and pppd can be used to execute other programs just based on the command line arguments. So that was that.

sudo looks quite complicated, just by looking at what it has to parse and validate (sudoers file). I'd rather not have it on the server, and just use custom purpose made static built suid binaries for necessary minimal purposes of privilege granting.

It's not even installed by default on some popular Linux distros. Of course I realize that it's very ubiquitous, regardless of this. And it's probably fine to use on your workstation. But leaving it unattended on some server feels a bit dreadful.
I'd imagine this cost would generally be borne by insurers or a government health care body.
There is no such thing as GNU sudo.

The homepage for sudo is https://www.sudo.ws/

It is licensed under an ISC style license.
What makes you think the guy in the ad is a "suburban dad"?

These companies sell to police, private security companies, military, and yes civilians. That segment of the ad looks like its targeted to more of a private security/police application.
Hmm the year is wrong on the timestamps. Attention to detail is important in C programmers working on security critical software...
One approach for solving that can be (but might not work always) to add new features only to more expensive packages. Of course the lower tier users won't be happy with that either, but if there are notable new features they can make an argument.
How do you define front running?
A total eclipse is perfectly safe to view with the naked eye. You just have to be carful you don't start too early or end too late...

Many references, but e.g., https://eclipse2017.nasa.gov/safety "Looking directly at the sun is unsafe except during the brief total phase of a solar eclipse (“totality”)..."
You would be wrong.

>One of those details Steve’s initial opinion on third-party apps for the iPhone. In the beginning, Steve was opposed to third-party apps, and wanted developers to create web apps that could be used through the device’s mobile Safari web browser. According to Apple board member, Art Levinson, “Jobs at first quashed the discussion” of allowing apps on the company’s debut smartphone.

https://www.cultofmac.com/125180/steve-jobs-was-originally-d...
Isn't light pollution due to bouncing off the atmosphere's content?

Ipso facto, no atmo => no light pollution looking up a circled lens?
Novel Camera-Based System for Automated Landing of Drone on a Fixed Spot
>Why does facebook do this rather than let third party advertisers advertise?

I think that's exactly what FB is doing, to be honest. They are simply letting third party advertisers advertise.

Historically, dem president in power has always been an indicator of increased spending on guns (because hardcore gun people become afraid that the dems will make guns more difficult to purchase, so they stock up). And increase in gun sales means increased budget (including ad budget) for gun-related businesses. Higher ad budget for gun-related businesses means more ads for gun-related businesses popping up on everyone's feed, as they keep outbidding other ads.

Combine that with the fact that a lot more people in your social network graph became more interested in guns for various reasons over the past year (protests on both sides, covid, dem president, etc.), and you have just massively increased the probability of seeing an ad for a gun-related business.
I first read it as "house blinds", then I saw it was "horse blinds" (aka horse blinders). lol
I think it's now enabled by default with Fenix. Actually, I think it was enabled by default in the older one too?
Going skydiving, with a class, with a parachute, with a backup, is still dangerous.

Climbing a mountain with good equipment and a buddy is still dangerous.

Being "properly prepared" is only relevant inside a context. You can't look at just preparation when deciding if something is too dangerous. The actual risk numbers are the important thing here.

If I'm driving 100 miles, and I do something sloppy that doubles my risk of dying in a car crash, the actual danger I face is less than the danger of skydiving just once with perfect prep. If it's also a special occasion where I'm going to get a huge amount of enjoyment out of it... the risk seems okay.

Even if we're focused just on car safety, we should be far more upset when someone buys a car without top-tier safety ratings than about some one-off trip like this.

Being able to point at some specific danger, like a battery on the floor, is just bikeshedding. What matters is the risk per day/month/year, and most of that risk is invisible.
Hacker – A Computational Model of Skill Acquisition (1973) [pdf]
> In both cases, each company's non-sharded databases were FAR more operationally problematic than the sharded ones. The sharded database tiers behave in common ways with relatively uniform workloads, and the non-sharded databases were each special snowflakes using different obscure features of the database.

That's because sharded tables restrict what features you can use (e.g., no JOINs). If you constrained the features on the non-sharded databases, you'd achieve the same net result.

Sharding _necessarily_ only solves one problem: queries operate against only a subset of data. While what you're saying is true (sharding avoids certain problems) it also restricts your ability to perform other operations (more complicated queries or reports are ~impossible). It is not without its tradeoffs.
Even if we run the same math with 7 out of 10 bugs being memory safety related, and assuming that Rust prevents all of them, those same example programs end up with 30 bugs in Rust and 10 bugs in C.

There's another argument I could make, too. Look at the bug tracker for the program you want to rewrite in Rust, examining the historical bugs. You'll find that there are often hundreds or thousands of mistakes that they made and already fixed in the original codebase. If you're rewriting it from scratch, can you be sure you won't make just as many? A stable, maintained codebase with a low throughput of changes tends to have fewer bugs over time, as the lack of churn avoids introducing new bugs and the application of time susses out all of the existing bugs. Rewriting the whole thing from scratch has a very high rate of churn, introducing a whole new slew of bugs on its own.

Now, a small codebase, focused on delivering its key value-adds without distractions, kept stable and at a low-churn rate over a long period of time: no matter what language you use, this is the best recipe for reliability and security.
Not sure of these are being automatically generated by a script or someone is manually editing and uploading them

On the one hand the video title patterns seem to not be formated consistency. But then all the thumbnails seem like a script is fetching images off Google and stretching them to 16:9 aspect ratio

In any case, nice find.
Enjoyable, beautiful animations. Keep making these!
As 'tzs points out, corporate employee PACs were not unlawful before CU, which, at any rate, had little to do with employee PACs.

There were any number of ways you could have learned this, but one obvious way would be to compare the date of the CU decision with the date of the creation of Google NetPAC.
But yes for any instructor who has a PhD?
If it still got software updates to Safari, then maybe. But also, browsing the web on my iPad Air gen 1 is pretty painful.
There was a $500 installation fee.
Important Security Update
> dead for lack of interest by the sole maintainer in reviewing and merging patches

I think you mean "lack of action" rather than "lack of interest."

It's easy to be enthusiastic about developers doing lots of work for you (usually for free) and to cast them as "uninterested" if they don't comply quickly (or at all) with your requests.

I suspect many maintainers are "interested" in reviewing and merging patches but are simply unable to perform large amounts of work without pay, due to time and financial constraints.
You mention two things.

1. Missing out on getting rich. Well, more money is nice, but focusing on chasing money can make you miss life. Don't do that.

2. Missing out on the discussion. You fix that by asking questions. At first, they may be dumb questions. But if you don't know something but wish you did, don't just sit there. It's easier to learn than it ever has been.
Isn't that a tacit argument against stay-at-home orders?
I’m not going to read your comment since you’re clearly being facetious.
Mars’ moons are more like asteroids though
For what it's worth, PAM is also not invited to my parties, for all of the same reasons as sudo was shown the door. And what people want PAM for is mostly solved with SSH certificates.

>writing separate tools would be the equal (or more!) lines of code and an equal amount of bugs in total

In total, yes, but crucially, not all on your system at the same time.
You can bet your last dollar that if the "right" RedHat or Debian developer rewrote sudo with feature parity, it would be adopted by all major distros in a couple of months. It's the sort of thing nobody really cares about except OpenBSD (which wrote their own).

The problem is feature parity. Most rewrites cannot guarantee that off-the-bat, so they end up struggling to persuade people to switch - why break stuff that works just fine and lose features, in the name of some engineering purity?
Container settings sync, and have done so for a while.

https://support.mozilla.org/en-US/kb/containers#w_what-you-c.... (item #7)
It didn't sound reasonable when JavaScript was introduced, and it didn't sound reasonable with WASM, yet here we are.
Single persons often have superhuman standards. It is easy to see that most of the best works in math or art were produced by an individual.

Code review can work, but often it doesn't. There are countless examples of projects with "strict" review requirements that have similar issues (whereas qmail only had one).

Writing tests is the important thing, it keeps you honest.
You reminded me of the Phillips toothbrush with AI. Marketing like this makes the term AI worthless.
TIL that Aramid fibers are not just something made up in bideo games. (: Thanks for sharing that.
The fact that you think you can use RDF without implementing ANY format, makes it obvious you don't get it at all.


Specifications are nice and cozy until you hit the harsh reality of implementing them.

"RDF iS oNlY tHe abStrACt GrApH StrUCtuRe", please, spare me the marketing bullsh*.
Nifty device, and great write-up. Seems like it might be simpler with an ESP32 though, since it does have an RTC.
I saw a funny facebook group that convinced me that people whose children's lives were ruined by vaccines are dumb. And not just dumb but very dumb. Because if it's SCIENCE you have to believe it. Never mind the countless examples where the science is political and motivated by money.
I think this can be useful to run with git hooks. It can branch off builds etc at commit. For quick and dirty continuous integration.
It makes sense. When the sky is clear I don't need to worry about rain. When it's cloudy I do. Only 1 is a danger therefore people prepare.
Blinders! Thank you!
> How does one programmatically detect a flamewar? :)

An NLP/Machine learning model would be a great way! Probably also taking in other features as input such as the number of comments per second, and how deeply nested those comments are.

Let's build one!
Algebraic topology is an amazing part of mathematics. (If you like pictures, you might enjoy Topology Illustrated by Saveliev.)
This study is flawed for a few reasons that I'd mentioned to the author when it was first published, but they ignored my comments.

The main problem is that they confuse DOMInteractive for Time To Interactive. The two events are very different. DOMInteractive is a legacy event that refers to the time when JavaScript can safely interact with the DOM. This really has nothing (or very little) to do with user experience.

Time to Interactive, on the other hand, is the time when a user can expect the page to respond quickly to interactions (clicks, scrolls, keypresses), ie, these user interactions should have no user perceivable latency. This is not a metric that has a corresponding browser event. It requires a bunch of post-processing based on various events. The researchers have made no attempt to calculate TTI.

Source: I've been working in this area of research for 15 years.
Very interesting. HE's BGP tool sees it https://bgp.he.net/AS42861

edit: so does https://www.peeringdb.com/net/2258
This seems on the money: https://news.ycombinator.com/item?id=25913516
IKEA to start selling spare parts for products
People at HN proclaiming all FAANG companies are equally bad, here’s another feather to the hat. All of them are bad but if u remove the problems at those companies, their core business model can still survive except Facebook. It’s business, at its heart is creating polarization and alternative realities.