skysight-inc/HackerNews huggingface dataset:
Abstract

Existing ethical discussion considers the differences in care for identified versus statistical lives. However, there has been little attention to the different degrees of care that are taken for different kinds of statistical lives. Here we argue that for a given number of statistical lives at stake, there will sometimes be different, and usually greater, care taken to protect predictable statistical lives, in which the number of lives that will be lost can be predicted fairly accurately, than for unpredictable statistical lives, where the lives are at stake because of a low-probability event, such that most likely no one will be affected by the decision but with low probability some lives will be at stake. One reason for this difference is the statistical challenge of estimating low probabilities, and in particular the tendency of common approaches to underestimate these probabilities. Another is the existence of rational incentives to treat unpredictable risks as if the probabilities were lower than they are. Some of these factors apply outside the pure economic context, to institutions, individuals, and governments. We argue that there is no ethical reason to treat unpredictable statistical lives differently from predictable statistical lives. Moreover, lives that are unpredictable from the perspective of an individual agent may become predictable when aggregated to the level of a societal decision. Underprotection of unpredictable statistical lives is a form of market failure that may need to be corrected by altering regulation, introducing compulsory liability insurance, or other social policies.
I wouldn't really call Zulip a counter-example. It wasn't aband^H^H^H^H^H released to the community, it was spun off as a separate company. They offer paid products, have employees, an office in San Francisco, etc.
If they have sufficient forewarning, they can steer the telescope out of the way somewhat.
I ran into that at a previous job. I'd need permission just to get a docker hub repo created or set up an S3 bucket. Too many layers of approvals. I came from a smaller company background where I had full authority to do anything I needed. I couldn't stand a lot of process and overhead, so I quit and went back to a smaller company.
In Punjabi (my mother language), its same as Spanish (not exact words).

Different words for brother's siblings & wife's siblings. Bhra. Bhen. Bhabhi. Saali.

Different words for elder than my dad uncle v/s younger than my dad (& their wives, so total 4 words). Chacha. Chachi. Taaya. Taayi.

Different word for my brother's kids v/s sister's kids (& gender, so total 4 words). Bhateeja. Bhateeji. Bhaanja. Bhaanji.

Different word for my father in law v/s his brother (& their wives, again set of 4 words). Sahura. Sass. Taaya. Taayi.

A set of 4 words for my father's parents v/s my mum's parents. Daada. Daadi. Naana. Naani.

Almost any of the above' friends (same social circle) gets the same word. So same word for my father's brother and brother's friend.

These all might share a but of pronunciation here and there; otherwise all of them are totally independent (one word), & not derived from each other (like something-in-law).
"her sobs in the night - every night, every night - the moment I feigned sleep"

Just a reminder that this is not a book 'glorifying sexual relationships'. This is not a book about a seductress. This is not a book that plays with ideas of consent.

Nabakov is playing a game with the reader, trying to trick the reader into believing that there is any truth in Humbert's narrative. I suppose it shouldn't be surprising that many readers still fall for it.

It's an amazing book, one of my favorites, but it's a book that has to be read - not skimmed.
On a gravity saddle, more accurately.
Funny, this doesn't sound like a spiritual successor to Atom at all. What made people excited about Atom (compared to Sublime Text, which people switched from and was ~always faster) was the extensibility.

Sounds like this won't have that. It's only a successor in the sense that it's built by the same people and tackles some of its challenges.
Makes me wonder if the authors were really unaware that wherefore = why or if they deliberately used it in the wrong sense to get us to talk about the article.
It seems pretty relevant for interfacing with humans
Why wasn't ProseMirror a fit for Obsidian? Seems like that would be better for structured documents.
In modern day America, working hard for things is a poor life choice. You're signing yourself up for a life of having to work hard to support everyone else who doesn't want to work.

You're much better off just taking it easy an mooching off the idiots who work all day.
The article mentions it’s a freshwater environment. Are they going to get wiped out if the ice melts enough to expose them to salt water?
Workflow applications gets reinvented all the time (there are hundreds of them out there plus many “standards”). However I have never seen a successful usage of workflow applications in industry. So my question is if anybody has any good examples of workflow applications being more successful than “normal” business applications?
JQBX is amazing. IWYM forever.
>It's just so disgusting to me to call yourself "antiracist" and then quite literally discriminate based on race.

Interestingly enough, the concept of anti-racist (despite the way it sounds) is racism by definition. I think some people use a different definition of racism to make this not be the case, but if you list out "anti-racist" policies you'll see they all contain racial discrimination in them.
Spectrum OS – Bibliography
A country would only see sanctions if it harmed a foreign powerful country. When multinational companies are suing multiple countries, there's no incentive for the countries to sanction each other.

ISDS provides barely-plausible deniability for giveaways from governments to billionaires.
NFTs can exist on most blockchains.

However only the big ones mean anything.

Your DB means about as much as a NFT on Luna.
It's so cute :)
I'm not sure if this feedback is useful, but I have to say that a collaborative text editor doesn't feel like that big of a sell.

Pairing in VS Code over Zoom has gotten a lot better over the last year or two, to the point that I choose it for simplicity over more purpose-specific tools like VS Code Live Share (which is a bit slow/glitchy but fine, and overall "neat") or Tuple (which is great).

Would I pay money for "VSCode, but faster"? Absolutely. I'm waiting multiple seconds for keystrokes to apply sometimes and don't know why. But the extensions are what make it VS Code – if I just wanted "a faster text editor" I'd uninstall all my extensions and just keep using VS Code (it'd blaze), or switch to Sublime.

I'm excited to see more people working in this space, so I certainly wish you luck!
I honestly can't think of a single piece of software on my current machine that knows my gender. It's really irrelevant.

EDIT: Yeah? That's why I said there's nothing to complain about. I just don't think they really needed to bother writing a paragraph to explain it. Most things are done that way anyway.
Receipts would not have mattered here.

The guilty parties were literally casting votes for people they knew would not show up.

It’s an identity issue, much harder, and with its own set of controversies.
Whats a statistical life?
I don’t think there’s anyone who knows too much in this project. They are just software developers.
No actually. When a sample has crossed the reporting timescale, and it's inconsistent. Regardless of if the db changes later or cache becomes consistent later, at the moment it's still an anomaly (inconsistency in this case).
It is fascinating, with a worrisome twist to it. The more stochastic we get, the easier it is to "zoom out" from the ground truth of individual lives.

Distant officials in high offices making Olympian decisions seem to produce mixed results on their best days.
There’s extreme moral hazard in allowing institutions to lend money on this scale while protecting them from the risk of a borrower’s default as well.
pyheif: Python 3.6 interface to libheif library
Dude, again, you could not be speaking more opposed my language. The gang marching against awesome great kick ass work like web bluetooth, web midi, web hid is absurd. These are epically useful & straightforward wins, huge capabilities, and this hemming & hawing & wringing of hands could not come off as more misguided & consevative & close-minded. But that wasnt even the case here, it was just... we dont get it. And you showed up in the thread & went off? Railed unreasonably?

Someome had to come & add, fill in the half dozen process events you ignored when you ultra-rudely came into the thread to piss all the situation. You are not hurting chrome by citing tbis, you are demonstrating your own axe grinding intempernace & hostile volatility.
Yeah! Fuck the Earth!! Me Me Me!!!
Can Australia and California countersue for the bushfire/wildfire damages?
Man that is really sad, but I suspect these code in the cloud schemes will be targeted toward hordes of developers with such a superficial grasp on what’s happening.
Similar things in a number's value v/s its number of characters I think is called True Number, & only 4 is a true number like 4 value & FOUR has exact 4 letters.
> Good work, but not a solution for cache invalidation.

Assuming your definition of cache invalidation is about "when/who" to invalidate on writes. Let's actually try solving it.

E.g. in its most generic form, a cache can store arbitrary materialization from any data source. Now when updating the data source, in order to keep caches consistent, you essentially need to transact (cross system transaction) on both the data source and cache(s). Usually cache has more number of replicas, I am not sure running this type of transactions is practical at scale.

What happens if we don't transact on both systems (the data source, and cache)? Well, now whenever the asynchronous update pipeline performs the computation, it's done against a moving data source (not a snapshot of when the write was committed). Now let's say the data source is Spanner, which provides point-in-time snapshots. On Spanner commit you can get a commit time (TrueTime) back. Now using that commit time, to read the data and compute cache update asynchronously can be done.

Because the materialization in cache don't take writes themselves, so updates to them are essentially performed blindly and can be ordered by the commit time (TrueTime).

Now this does assume whatever we cache (the query e.g.) needs to be schematized, and made known to the invalidation pipeline. I think it's a very fair assumption to make. As otherwise (anyone can cache anything without the invalidation pipeline knowing at all), it's pretty obvious that this problem can't be solved.
Other countries have NOT figured out gun control, as the recent fall of Hong Kong and imprisonment of the entire continent of Australia have illustrated.

The solution is not a simple one as you imply, otherwise it would have been solved already. Give people some credit!
I assume that they have to be reheated at the destination city before delivery. They may even be cooked there. In Australia several years ago you could get "freshly baked" French croissants from the supermarket. They were actually frozen "parbaked" goods that were cooked on the day.
It’s specifically for browsers to use in testing. The idea is that the glyph dimensions and positions fall exactly on pixel boundaries. Then you can make your css, html, SVG, etc test such that you can go through the spec and precisely specify the exact pixel value for an entire test output.

The ideal result is that each engine is able to render the same test and verify that their layout, etc is exactly correct.
You would think the worst is over, but no, now it's got larger than expected micro problems to deal with.
I've been talking to Nathan and think he has a good handle on the issues. One of the biggest mistakes in xi was an over-reliance on async and a loose coupling between the main logic and the UI surface. Zed isn't making those mistakes. I'm eager to see what the come up with and look forward to friendly competition in the open source Rust UI space when they release their toolkit.
Monotask to chip away at your to-do list
I'd hesitate to jump to the conclusion that all "TL;DR" comments are helpful. Personally, I find most of them to be (1) either too simplistic to learn much about the article, or (2) sarcastic dismissals of the article (sometimes by people who don't seem to have even read it). A good summary of a long article would require at least a well-crafted paragraph, not a single sentence.

So why not just rely on HN's already existing voting mechanism to figure out which comments should be promoted? If people find a particular "TL;DR" comment to be useful, they can upvote it, which causes it to move toward the top of the page. If they're not being upvoted, it suggests that most people aren't particularly enthusiastic about them.

Also, giving preference to any comment that begins with "TL;DR" might encourage people to abuse the feature to get upvotes (since comments at the top of the page are more likely to be seen and upvoted). For example, they could begin every comment with a hasty and not particularly useful "TL;DR" even if several better summaries have already been posted. Then you'd have a sea of "TL;DR spam" cluttering the comments.

Finally, a well-written article would have an introductory paragraph that summarizes what it's about. Any academic paper would have an abstract at the top. If you just click through to the article, you'll probably get a better summary than someone can put in a comment.
A timeless clip from Monty Python on the subject :

https://www.youtube.com/watch?v=WboggjN_G-4
Brave is awesome and runs circles around the others. Librewolf is technically more private but breaks too much of the internet. Firefox has jumped the shark as of late.
> conspiring to illegally vote in a federal election for orchestrating schemes to fraudulently stuff the ballot boxes for specific Democratic candidates in the 2014, 2015, 2016, 2017, and 2018 Pennsylvania elections

I'm gonna go ahead and guess 2020 wasn't tacked on for obvious reasons.
My theory is that this is why most enterprise software is terribly slow and buggy with horrible UX. If something works, and there is a completely coherent logically consistent system buried in the mess, people can and will usually figure things out. And the drive to make more features generally wins out over time above addressing technical/UX debt.
Presumably because browser were historically much better at handling and rendering English and Western European characters (and input) than they were at other scripts?
If you haven’t read it before, don’t read the Wikipedia summary; read the actual story. It’s easy to google and pretty short.

Isaac Asimov said it was his favorite story he’d written. He imagines the entire history of the future of humanity, to the end of time, in a few pages. Really a marvelous story.
Sadly sports funds large portions of some school budgets in the US. School funding is quite messed up.

Individually you feel pressure to move into the best school districts. Yet collectively it falls into racial boundaries because of decades of systemic racism.

Forced busing suddenly fixes a lot of the funding biases, but is very unpopular because fear of the other is hard to overcome.
A chance for us all.
In yesterday’s California election (Los Angeles County, specifically), it had me review all of my choices on the screen (after I was done), then it printed out the form so I could review the printed copy. Then (very confusingly) the final step was to insert the form back into the machine. Basically everyone was confused by this review and reinsert process, but still it seemed like a good system for ensuring there are no glitches.
Let's solve the "cache invalidation problem" by your definition.

E.g. in its most generic form, a cache can store arbitrary materialization from any data source. Now when updating the data source, in order to keep caches consistent, you essentially need to transact (cross system transaction) on both the data source and cache(s). Usually cache has more number of replicas, I am not sure running this type of transactions is practical at scale.

What happens if we don't transact on both systems (the data source, and cache)? Well, now whenever the asynchronous update pipeline performs the computation, it's done against a moving data source (not a snapshot of when the write was committed). Now let's say the data source is Spanner, which provides point-in-time snapshots. On Spanner commit you can get a commit time (TrueTime) back. Now using that commit time, to read the data and compute cache update asynchronously can be done.

Because the materialization in cache don't take writes themselves, so updates to them are essentially performed blindly and can be ordered by the commit time (TrueTime).

Now this does assume whatever we cache (the query e.g.) needs to be schematized, and made known to the invalidation pipeline (in the form of some control plane metadata). I think it's a very fair assumption to make. As otherwise (anyone can cache anything without the invalidation pipeline knowing at all), it's pretty obvious that this problem can't be solved.
> She also taught me to read 2000 words per minute with retention,

Can you expand upon this and/or link to any resources related to the method?
Lemuroid – open-source emulation project for Android [/TV] based on Libretro
If there were no snarky English teachers and pedantics to point this stuff out, think of all the knowledge that would be lost. The English language has a rich history and expansive vocabulary.
>>>How exactly did they give away the location?

They didn't, not with sufficient detail. Hence the need for the sonar on the submersibles, probably need to do some undersea mapping to pinpoint the wreck. I only know it is "near" Islas del Rosario. It's in water 950 meters deep, so the average concerned citizen can't exactly strap on a wetsuit and go poking around the ocean floor for it.

This site [1] from 2015 claimed it was in 300 meter waters, ~25km from Cartagena. Some of the infographics suggest it is NW of Isla del Tesoro. Maybe best to look at nautical charts of the area, and plot a course from west of Isla Rosario to northwest of Isla del Tesoro, along the part of the sea floor that is ~900m deep (course runs roughly NE). Map/scan that with the sonar on the submersibles, focus on major "outcroppings" that are possibly the San Jose (or the other two nearby shipwrecks). For a second pass, go straight to those outcroppings with a higher-resolution scan, plus visual cameras (use the released photos as reference for visual confirmation). Once pinpointed, send in the bigger cargo-carrier sub with robotic arms, excavator shovel, etc. and start scooping up the treasure.

Split it 60/40 with HSBC, and your team still gets to keep ~$4.7 BILLION. That's a better unicorn offramp than building yet another BS SaaS cloud app.

[1] https://blog.geogarage.com/2015/12/spanish-galleon-may-conta...
Makes me wonder how I survived public school - I never saw a volunteer in the classroom ever. They weren't poor schools, either, and this was back when moms didn't work.
You can make an argument, and I think many people have, that only rich people should be taxed and not corporations, because only some of the stakeholders in corporations are rich.

But there are two questions that I can think of raised by eliminating taxation of corporations.

One is, will the revenue be made up by increasing taxes on rich individuals; and,

Two, how can we prevent wealthy individuals from using corporations to shelter their income from taxes, if they are all tax free? I'm not sure it is a simple problem.

Plus, do the complaints about "double taxation" really make much sense in the big picture? Money flows around and around in the economy and gets taxed an unlimited amount of times in the long run.

Maybe there are reasons for aspects of the current system that seem kludgy at first glance.
>It seems pretty clear to me that in the video games industry (and pretty much any 'art' industry for that matter) great results are driven by singular, great people. Todd Howard was the mind behind TES and Fallout 3/4.

Pretty sure this attitude is what led to Daikatana. Cults of personality are universally bad.
Electron could probably be described as "a big chunk" of Atom's codebase. The rest of VS Code has a lot of similar functionality to Atom, so calling it "a rewrite" doesn't feel that far off (except insofar as it was redesigned as well, but that's sort of semantics)
IME most people IRL also think XP was the peak of UI design. Personally I prefer Windows 98 (really FVWM if given the choice, and I am given the choice so that's what I run.)
Zozotez: A tail call optimizing Lisp interpreter that runs on Brainf*ck
Try really.
Let's actually also try to solve the "cache invalidation" by your definition.

E.g. in its most generic form, a cache can store arbitrary materialization from any data source. Now when updating the data source, in order to keep caches consistent, you essentially need to transact (cross system transaction) on both the data source and cache(s). Usually cache has more number of replicas, I am not sure running this type of transactions is practical at scale.

What happens if we don't transact on both systems (the data source, and cache)? Well, now whenever the asynchronous update pipeline performs the computation, it's done against a moving data source (not a snapshot of when the write was committed). Now let's say the data source is Spanner, which provides point-in-time snapshots. On Spanner commit you can get a commit time (TrueTime) back. Now using that commit time, to read the data and compute cache update asynchronously can be done.

Because the materialization in cache don't take writes themselves, so updates to them are essentially performed blindly and can be ordered by the commit time (TrueTime).

Now this does assume whatever we cache (the query e.g.) needs to be schematized, and made known to the invalidation pipeline (in the form of some control plane metadata). I think it's a very fair assumption to make. As otherwise (anyone can cache anything without the invalidation pipeline knowing at all), it's pretty obvious that this problem can't be solved.
> excessive use of VLOOKUP

I feel called out. Maximum number of rows in a VLOOKUP in personal spreadsheet is like an array of 2x1000. In an earlier job, it was 13x39000. Excel automatically increases the range when you add rows in the middle. Then I split my data per year, & it was like 13x5000.
I'm sorry but you lost me at "pro-vaccine propaganda". Where's the characterisation of all the obvious disinformation spreading on social media (and rage-maximising MSM) as "anti-vaccine propaganda"? You're implying bad faith on the part of those spreading a pro-vaccine message and are making it their fault for "not embracing" or making "them" "comfortable". The problem with that is how can I embrace someone who believes that vaccines cause autism? How can I make someone "comfortable" when they can't see their own cognitive dissonance for seeing their doctors as shills for big pharma on one hand (vaccines), but will happily listen to and take their advice when it comes to, say, broken bones.

Do we need to do a better job of educating people about the fact that medicine, and "science" itself is not process of distinguishing black from white. Reality is imperfect and complexity is progressively discovered. Do we forego the imperfect now waiting for a perfect understanding of something? What happened to the Pareto principle, risk management approaches, and opportunity cost? I find it hard to feel like "embracing" people who take a mistake as evidence of conspiracy.

Don't the voices pushing the anti-vax disinfo bullshit carry some responsibility for polarising people's views and turning opinions against medical authorities? Or are they absolved of responsibility?