skysight-inc/HackerNews huggingface dataset:
Well they have value in hearing others and being heard, I'd assume. All my friends have their own mics because we couldn't understand eachother otherwise, and we don't have problems with fidelity. My coworkers are a different story, because consumers rarely listen to integrated microphones before they purchase a device (bluetooth earbuds are absolutely terrible about this, fwiw). Who's at fault, the company for cheaping out, or the consumer for not caring enough to find out if they company cheaped out?

The technical problem is solved. The economics problem of getting people to value the solution and marketing problem of educating about it is still open.

Regardless, this isn't a problem to be solved by software. It's a consumer electronics problem.
> (CAPTCHAs use similar techniques but result in more UI friction.)

Not only are they inconvenient, but they're often inaccessible for some users. So I just wanted to say thanks for not going that way, even if the cost we must pay is some theoretical compromise in privacy.

Edit: On thinking about this some more, it occurred to me that by using a user's activities on a web page to determine whether they're a bot committing fraud, you might be inadvertently penalizing users that use assistive technologies, such as a screen reader, voice input, eye-tracking, etc. I haven't had a problem with this when doing a Stripe checkout with a screen reader, but I just wonder if this possible pitfall is something that your team has kept in mind.
Airbnb: Binary Alert
State and federal governments are even worse than local with regards to endless regulations.
Good job on helping to curb mindless browsing!

On this topic, another add-on I have found to be fairly helpful is called "Pluckeye" [1]. At its base level, it simply blocks all images and video from your browser. You can customize it by adding/removing websites from the blacklist, and is fairly robust to occasional cravings by having a delay on changes to the blacklist that allow a website. The only downside is that most websites now look broken, but I've found that I don't really miss being bombarded by the colorful graphics on websites.

I think there is significant work to be done on making these tools more widely known, but I'm happy with the progress being made. Good job, again!

[1]: https://www.pluckeye.net/
You reply just sounds condescending. Yes, smokers (myself a smoker) know that their logic isn't ideal on this and we're aware that much of it is biological and emotional, but there is room for reasoning about when to try quitting for a less stressful and more likely optimal result. We're not simply blind rats in a cage just because we have this ferocious addiction, and we don't need to be implicitly told by others that all such reasoning about how or when to go about quitting is nonsense, that we "should just do it".
In weak cases, lawyers from either side will try to confuse some of the issues. But the rules of evidence, criminal trial procedure rules, and the presiding judge can make this difficult.

Also, even though good research about jury deliberation is limited because they are conducted in secret, I recall (from memory) that research shows juries are pretty good at detecting when someone is trying to deceive them.

Further, in trials, the opposing party gets a say in the matter too. If one side says something deceptive or deliberately confusing, competent lawyers for the other side will point this out and attempt to correct the record, possibly turning the jury and the judge against the deceptive lawyer.
Other than the practical reasons (Zeit is a common German word) their product and focus has changed quite a bit.

They started as serverless docker and changed to CDN + edge cloud functions to specialized hosting for front end projects.
$1B, but it landed at about $750M because of the FB shares that took a tumble just after.
Don't Mess with Texas
This is not a response in this "argument", but, please watch "Citizenfour" and/or Hollywood version "Snowden".
Having done some anti-fraud work in the past... that is
Not something I would turn off for some over wrought privacy concerns. There is a reason for the GDPR exemptions for this.
I mean, looking at that page, AMD's current real consumer offerings probably bottom out at the Athlon chips. I haven't seen an FX chip in a newly released system in a long time, and the A-series chips seem to be on their way out, even in the small chunk of the budget laptop market where they ever had any real share.

So Ryzen is arguably most of their consumer offering right now.
Glad to have struck a nerve with the Rust evangelists.
Except that for whatever reason people don't do this so the advantage continues to exist. Possibly because there aren't enough remote jobs?
> Kerckhoff's principle applies

That's true and yet unhelpful because all software has errors, some obvious, some not.
I missed this in my previous reply ...

> Look at all the results. Even before that exceptions are more often a win than a loss.

The blog post you linked to effectively says "it depends"
> Also consider how much faster / cheaper it would be for a studio to create new graphics engines when you only have to write 1000 lines of ray tracing code instead of 100'000 lines of rasterization hacks (for a worse-looking result!).

You were talking about games here, no? That's ultimate hard time constraint.

1000 loc gets you a very basic path tracer which isn't really going to be good for very much.

Your dispersion example is interesting - you can't really do it correctly with rasterization, no, although you can do a distorted background texture lookup with individually offset/blurred RGB channels. If you want to do rough glass you can just increase the blur amount. Not correct but looks 'good enough' in a lot of cases.

With ray tracing you can just trace 3 rays (one for one for each of red, green and blue). Simple! Except can you really afford 3 rays? Also how much do offset them by? You could use Cauchy's formula and use real refraction indices, but then you're going to get ugly separation between the channels. You could sample the whole visible spectrum and use temporal accumulation to build up the correct color, but now you've got color noise. What happens if you want to simulate rough glass? That's going to be very noisy indeed.

What about shadows from the glass? You can't afford to render caustics to do it correctly after all. Do you just ignore them? That'll look weird. Use a fresnel-weighted transparent shadow? Probably but now you have to handle that correctly everywhere and running a shader for shadow rays is expensive too so maybe you have to special-case that situation so most of your scene lands on the happy path.

My point is that anyone can write a basic path tracer in a weekend that will correctly simulate light transport given an infinite amount of time. Writing a renderer that will produce an image of a given quality in a given amount of time, incorporating a list of effects that an art director has decided are essential to the look of you product, is a very hard task still. It's simpler in a lot of ways, but also has to handle a lot of other complexities for the things that aren't possible in a rasterizer but are still very expensive to compute in a ray tracer.
> There is no foil on my head, but

Good thing, because this would amplify radio frequencies. This trope needs to die.
The 2 parking space rule is because we allow people to park on the street overnight. It's very simple to just not allow that or if it's allowed, then charge a market rate for the space. If people want parking then the house can have it, or there can be a garage. The problem is that they're getting a public good for free - free on street overnight parking.
> first or last name, physical or email address, SSN, telephone number, or any contact method I am familiar with (maybe you know a way?)

What about a face? Fingerprints? Voice? Aren't those identifiable information even though it didn't make your (common sensical) short list? Mouse movements are on the same order of specificity.

Edit: Also not giving legal advice.

Edit2: Please see https://news.ycombinator.com/item?id=22939145
> KGB doesn't exist anymore

it actually does [0] - at least in belarus and some of the russian-occupied pseudo-republics

[0] https://en.wikipedia.org/wiki/State_Security_Committee_of_th...
14 days is, I believe, the estimated 99th percentile for incubation time, not the mean.

Mean is more like 5 or 6 days.
I know from actual experience that trying to explain why medical false positives can cause more harm than good to the layman is ludicrously hard.
In fact quite a number of people are out there working for free because "it's the right thing to do in a crisis."
I really despise when ‘researchers’ make such belittling claims about ‘people’ (not them of course). The first assumption when observing something, anything, should be that there is a good reason for it. Assuming that other people are stupid is the similar but opposite fallacy as assuming that a stage performer has magic powers.

As in other posts here, it’s not hard to find good explanations for this observation.
sd is 24 years old:

http://sed.sourceforge.net/grabbag/scripts/sd.sh.txt
Well, most of the people who made it, and the early adopters tended towards being rational, eh?

Boiling frogs and Eternal September and all that.
That may depend on some specific knowledge of the code, which is of course why they were asking for it.
There is clearly too much government and there is regulatory capture - are you saying these aren't true? Just because some regulation is deemed good doens't mean the majority is.

There is a bias that the present and recent history is how things are and should be and that any changes require superior proof than the initial experiment in passing the legislation.
Epic Gives in to Google and Releases Fortnite on the Play Store
Show HN: Distributed Caching on Kubernetes with Olric
Conceptually, panics should be rare, because one firing means that some sort of unexpected problem has occurred.

However, the real world is not "conceptually." I don't think there's any real data about how often they happen, but at least my experience is that tools I write in Rust rarely end up showing me panic output.

> That's not the case in C++ where "throw" is a keyword you are expected to use for error handling.

Yes, that's correct. The intended semantics of the two features are very, very different.
Labs for Rust OS – CS-3210 at Georgia Tech
one day you will realize that your body was prio #1
There are undoubtedly recluses, but do they also have frequent contact with people to catch diseases from?
I only use the PostgreSQL adapter only for a very simple database, so I can't comment on it.
Byton furloughs hundreds of workers with unknown impact on production timeline
That's how it should be to be honest. In critical situation people cannot be trusted and procedures must be enforced. Even if most people would follow the rules, the issue is that a minority always wouldn't, with devastating consequences in these circumstances.

I also believe that anyone arriving in China now is kept in isolation in a hotel for 2 weeks whether they like it or not. No "please self-isolate", just 'soft' detention.
I can see how one could have that view. But in practice the role of US juries is limited to determining facts. The judge and appellate courts determine how the facts apply to the law.

Also, judges presiding over jury trials can set aside jury conclusions for a variety of reasons. And higher appellate courts can do so as well.
Being NSA they could have easily have gotten source code in the covert way - one of the employees had copy at home, they emailed it around! But for encryption software there is no value in source code in the first place - algorithms are standard, and software can be disassembled anyway. All access to the source code does is allows them to save time on disassembly. Author knew all this and this is why he gave them source code in the first place.

Basically fabricating this story and risking exposure just wasn’t necessary.
I have yet to hear of legally binding definition of PII that involves mouse movements.
Even with caching, SourceHut is a lot smaller than that. SourceHut benefits from caching, too - the repo summary page comes from 2 requests and 29.5K to 1 request and 5.7K with a warm cache. And in many cases, the cache isn't the bottleneck, either - dig into the Lighthouse results for specific pages to see a more detailed breakdown.
Absolutely. The problem is that nobody gets promoted for slowly incrementing on an existing product.
And your I-94 is automatically extended with your visa extensions. Its your visa extension date that has the precedence.
To be truly open in terms of privacy, open-source + auditable open releases is the way to go.

I'd recommend a free extension with a paid plan which has additional features. Provide the basics in the free version and the really good stuff in the paid version.

If source code is the same and it's just feature flagged based on a ping to a server to validate a license key, then it'd be indeed easy to copy the paid features in another extension. To a large extent you'd be relying on the web store moderation a copy to not be published and to tech-savvy users to not install it locally.

However, that approach could ensure a wider reach of users so the share of the paying ones to be big enough in absolute numbers.

Marketing the extension to non-developer audience would help reduce the chance of manual installation.

The biggest difference would be that the developer audience could contribute to the open-source code and you'd be making money from those contributions. I don't think the income from that alone would be enough to support you in the short-term, but in the long-term with good expansion with other products, that could prove to be a very strong passive income.
> I'm sorry but if you think the NSA is the shadiest

You're right about the detail (probably) and also very wrong to be focusing on that particular detail instead of interpreting it as just barely mild hyperbole.

You've gone to "it's not the absolute worst, therefore I dismiss the statement" instead of "it's not the absolute worst, but it's still really fucking bad so I'm going to recognize the premise and move on".
I set up a Minecraft server for some friends a few weeks ago, and I learned firsthand how huge of a performance improvement one can get by dropping the render distance.

My basic understanding of the problem is that it's less of a graphics problem and more of a CPU one. Loading another chunk requires the game to actively simulate everything happening in that chunk, and, since the game is single-threaded, increasing the number of chunks loaded quickly causes the amount of work needing to be done per tick to explode.
Sorry for the delay in getting back to this...

All the engineers went to work for Oracle and were given large incentives to stay for 2 years. Most stayed and got their incentive payouts, though they all eventually left later on. I think the longest tenure at Oracle there ~8 years.
is it just me, or did MacOS get uglier with each release?
From the number of cooking programs on my TV with british cooks at the moment I would assume the british have upped the game a bit on cooking :-)
Sorry for the delay in getting back to this...

The wind-down cost was very small in comparison to the price Oracle paid.
Why is it that in recent years, with this and the more recent ls quoting fiasco, maintainers of longstanding UNIX utilities suddenly got the urge to fix what isn't broken?
On the off chance you see this, I'm pleased to report that the answer is, no! It works brilliantly as long as you use the free "Parsec" service's client to access the desktop and your games. Browser access to the Paperspace desktop is fine for normal app use but no good for gaming.

Setup wasn't quite push-button but I got it up and running by dumbly following the instructions. Parsec was the most confusing part. Trust the docs, and it'll work.
You might be able to point to a regional power and say yes, these guys are pretty shady. What you have to remember though, is that the USA is a global power with global reach, so any shadiness is more scalable. Also, don't forget that the US often does stuff like hand people over to another agency knowing they'll be tortured.

https://theintercept.com/2017/07/20/cameroonian-troops-tortu...

EDIT: Don't forget that NSA acquires data to create actionable intelligence that can be passed onto another actor. Whatever you think about them, their work is being used in many cases ultimately by another agency or government.
It's less my short list and more the one in the text of the law being cited. Other things, such as finger-, voice-, and face-prints were probably not contemplated by lawmakers in 2003 and thus go unmentioned. They may fall under the "maintains in personally identifiable form in combination with an identifier" clause, though.

Of course, that also provides an easy way to comply. Don't store mouse movements in a way that ties them to PII under CalOPPA, and you don't meet any criteria.
There is rank speculation about strains and temperatures - some of it based on case rates and death rates which is just pointless if comparing NZ and say the US because our situations are radically different.

1/3 of NZ infections are returning NZers, making up the vast majority of initial infections detected weeks ago.

The community transmissions are spread around the country, and unlikely to have a single super-spreader as the source. Our health system (including ICU wards) is vastly under-utilised at present, so any cases are getting the best care possible, and we have first world healthcare. There is no elective surgery at present, and our hospitals have been funded by our socialised healthcare. We could do with more PPE gear, but we have sufficient because our health system is not overloaded, because our government listened to good advice.

Let’s pick NY as comparison: confirmed “132,467 cases, including 9,101 confirmed coronavirus deaths and 4,582 probable coronavirus deaths“. Assuming death rate 0.5% after 3 weeks, then actual cases is in the millions. With that sort of community transmission then strains could make a difference. NY state has approx 4x the population of NZ, and 1000x more deaths.

NZ has a few thousand cases, NY has a few million cases. NZ acted fast and hard as soon as community transmission was detected. That explains the difference in deaths, and you can’t jump to any conclusions about death rates because the relevant numbers are too imprecise.

Either way, I expect NZ will sequence the different clusters, so in time we will know
This is not a well-formed question.
The abstract in this is really great, a full lineage of the product going back to 1965. Yet short and concise. Beautiful!
C'est pas mal :-) Je connaissais pas. Merci pour le lien pioc !
Source availability helps in crafting successful exploits in the real world.

Providing the source of a closed source project to an adversary so that they can break your software is nefarious.

If the author's justification was...

"My crypto implementation is perfect. There are no bugs in my code, so providing source code (which the user community does not have) to an adversary does not have any effect on any user's security."

...then the author is simply incompetent, not malicious. But I am not inclined to accuse the author of such incompetence.
Can anyone recommend a better shopping search engine or price comparison tool?
New Zealand definitely benefited a lot from being a remote island nation but our response also got a lot of things right. For example, being quick to implement travel restrictions and eventually a closed border. The other example that stood out to me was that the country decided to go into its highest level of lockdown when the first cases of community transmission were detected (I believe when it was decided we had 2 cases of community transmission).

So I definitely agree that NZ benefited a lot by being more remote and having no land borders, but we are only doing so well because we didn’t underestimate the virus and took drastic action early.
Aerodynamically equivalent Covid-19 1.5m social distancing for walking&running [pdf]
So what you are saying is that everyone should work for minimum wage, and any wage in excess of that is profit?
That's the thing with SSR... (i.e. with Next) or with pre-rendering apps before hand. In the initial GET request to the page, you also send a cookie with user preference. Depending on their dark mode preference you can style the page to be in dark mode as part of the server or pre-rendered markup -- no JS required :o. Now.. how difficult that is to do with Gatsby I don't know. But the fact that someone shot themselves in the foot with Gatsby, then learned to hobble along on one foot isn't a cause for celebration imo.
"Developers reveal why more aren't using it" is the rest of the title.

Developers reveal that more aren't using Rust because it's not widely adopted enough? That seems... a bit circular, maybe?
Not many American students want to get graduate degrees compared to international students and most people who apply get into the programs. They're not free for Americans. They pay in state if they're residents at state schools or pay the same as international students if at a private school or if theyre out of state.
> So treat them as bytes.

Which was my entire point!! You have to go to bytes to get correct behavior. They didn't fix the nonsense by changing the default data type to a string, they just made it even more roundabout to write correct code.

> It just made it impossible to inadvertently treat bytes as a string in a certain encoding

It most certainly did not! It's like you completely ignored what I just told you. I already gave you an example: sys.stdin.read(). Uses some encoding when you really can't ever guarantee any encoding, or when the encoding info itself, is embedded in the byte stream is the normal case. How do can you know a priori what the user piped in? Are you sure users magically know every stream's encoding and just neglecting to provide it to you? At least if they were bytes by default, you'd maintain correct state and only have to worry about encoding/decoding at the I/O boundary. (And to top off the insanity, it's not even UTF-8 everywhere; on Windows it's CP-1252 or something, so you can't even rely on the default I/O being portable across platforms, even for text! Let alone arbitrary bytes. This insanity was there in Python 2, but they sure didn't make it better by moving from bytes to text as the default...)
Or you could just not collect information you don't need? You don't have to ask consent if you just don't do it, you know. The pop-ups are annoying because the website owners want you to just click through. Ever seen one of those where you have to uncheck every single box? Yep, those violate the GDPR. The default setting should be no advertising or other bullshit data, and opt-in if you want it. Which no one ever does. Hence the violations. Get mad at the manipulative ad companies, not the people who for once produced an OK piece of regulation.
Suzanne Treister's fictional video game stills
The way I see it, Google tends to imagine that they have to handle all the complexity and not leave their users the ability to handle things themselves. They want everything to be a revolution. Google tries to deliver the "one true way" for building things.

What they miss is that users are actually pretty proficient at building things the way they're used to. Even if that way isn't necessarily the most efficient it's what they're good at. And they don't actually need or want a revolution, they just want to plop some existing infra into a hosted datacenter, or spin up some dumb VMs and run some dumb VB app on them.

I work in Azure, and I like to work on cool new things like Google imagines as well. But I have to admit, the vast majority of the money comes from dumb functionality that allows users to lift and shift. This seems to be what Google has a hard time accepting.