skysight-inc/HackerNews huggingface dataset:
I think you must be talking about HIPPA compliance, not SOX?

Anyhow, I think the right to privacy is also not absolute. If I'm in public and someone takes a photo, I can't stop that. I also can't force people not to look at me when I'm out in public, or stop them from saying they saw me on the street. Their rights to go about their business in public and their right to free speech are not trumped by my right to privacy.

Medical privacy is different, of course, but that's just another example of my point. In narrow circumstances, certain people (e.g., doctors, hospital staff) can be punished for violating your privacy about certain topics. But there are plenty of exceptions to that. The first hit on my search for "HIPPA exceptions" lists at least 10 reasonable exceptions, including public health and law enforcement: https://www.healthcarecompliancepros.com/blog/exceptions-to-...

In case it isn't clear, I think this is a fine example of balancing societal trade-offs.
The connector requires a small amount of downward force to slot the nvme device. Without a screw, the device can easily pop out of the slot.
I've tried to read The Checklist Manifesto twice now, and I couldn't because I'm too squeamish.
Quite bonkers, and news to me. This must have been one of the more grandiose campaigns of the Victorians.
It being their official sites gives those value / legitimacy and makes them even more okay to not kick them off. Kind of like there should be hardly anything the US president can do to get kicked off twitter.
Many Islamic (not just Arab. Also Persian and others) scholars were on the right track about identifying evolution, and far from the evolution denying general populace today.

See the short "history" section in this article: https://en.m.wikipedia.org/wiki/Islamic_views_on_evolution
That is because everyone else is working on 6G!
One big difference between the airlines and the automotive industry (or doctors) is that with airlines a crash doesn't just kill the paying passengers. It also usually kills the pilots and other crew.

This sets a floor on airline safety--it has to be safe enough that the airlines can readily find pilots. Some passengers, especially those who rarely travel, might accept more risk for a better price but I suspect that pilots, who might be making hundreds of flights a year, would not be so willing.
Only 2FA Paypal Option Available: SMS
I've spent more than 3 hours on the phone with PayPal support. They disconnected my bank account but won't tell me why. The only option they will give me - and they're emphatic about it - is that they can only re-authorize me by SMS. Literally _zero_ other options (computer says no). I don't have a cell phone that can receive an SMS, but that's beside the point. Am I crazy in thinking this is crazy? Is SMS not proven insecure several times over? Anyone else had a similar experience?
No, you don't. Look at the successive increments: they get tinier and tinier over time, exactly like one would expect from an increasingly professionalized global sport drawing from a talent pool of hundreds of millions of people. The only gaps or changes in the record which are remotely comparable to how much Calment exceeded and continues to exceed other oldest-people date back to the 1800s. Her record is in the completely wrong place.
I was told of Algebra coming from Al-Jabr meaning "number games". I was surprised I didn't see this mentioned in the article, until I found the book mentioned in Al-Khwarizmi's biography [1]. The book's title is "Hisab al-jabr w'al-muqabala" but no translation is given and Google's translation "Al Jaber account and interview" is not helpful. Can anyone confirm or deny the explanation I was given?

[1] http://www-history.mcs.st-andrews.ac.uk/Mathematicians/Al-Kh...
There is basic infrastructure for SF Mesh in place (200+ miles of municipal owned fiber + wireless nodes throughout the city). In fact I have one at my house pointed to a local public heath clinic (there are a number of non-profits and others who get free municipal mesh internet). There is def strong interest for this in SF - we held a community event and had over hundred people show up.
Not downcase, modern. I.e case-preserving and case-sensitive. E.g. to be able to define native ffi calls into CamelCase functions. Downcasing is destroying information, Modern is keeping the original symbol names
We use ELK for logging and Prometheus/Alertmanager/Grafana for monitoring/alerting/dashboards.
Arabic and Hebrew are both Semitic languages. Elohim is the Hebrew word for "gods", the plural form of el, "god", as seen most commonly today in Hebrew names like Michael, Samuel, Raphael, Emmanuel, Elijah, Eliezer, etc. etc. etc.

Allah is just the Arabic cognate, plus the definiteness marker. So yes, anyone speaking Arabic will use that word to refer to any god, and anyone speaking Arabic in the past would have used that word to refer to any god. Similarly, a German today wouldn't hesitate to apply the word "Gott" ("god") to Thor, because Thor is a god. Whether the hypothetical German is Christian isn't really relevant, and neither is the fact that the Christian god is nameless, being usually referred to by a title such as "God", "Lord", "Father", etc.
what security issues were prevented by libav's wholesale removal of working code? why did libav implement new ffmpeg features in gratuitously incompatible ways? why did libav print the hilariously defamatory "FFMPEG IS DEPRECATED" message?
I would invoke the "skin in the game" metaphor. Listen to customers who have a vested interest, for their own reasons (brand building, networking, the "expert" part) as well as for optimizing some part of their professional workflow, making your service a catalyst of their moneymaking abilities (the benefitter part). The hacker part to me is mostly a consequence of frustration or necessity, and that is different for every industry.

If a publicly outspoken professional uses your software, engage them. That has been very helpful for our company every single time. It resulted in great publicity, brand building and in almost all cases meaningful insight into the what and why of their actual business problems.
>over 35,000 active nodes and about 63,000 km of wireless links (as of July 2018)

That's impressive.
What's the population of supercentenarians in Sardinia who are under 64 years old?
Hmm. That link seems to use a paper for its source, titled "Technical review and evaluation of the economics of water desalination: Current and future challenges for better water supply sustainability".

I tracked down a copy of that paper. It opens with:

"The cost of desalinated seawater has fallen below US$0.50/m3 for a large scale seawater reverse osmosis plant at a specific location and conditions while in other locations the cost is 50% higher (US$1.00/m3) for a similar facility. In addition to capital and operating costs, other parameters such as local incentives or subsidies may also contribute to the large difference in desalted water cost between regions and facilities. Plant suppliers and consultants have their own cost calculation methodologies, but they are confidential and provide water costs with different accuracies. The few existing costing methodologies and software packages such as WTCost© and DEEP provide an estimated cost with different accuracies and their applications are limited to specific conditions. Most of the available cost estimation tools are of
the black box type, which provide few details concerning the parameters and methodologies applied for local conditions."

I read through the rest of it. To the extent that it offers cost comparisons of some large scale SWRO projects, they seem to be self-reported and come from projects in Saudi Arabia, Israel, Oman, and Australia. This leads me to a couple of concerns WRT the construction and operating costs of SWRO projects:

(a) that a comprehensive, independent, apples-to-apples accounting of the costs of these projects has not yet been done;

(b) that some of the long-term costs are being externalized, especially the expected impacts on local ecological systems that become the necessary dumping grounds for the wastewater;

(c) that the costs to date are severely location-specific, and do not address for instance trying to transport seawater a mile uphill as needed in many of the areas expected to or currently experiencing severe freshwater instability.

Clearly SWRO is a viable option in specific areas that have nearby access to a suitable water source, good power infrastructure (or solar availability), a lack of freshwater availability, and an appropriate wastewater treatment strategy (or, more likely -- and sadly -- loose regulations that obviate the need to address this).

But calls for SWRO as a worldwide, one-size-fits-all, cheap solution are misguided and misinformed, IMO. Mostly I worry that "just build desal" will frustrate efforts for conservation and improving existing infrastructure, especially in places where desal isn't a viable option anyway.
It does apply. Someone has to be the oldest. Someone has to be the oldest-person who has the largest gap. Regardless of how old that is, or how large the gap is, there will be at least one.
Being the person that helps and supports people can bring people closer, but only so close. I find when I want to socialize with people, I hide that side of me, unless necessary (it comes out all too often), so that there is an opportunity to get closer than just helping people with their problems. Being overly empathetic makes it hard to gain close friends.

Empathy is often misunderstood. It's seen as feeling the emotions of others. That's not wrong, but it doesn't hit the heart of the matter. Empathy is being able to model other people. It's knowing what others know, figuring out how and why they think they way that they do. It's a powerful ability. Without it being a great leader is impossible. It's necessary to be both kind yet encouraging improvement at the same time to manage and help people.

Beware of hubris syndrome. It takes empathy to grow, aid others, and become a leader, but paradoxically when one gains power their mind starts to optimize out ones empathy reducing it over time. What once got you into power stops becoming necessary. By understanding this and how it works, one can keep themselves from falling into that pattern. The world thanks you: https://www.strategy-business.com/article/How-Leaders-and-Th...
https://news.ycombinator.com/item?id=20629651
>I'm finding that the rewards in mental health are more than sufficient to justify the astronomical opportunity cost.

The opportunity cost is that obiefernandez is not working to earn money? Or not studying to improve their income? Earning money to be able to spend it later on things like overseas travel.

Reminiscent of Heinrich Böll's parable of the fisherman: https://www.becomingminimalist.com/recognizing-happiness/ (this version doesn't presume the fisherman is Mexican - is the original story in German?).
RPL is one of the more interesting later developments from HP's calculator group. After the HP41C series, they realized that continue the development they wanted to do, they needed a higher level programming environment. To that point, my understanding was that it was all essentially machine/assembler level code written for their (fully custom) CPU architecture.

Their response to this was RPL, which borrowed rather heavily from both FORTH and Lisp. In keeping with their RPN user model and the light memory footprint of FORTH, RPL used a threaded execution model composed of a hierarchy of function (procedure?) object definitions. As with FORTH, these could be either defined in machine code or defined in terms of other RPL words. From Lisp, RPL borrowed the notion of tagged data objects and first class function objects. A user program written in RPL was composed of one or more function objects bound to variables. Keeping with FORTH, user program objects were in many ways peers of the objects built into the system ROM. Same format, execution, etc.

If you look at the documentation around these calculators, you'll see references to both "System RPL" and "User RPL". The real difference here is that when HP defined the words that were built into the calculator ROMs, only a fraction were given names within the ROM. These were the words that HP vetted for customer user and deemed safe (by ensuring they all checked types, etc.) "System RPL" words didn't necessarily have the same type checking and couldn't be used without risk of corrupting memory etc. Of course, they were also faster and had some additional capabilities if used with care. These are how HP built the ROMs internally, and with HP's help, the internet community developed tools for non-HP folks to write so called "System RPL" and even machine code level software.

If you came at one of these RPL calculators from the perspective of one of the earlier traditional RPN calculators, this could all be unsettling. There were a number of various changes to the UI, starting with the fact that the stack was no longer bound at four levels. It's a definite change in perspective.

From the perspective of a new user, the calculators had a great deal of internal consistency to their software model that could make them a lot of fun to use. It was in many ways 'turtles all the way down', which meant that even if you never used the system functions, you still could pretty easily write hook functions for the the REPL, custom menus and key bindings, and all with what would in these days be described as first class functions bound to event handlers. (On a 4-bit custom CPU that would run for weeks on three AAA batteries.)

One final aspect I'll leave you with is that, while the flagship calculators were almost all still RPN, HP also used this platform internally for a number of other non-RPL models. Some of the business calculators, the HP38, etc. all used this software, even though they did not necessarily expose a stack through their UI.
The central issue, is that fossil fuels are a commodity, and solar and wind are technologies. Both, of course, have physical components (coal, sand, metal, etc.), and both involve technological progress (fracking is a particularly important example), but the long-term trend of commodities is, at best, up and down and up and down, whereas the long-term trend of technologies is down.

This means that, because both solar and wind electricity have prices that decline at an exponential rate (different from Moore's Law in the %/year, but not in their shape), the fact that they are competitive now, means that they will be far, far cheaper in the future. No matter how much of a head start you give a linear process over an exponential one, eventually the exponential one wins. Commodity prices are worse than linear; they are more similar to sinusoidal.

The real issue now, which is not widely discussed, is how to prepare the world for a time, within a decade, when every fossil-fuel dependent economy goes the way of Venezuela. I don't think we are remotely ready to handle the fallout from that.
The car insurance industry is by no means the most useful comparison, but it does make some provisions that resolve a number of these issues. By that I mean with car insurance, a reasonable deductible and the knowledge that submitting an insurance claim will likely result in higher premiums, tends to keep people from over-reacting to small things. Most car insurance companies also offer a variation of the "preventive" care at reduced, or even no cost, such as with window rock chips - its far less expensive to fix those rather than replace the entire window.

I'm not suggesting copying the car insurance model over to health insurance, but I think there are some worthwhile areas to explore, as I don't see the current health insurance system being sustainable much longer.
Architecture decision records (ADR) are an excellent way to show managers that work is proceeding, and that research is necessary, structured, timeboxed, and transparent.

https://github.com/joelparkerhenderson/architecture_decision...
FWIW you definitely come off as though you have "a bone in this fight" while the parent does not.
I think you're stuck with the oddball aspect ratio. Part of the CMOS readout process is done an entire line at a time, and there just isn't a way to increase the speed this much without dropping most of the lines. Actual high-speed cameras have similar limitations at the higher speeds.
To me, Flatt's proposal for Racket2 smells more like adding tools to better facilitate infix languages than depricating S-expressions. Given Racket's pedagogical mission, it looks more like a move toward migrating the HtDP series of languages (Beginning Student, Intermediate Student, Intermediate Student with Lambda, and Advanced Student) to infix syntax than anything else. Not really the end of the world or a big change to the larger Racket community. Just another extension of an ecosystem that remains s-expression based despite Algol and Datalog shipping in the box. It's hard to see Flatt's work porting Racket to Chez Scheme as a prelude to abandoning Scheme as the basis for the Racket ecosystem.

On the other hand, the reality is that Racket's syntax makes for an uphill fight when it comes to adopting the HtDP curriculum. Anyway #lang racket syntax is just sugar on the more important concepts in the HtDP methodology. The HtDP engineering principles are matter much more than which language is used at the top level.
>The US has toppled brutal dictators like Saddam Hussein and kept the global peace

Those two statements directly conflict: Saddam kept things under control a lot better than the violent mess that exists in Iraq now.
I tend to agree that health insurance isn't really insurance - it's more like a costly, inefficient payment intermediary that collects money from the young and/or healthy to pay for care for the old and/or sick.

Which seems like an OK idea in principle, but it isn't working very well for patients.
Persian false invitations and promising future services to (mostly) strangers
You probably should be checking in the console network tab to make sure you are getting the correct HTTP status code (301 vs 302).
You mean on a trackpad?
Great article except for this prediction, Which fails to grasp the continuous exponential momentum of solar price decay:

all-in cost of solar power has dropped 85% since 2010, and BloombergNEF forecasts an additional 63% drop through 2050.
A skunk can't smell its own stink. Are you sure you didn't smell?
>it works better if you substitute 'arabic nations' with 'dictatorships'.

You are correct this applies to dictatorships in general, and in fact the article mentions the similarities to the Soviet military.

But then you have to ask why the Arab nations are almost all dictatorships, and that brings you back to culture, at least considerably.
Although not Ericsson, Bofors had developed some bad habits to help sales.

https://en.wikipedia.org/wiki/Bofors#Bofors_gun_scandal
The problem I've run into (YMMV) with C++ is that a lot of documentation/information is outdated (dangerously so).

C++ isn't a single language, it is three major revisions (98, 11, and 17) of a similar-ish language. If someone used C++ continuously throughout its evolution this is a non-problem. Because they were able to slowly adapt their knowledge, while still having the ability to mix and contextualize.

For new people entering the language "just use C++17" is largely a fiction. Because the first time you look at stackoverflow, a tutorial, or GitHub code all bets are off. And a lot of developers end up in interop hell because they're trying to get to C++98/11 structures to work with C++17 ideas.

I don't actually agree that C#/Java gives an advantage to C++17. In fact I think the reverse. The syntax is similar, but syntax is relatively minor in the grand scheme. Rust, once you get past syntax, is much more similar to high level language because you aren't wandering through the memory management minefield.

Just my 2c.

PS - I don't "hate" C++. But you cannot just jump straight to C++17 while pretending C++ 98/11 don't exist. You have to learn all three, and then learn not to use the first two, otherwise you wouldn't understand most of the information available to you (and most libraries you're interopping with are writing in a dialect you don't understand). Learning C++ for real is a huge under-taking.
> However, I was under the impression that "5g" doesn't actually mean anything. As in there is no technical definition or standard that Huawei could be ahead of. Are we just talking about general mobile technologies or have things changed wrt 5G?

I believe most people mean 5G NR (https://en.m.wikipedia.org/wiki/5G_NR) when they talk about 5G, the same way 4G usually means LTE.
Military first is the rule. I wonder if they managed to get the stolen money, meaning cash it out. They might have stolen $2B but that money or coins might still be off limits to NK.
Yes, as the more time invested into research, the less time and the greater accuracy of planning. But like all multivariable situations, a balance is needed. With that planning feeds back into research in that you may hit a cut-off point, that don't mean research stops, it just changes the focus and future research will come into version 2.... As is with software, you hit a time in which you would love to add this and that and tweak this and that, but those end up being patched or version 2.... later on. Like everything, it is a fine balance, no cookie cutter template or formula as every situation is different. But they have comparable factors that you only learn over time and then in niche area's. You also learn to get those balances better and with that, plan ahead more.

But do put a price on your passion, more so if you plan to combine that with work. As the later can kill the former just as much as the other way around, get that balance right in a way that works for you.
Any reasonable HIDS/HWIDS, beyond physical PCB auditing, x-ray verification and supply-chain chain-of-custody documentation,
needs to include continuous monitoring firmware using end-to-end public key-verifiable signatures.

Also, open-source hardware, including the firmware, would alleviate some of the downsides of closed blobs.
RescueTime is a similar thing, but it tries to autoclassify.
Nice! Though it'd be good if they swapped the scenario where they hide the protocol to be `https` and make `http` the one that sticks out awkwardly.
Solo SaaS app dev here. I found Sentry[1] to be the most valuable tool for monitoring what's going on inside my (Django/React) app. Sentry catches every exception/error in front- and backend, then collects and aggregates them, so I get a single ticket/notification for every type of issue, instead of thousands of those for every instance of the same problem.

For me, that's much simpler than trying to log each error and analyze the log later on. I still create application logs, but only read them if I need more information about a problem logged by Sentry (most of the time I don't need that at all, because Sentry collects a lot of context already).

Another plus for Sentry is that it can be self-hosted, which makes GDPR compliance a little bit easier.

Besides that, I use Monitor Scout[2] for checking that my app is still up, and fail2ban[3] to get rid of script kiddies trying to brute-force passwords and stuff.

[1] https://sentry.io/
[2] https://www.monitorscout.com
[3] https://www.fail2ban.org/
I like upvotes of course, and flagging is fine. IMO downvotes tend to greatly increase the echo chamber effect and should either be removed or less weighted.

The least controversial comments usually bubble to the top, even when they're not the most informative or constructive, due to downvotes.

Controversial but otherwise fine comments should not be punished by downvotes if they don't violate site policy (flagging). IMO a site that promotes good discussion shouldn't allow users to tank comments they don't agree with
I'm not saying any of it is efficient, just not 'literally impossible'.
Sounds like they provide a search/aggregation service that many users find useful.