tsbinz

It's also possible that they are different from you (e.g. they have an IPD that's not in the range the headsets are designed for, or they are more sensitive to the vergence-accomodation-conflict) and still experience eye strain/headaches. I do own a headset and I also love beat saber and alyx, but I can't use it for too long.

Apple tries sneaking in iCloud syncing regularly, Adobe did it to me with their cloud storage as well. Sadly, behavior like that seems ok with product managers.

The content your parent comment refers to was (partly) what I saw when I installed it and scrolled through the default suggestions before it had the chance to learn anything about me. Sure there was a lot of harmless and just silly stuff, but the amount of animal abuse like https://twitter.com/noellesdesigns/status/122443946827220992... that scrolled by made me stop using the app.

default subs haven't been a thing since 2017 though (https://www.reddit.com/r/changelog/comments/65x4a7/testing_a...)

MS had x86 emulation for a while, but not x64 (Windows on ARM could run 32-bit binaries, but not 64-bit).

Unless you're very careful I think it should be detectable at those levels. If someone is taking the same amount of time when playing some rare and tricky opening line as they are when playing the QGD, that's pretty fishy if they don't have the level where you have a big variety memorized.

It doesn't (it does heavily push you towards it, but you don't need it), you can edit a group policy in order to be able to store the key on a usb drive or to use a passphrase.

Previous discussion: https://news.ycombinator.com/item?id=10567408 - title probably should have a (2015)

State senates are not the federal senate.

Colorspaces are an issue with scaling/averaging, but it's not what's happening here.

Opencv does use linear interpolation by default. What you'd need to do is to use something that helps against aliasing, for example first blurring the image with a kernel of the appropriate size or to use a scaling method like opencv's INTER_AREA.

Note that these are light models that are designed to be run quickly on a cpu with batch size 1. It's not that uncommon to see multithreaded cpu code beat the gpu in that setting also for other backends.

The problem is that "people can make that decision for themselves" only works if they themselves pay the price for their actions. If you're in the age range that is likely to get an asymptomatic or mild development, the price of you getting infected and walking around infecting others are paid for mostly by others.

"Let everyone decide for themselves" rewards the selfish and makes people that restrain themselves jealous of the selfish people. If that's the kind of society you want to live in, well, that's your choice. But I think a lot of people don't.

Maybe your goal was to "just" flatten the curve which, even if you don't overwhelm hospitals, still leaves a lot of people dead or with permanent damage. Others think the best strategy is (and some other countries' stated goal was) to push cases down to a number where containment strategies (tracing contacts and wiping out infection chains) work again. Some countries got too lax after the lockdown and let cases rise above tracing capabilities again, in other countries that still works.

It's sad that people fall for the "privacy first". I recently got a new Macbook and opting out of the cloud services was a real hassle, and sometimes the settings pop back on updates. Apple wants your data, they just don't want anybody else to have it.

I buy some of my devices from apple because I like the hardware. The walled garden is annoying and has nothing to do with resale value. The resale value is high because of continuing updates and nice hardware - you'd factory reset everything you buy second hand anyway.

If you were working for them like a regular employee, that has quite a few pitfalls - you'd need to perform the duties that an employer has then (get a "Betriebsnummer" (employer registration number), register your contract etc) - working "on a freelance basis" where you actually act as an employee isn't legal (https://www.existenzgruender.de/SharedDocs/BMWi-Expertenforu...). And if compliance is important for a company, they'd need at least someone that is familiar with labor law in a country before they start employing people there, even if they don't explicitly need a business entity.

We must be looking at different chess streams. Bullying is super common in a lot of the popular ones, and some of the mods take part in it.

If you've been to Zurich and your mobile reception was bad, you either were using a bad provider or your phone has issues. I'm on the swisscom network, and the only time I lose 4G is when I go to the mountains.

And if what you say is true I suspect the provider dependency is also true in the US as I hit quite a few holes when using an AT&T sim card on a road trip through the US.

There is a couple of things to keep in mind.

First, like others mentioned, they are way off in the effect size, for this kind of time dilation you need 80% the speed of light, not 8%.

Second, when looking at time dilation caused by velocity, it is always necessary to say who observes what since observers that move relative to each other won't agree on which clock runs at what speed. If the star moved at 80% of the speed of light, someone on that star would say "When a 100 minutes pass here, only 60 minutes pass on Earth" while an observer on Earth would say "When 100 minutes pass here, only 60 minutes pass on that star". So both observers would say that the other's clock is running slower than their own.

This answers a part of your last question - time dilation always makes clocks appear to tick slower than your clock if they move relative to you.

There are other effects that can make things appear "sped up", there's all kind of odd things happening when you go to high relativistic speeds ...

It looks like someone (in addition to forgetting to clearly state where the observer is) forgot a zero when putting it in the calculator, at 80% of the speed of light you get the time dilation factor they state.

I'm not saying that a compiler shouldn't flag this. I'm just saying that current compilers don't.

I'd guess that static analysis tools do flag it, but haven't checked.

The parentheses here aren't actually "extra", without them the meaning would change - since && binds tighter than = without the parentheses the left hand side of = would not be an lvalue and compilation would fail.

I would be careful with statements like this. New compilers do NOT make this a warning/error, see for example

https://godbolt.org/z/5zzz33

Note that there are parentheses around the assignment which the compiler takes as an indication that this is intentional. Also note that the parentheses are required because without them the precedence would be wrong.

No, a traditional newspaper optimizes for number of subscribers/readers, not for time spent reading the newspaper. It's online ads that change the equation.

The problem with contact tracing apps is that their effectiveness has a quadratic relation with the adoption rate. They would be mostly useful to trace "random" contacts (since you tend to know which of your friends and family you saw within the last 2 weeks), but to be able to trace a possible infection both the infected and the "recipient" have to have the app and active. In Germany they said their 12M installs is "good" but that's just 15% of the population, so if you'd take a random pair the chance to detect a link is 0.15*0.15 = 2.25% ... so it's obvious that this isn't going to move the needle much. So in order for this to be effective, you need to have very high adoption rates, and it can only help in addition to other measures (wearing masks, hygene, avoiding indoor gatherings, ...)

It wasn't paid in the US. The purpose of the scheme that Apple (and other companies) were using was to protect profits from US taxes.

https://en.wikipedia.org/wiki/Double_Irish_arrangement

Hm, if the statements in https://www.youtube.com/watch?v=bvim4rsNHkQ are correct that failure was because they ran out of hydraulic fluid, not software (but maybe/probably that's not the complete story)

I'm not sure you need to do that (define singular values via the operator norm), but one thing I don't see a solution for is getting rid of the requirement of the inner product for the definition of the adjoint.

Small correction: It's not the full hash that appears in the results, it's the suffix (so the part after the 5 chars you put into the URL).

If you don't want the password to end up in your shell history, this works on in the shell with common tools:

tr -d '\n' | sha1sum

Then type the password you want to look for, hit enter and control-d. You can test with "common" passwords like https://www.reddit.com/r/XFiles/comments/6ge7h4/mulders_home... if you're doing it right.

And if you are really paranoid, you can just download the whole set of hashes and do the lookup yourself.