skysight-inc/HackerNews huggingface dataset:
> Also, it seems very strange to complain about companies collecting data that they're required to collect by law.

Thanks for clearly phrasing this, because I think this is exactly what I'm complaining about.

Audacity is, in fact, not required to collect anything by law, and for a very long time, it did not. It's a piece of software that runs on your computer. It doesn't even require you to have a network connection. It doesn't require the developers to even know that you exist.

No law (in any slightly free country, at least) prevents the existence of software that doesn't phone home. WordStar wasn't illegal. Emacs and Python and ffmpeg aren't illegal.

It is true that once you start collecting data, legal requirements start to apply, and you need to comply with requests for that data. That's a really good reason not to collect it in the first place.

If all you have is a stack trace, and you have nothing personally identifying (including filenames), then the data you have is useless for any other purpose besides fixing the bug. You're protected from legal requests, you're protected from illegal requests, you're less of a target of hacks, and so forth.

Fedora's ABRT, for instance, goes out of its way to ensure that any crash data they collect is suitable to make public: https://abrt.readthedocs.io/en/latest/ureport.html#ureport That's a pretty good way of squaring this circle. If the data is okay to make public, then by definition it's not a problem if anyone (law enforcement or otherwise) wants to see it, and you don't have to rely on their good intentions.

Ubuntu disables Apport by default in release versions, according to the page you link: https://wiki.ubuntu.com/Apport#Why_is_apport_disabled_by_def...

KDE doesn't claim to collect information about crash dumps; it just collects statistics about how it's used.

It is, of course, harder to debug things from just a list of symbols. And as you say, it's not feasible to teach everyone how to use gdb. So there's a tradeoff. You acknowledge that the software isn't going to be as good as possible in terms of bug-free-ness (or you find other ways to address that problem, like fuzzing or static analysis), but in exchange, you make the software better in terms of how it treats the user's privacy.
By making ourselves smarter and preaching science everywhere we are.
The argument is bollocks and I would like to see better from a technical evangelist organisation: "We want fibre" so we'll insist on 100Mb/100Mb symmetric throughput as a design requirement. That's the tail wagging the dog.

Start with your requirements and then pontificate, eg "I want this":

* Nominal download speed with no latency guarantees at up to 100Mbs-1
* Sustainable throughput for three concurrent 4HD streams
* Latency suitable for speech without lag
* 1500 byte frame transfer without me having to worry about MTU issues

The second requirement is basically three lots of 25Mbs-1 with a reasonable ACK response time. I picked three: Parents and kids doing their own thing as two groups plus another one.

The third requirement is a bit tricky but generally doable. If you do VoIP then >30ms latency is the start of the point where people need to manage their comms. Humans are actually really good at dealing with crap latency, provided the quality is good. I would suggest that say 10ms to your ISP PoP is a good start for latency.

The EFF article waffles on at length. It is both crap technical and stolidly political in nature. I think it fails on all levels but I still applaud the basic premise: We all need reasonably decent, low latency connectivity.

Oh, soz, I'm a Brit, but my last point still stands 8)
The signed shim itself is orders of magnitude larger than 512 bytes, not to mention the firmware that starts shim.

I don't think the Bootstrappable Builds folks are interested in touching proprietary software/firmware, so it is likely they would not be using UEFI or similar.
Besides providing a standard set of behaviors so people don’t accidentally mishandle idempotency in their hand-rolled attempt, it also allows networking frameworks to build in support for this in a generic fashion (if there’s any particular behavior they want to do around idempotency). This isn’t for browsers doing browser things, it’s for API clients calling APIs.
> why now, after 40 years

If this is a case of wear leading to total failure, isn't this like asking why we take the turkey out of the oven on Thanksgiving after 3 hours? Because that’s how long it takes.
The SF DA refuses to prosecute crimes. Police were still enforcing laws until they gave up.
We won't start doing 8K 3D video until its actually possible to do so.
What is the point of the initial test if you’re just going to delete it.
>I really don’t understand why switches are not proposed by the largest vendors.

Because paying customers don't understand or care about privacy.

Facebook is still a thing. Let that sink in.
More programmers really should have a look at what sort of assembly the compiler generates for their code. Compilers aren't magic, and seeing what sort of code it generates does give authors more insight into how concise their code truly is.
Also with magnetic influences, like thermo sensors in large transformators, breaks or motors.
Wikis and Teams training meetings. Wikis are sort of useful for simpler things and on-boarding (but I do prefer a script for installing the software). Training meetings are a must for anything beyond these.
Hey if you don't mind what are some examples of edge cases?
> Decent quality starts at several 10s of Mbps, and high quality 1080p is in the 200-400Mbps range.

That's so incorrect I don't even know where to begin.

I regularly record my own "talking head" in 1080p from OBS in h.264 at CRF 14 in "ultrafast", which is extreme crazy quality/space overkill (literally indistinguishable image from original, extremely low CPU usage), and that's an average of 34 Mbps.

I then immediately recompress the resulting enormous file to a still extremely high-quality CRF 21 in "veryslow" to be suitable for editing and subsequent recompression later, and that results in an average of 2.4 Mbps.

For comparison, high-quality 1080p h.264 movie and television releases on torrent sites are usually around 5 Mbps. The difference is that half my frame is a plain/stationary background while movies and TV have complex backgrounds, hence double the bitrate.

I have to ask -- where did you get the idea that "high quality 1080p is in the 200-400Mbps range"? That's off by two entire orders of magnitude. It's almost all the way to raw uncompressed 1080p, which is 1,500 Mbps.
> Is there any examples of open source projects that died because people were making too many ports?

Yes, Linux tracing.

I entered in 2014 when there were 14 different tracers, none of them finished (ie, does everything and works on all distros). It wasn't a lack of engineers -- there are plenty of smart engineers in tracing. But they were scattered among those 14 tracers. It was a mess, and no one could understand why Linux didn't have a mature tracing solution. (I think this also answers your question: Why cares if people make shitty ports?)

So I started thinking I could fix it by creating my own 15th tracer...Just kidding! What a terrible idea. Instead I joined one of those 14 existing tracers (a new one called BPF) and worked hard to get others on board, and do what we hadn't done well before -- collaborate!

Early on I wanted to do my own front-end, but Alexei convinced me to collaborate on bcc. I also wanted to do my own language, but got people to collaborate on the existing bpftrace instead.

The entire journey of BPF observability has been one of us choosing NOT to keep spinning up competing projects and instead to collaborate together on one. And that's how we succeeded in delivering a tracer that does everything on all distros.

I should add you might be missing a bit of context here too, and that's that tracing is maintenance heavy: You don't develop it once and then it works forever. It needs constant updates to match kernel changes etc.
I'll be signing.
I would say in Brisbane, Australia the average pay for a Mid level is a $110k AUD package, with seniors being $130k AUD up. Keep in mind Australian listed salaries are often BASE. On top of this you need to factor an additional 9.5% superannuation (A kind of mandatory retirement savings) that must be paid. Project labour charge out rates start at $150 AUD an hour for a junior. Seniors can cost over $300 an hour. We are a high labour cost market.

Firstly most companies don't roll their own software, a lot of stuff is done with off the shelf products, and maybe some outsourced customization (especially in the web space). Custom software is typically only developed if 1.) there is a pressing need and 2.) there is nothing that can already fit the bill and 3.) it will result in a large enough business benefit to cover the cost.

Now there are things SMBs that do create software do to get better efficiency. Firstly teams tend to be smaller, often with a push for everyone to be "Full Stack". Originally this was Backend + Frontend, but this is often including DevOps, QA and more. Teams will often require everyone to work in every skill area at least at a junior level. Secondly there is a push in a lot of organisations for more then 38 hours of work a week in anywhere that is billing out staff.
Finder doesn’t run as sudo though. TCC is layered on top of Unix file permissions. It prohibits access to files, it doesn’t open a hole through pre-existing protections.

Basically, it acts as a sandbox rule. Sandboxing your app doesn’t allow you access to new files, it just denies access as determined by the sandbox profile.
Unit tests are for TDD. They make it difficult to write untestable code. They rarely catch bugs, they are your spec.
The entire reason SF is having this problem is that the majority of the city believe shoplifting is fine based on their voting patterns the last few decades.

https://www.dailywire.com/news/cbs-anchor-muses-if-famed-wal...
QC is where I actually learned to program. I'd already done a lot of c and early c++ but the motivation of seeing my changes in the game world were a lot better than anything I could make in my own.
I suspect that datacenters do not implement PID not because nobody there is aware of control theory. I suspect they tried and decided against it.
> lost building plans

That's pretty wild. I thought city halls had copies of all building plans from when they were submitted for permit approval.
Anyone remember Napster? There were extremely obscure musical recordings that were instantly found on Napster that are impossible to find even today. It took a long time for anyone to rebuild that data to the level of usefulness that Napster had.

If Sci-Hub is forced to shut down due to legal pressure, technical problems, running out of money, or the founder losing interest, it would take a long time for anyone to duplicate Sci-Hub if they started from zero.

I think a good way to keep the cause alive is to backup or mirror the 85,483,811 papers hosted on Sci-Hub. That is, if she's willing to allow it (maybe it's already being done, but how widely?).

In the case of Sci-Hub, you'd need between 85 and 850 TB for each backup or mirror depending on whether the average paper size is 1 MB or 10 MB.
my previous company has an entire branch in Ukraine. Less need to comply with EU labor laws but equally talented professionals
Roy Mustang does it with way more style ;)
You seem to misunderstand app permissions. A sideloaded app doesn't magically avoid the permission system. If you can steal passwords by installing an app via sideload then there's a huge hole in the security of iOS. You seem hellbent on badmouthing sideloading but seem to have a poor understanding of sandboxes and app permissions. The security against what you mention is supposed to come from iOS - not app review teams.
Release notes:
https://github.com/neovim/neovim/commit/a5ac2f45ff84a688a094...
NNUE is much smaller than Leela's net, and has a much different architecture that's optimized more for CPU. Additionally, Leela uses Monte Carlo Tree Search and Stockfish uses Alpha/Beta pruning.
I've seen audio devices where it's the same socket and you choose in software whether it's an output or input.

I think it was realtek built-in on a hp SFF PC.
Point taken.

I think ultimately the problem of academia publication isn't the openness of access (which obviously is good if we can have), but the whole system as you mentioned.
Test the heck out of the external, documented contracts. Then the test suite helps you refactor: reshuffle the internals while maintaining the contracts.
FWIW, this site is not a corporate blog, but a community encouraging current and aspiring sysadmins to learn in public. The author is not an official spokesperson and is very new. Also, I should have caught this point before hitting publish, so it's my bad.

And if it's not obvious: Red Hat wrote enough of Kubernetes to know better than to base64 anything of value.
“Keep your friends close and your enemies closer”

~ The Art of War. Sun Tzu (5th century BCE)
> You seem to be under the impression that anyone here has an obligation to make sure that you're adequately convinced.

All I'm just asking for clear evidence to a claim, like someone asked me for evidence of a claim I made, I provided a source and evidence. Not hard, seems you and others have an issue with it.

> You clearly won't believe that most drug transactions are done in cash unless you see incontrovertible evidence. That's fine. But no-one cares, so I don't know why you expect demands for a source to be met.

Do you expect me or anyone else to believe a random person like you making a bold claim at first glance?

So unless you have a source to a bold claim, I can dismiss it.

> But in this case, it's such a well-known and obvious fact that there's no such benefit.

Then the refutation should be quick and easy right? Again, I see none so far.
I actually laughed out loud when I got to the part where each opcode was its own microservice, implemented in a dozen different languages. Well done.
Was in AEC in Florida for nearly twenty years. Started in a precast plant. During my MArch studied under one of the top forensic architects in Florida, Chuck Goldsmith, after grad school I worked as a Licensed Plans Examiner, got my Florida Architect License in 2007 - though it is currently inactive since I don’t practice there.

So yeah I do know someone with an informed opinion.

Concrete beams fail in tension. Likewise so do concrete moment connections where said beams join columns.

On the other hand columns fail by buckling when they become too slender…which is effectively what happens when a column loses steel and concrete due to corrosion and spalling.

From a personal standpoint I take the shit seriously because people might die if I get it wrong. I have been personally liable for buildings subject to salty conditions and dealt with the kind of people who would rather spend money on crown moldings than stainless steel structural components.

There is a lot of incentive to find rationales for saying the collapse is a one off.

The only unusual aspect is that it is the first. But Florida has buildings with similar issues down one side, up the other, and around the Big Bend all the way to Alabama.

I wasn’t surprised when I saw the building fell. I wasn’t surprised when I read that the first reports went back to the 1990’s. Wasn’t surprised to see the pictures from under the pool.

That’s what happens to concrete in salt air and how people ignore bad news about buildings falling apart.

The real price of fixing the problems with that building would have been comparable to building it new…hundreds of dollars per square foot not the few thousand per unit that the board was willing to spend.

No board is.
Yes. Perry, err... Perrier Air!
Prometheus, Titan god of fire, was sentenced by Zeus to eternal torture. An eagle ate his liver every day and it grew back overnight to be eaten again. The Modern Prometheus, Victor Frankenstein, didn't end well either, dying of the arctic cold while chasing his monster. I wish Ms Elbakyan, our Even More Modern Prometheus, a kinder fate. But clearly it's a high risk job.
So I think Google is definitely motivated to keep malware off of its app store. It’s bad for business. But we see the malicious apps from time to time anyway.

Likewise Apple is motivated to keep malware off the app store. Again it’s a bad reflection on Apple when they sneak through, but they do.

I just don’t see third parties being more motivated or having more resources than Apple or Google to police an app store. The malware is going to be worse on a third party app store, and they will quickly turn to dark patterns in order to maximize whatever they can squeeze out of the user.

I’m not opposed to opening up competition on app stores. Just don’t come back here to register your shock when the malware situation is kicked into overdrive.
And if you go to school in a Christian community, Christianity will be the unseen lens that underlies the curriculum. And so on with any other culture. It's not ideal, but it is what is.

CRT is a helpful lens, much like Marxism, Smith-style capitalism, and many other lenses. Like all of those, it has its limits. I want my kids to have as many lenses as possible, and to be able to use them critically.

I'll mention -- even elementary school kids have no problems understanding these lenses. I'd argue Smith, CRT, and Marx ought to be taught around 3rd-5th grade, not high school. My problem is CRT is being taught in kindergarten.
Like aircraft disasters, most civil/structural engineering disasters have more than one "cause". There is not always a satisfying answer or a single "smoking gun". A bunch of things usually have to go wrong at the same time for a building to collapse catastrophically. Building codes and engineering designs have a lot of assumptions built in, including an assumption that construction does not follow the drawings exactly. But other assumptions include lack of corrosion to a degree, regular maintenance, proper materials specifications, no subsequent modifications, a particular load pattern, etc.

Even then, most buildings are not really designed for much more than 60 or 70 years. Of course, most buildings are also supposed to be designed in such a way that even if it fails, it does not result in a cascading failure. The fact that this particular kind of disaster (apparently spontaneous collapse) is so rare is what makes it newsworthy.
People expecting some kind of judgement or cost to be levied on the city for its foolish ethics and reckless policies are forgetting that the quality of life issues are the cost. There is no further punishment needed. You want to pretend every homeless person is a victim worthy of massive subsidies and a blind eye by the police? Fine, you will have a city overrun with homeless and streets filled with feces.

Trying to predict how many people are willing to put up with these costs in order to build their ideal utopia is a risky enteprise. As Neitszche said, man can bear any how as long as he knows the why. The majority of SF voters are convinced that they are being moral by tolerating this behavior and so they are prepared to bear the burden of living with what they tolerate. In the big picture, this is nothing compared to the human costs of other utopian projects we've tried in the 20th century, so I don't think the voters of SF have reached anything close to peak disgust. Feces and an epidemic of drug overdoses is nothing compared to gulags, and even the ones who built the gulags were absolutely certain that they were doing the moral thing. Thus I am not predicting any change of heart by those who run the city. A few hundred overdose deaths and tens of thousands of property crimes are a small price to pay in order to feel that you are being compassionate.

What I do know is that many people who have different values are leaving the city in droves, trying to find places that are managed more wisely. Thus my prediction is that San Francisco will develop a poor reputation as a mismanaged city that is run by people who think disastrous policies should be continued as long as they are based on good intentions. I am not predicting that SF turns into a Detroit, or becomes a poor city. I am not predicting that most of the tech jobs will leave. My only prediction is that the city will become an object lesson for other cities to learn from.
The command line interface is designed for interoperability with chess GUIs according to an informal standard called UCI. UCI is sufficiently simple that you can talk to the engine manually if you really want to but it is much (much) easier to use a chess GUI. For example Tarrasch https://triplehappy.com (shameless plug for my chess GUI).
As a new grad down the border, you can make more than that.
Probably! If I had to offer a definitive opinion on the author's intention I would agree with this interpretation.

But physical space is inherently rivalrous, and a policy of "everyone runs a red light if they think they can get away with it" is going to have people being disastrously wrong sometimes.

I've actually ridden a scooter in places in SE Asia which basically work this way and it's... different. Less insane than it sounds, or looks like, but the rates of traffic fatality are objectively much higher.

This is why I thought it was interesting enough to comment upon.
Sorry, I mean a high school educated concrete pumper with 20 years experience will rote learn what the standards are. So the workers should see it's less than standard.

For something to be really off standard, it has to be complex or using illegal immigrant workers or something that is hard to see, like a bad concrete mix being brought in.

It also needs a reason. The cost benefit has to be more than risk. The builders won't risk a $xx million building by saving on re-bar. A contractor might, but they'd have to get away with it.
I just took another look at the article and it appears I misunderstood what it was saying. I thought it was saying automation of Finder granted access to other users' files. This is not the case. It was talking about accessing other users' files in the previous section, but in this one it's merely claiming that allowing automation of Finder means being able to read data owned by your user that would otherwise be blocked by TCC.

And honestly, that's not a surprise. "Granting an app the ability to automate the Finder means granting it the ability to access any data the Finder can access" seems fairly obvious.
I had the first gen Chromebook and the first thing I did with it was install Crouton and access Ubuntu.
Thanks :-] I was trying to figure out why stockfish debian package suggests xboard, but they don't work together. It is because stockfish suggests xboard and polyglot, but polyglot is required to use stockfish with xboard.
If unit tests are hindering your refactoring then you aren't writing SOLID code. The only time I find myself, e.g. splitting a class in two, and then having to deal with its shitty tests, are when I'm dealing with legacy classes that did five things at once. Oh, and their tests were just "did it crash?" tests, i.e. call a method but only check the happy path.

If you have reached the point where you feel tests hinder refactoring then you have two paths: a/ learn to write smaller, SOLID classes, or b/ meh unit tests are stoopid.
Rematch Alpha Zero. Have power consumption restraints. Go!
I wonder if wolfram is aware or interested in this project. He also has made progress in developing a computational understanding of the physical world.
No, because not every rule/law is a case of special pleading.

If you think it's not arbitrary then you are free to make that case, and then I or someone else will point out flaws like the special pleading that is already glaring. Peter Singer's work on speciesism is a good place to find out the obstacles you will have in constructing a non-fallacious, non-arbitrary argument.
But stool is gassing out too. Sometimes very noticably so...