jxcl

> - Opens in App Store, which gets stuck (as always) asking me for billing info.

> - Rustle around for PayPal password. Why not just provide a .dmg?

> - +4 minutes, finally get App Store working. Download.

This seems to be more a complaint about your operating system than the app.

This already exists to some extent: https://mycroft.ai/

> Fever, red eyes, overflowing mucus, extreme soreness and raw throat for days or over a week - are you trying to tell me that this isn't sick?

I'm saying (and so is this study) that these symptoms are not necessarily due to infection. You strain your body to an incredible degree when racing, so it's perfectly plausible to me that these symptoms are just the body recovering from the strain rather than fighting infection.

This is all anecdotal evidence that's pretty well countered by this statement:

> Their first conclusion was that athletes are lousy at identifying whether and why they are sniffling. The original 1980s studies had relied on runners’ self-reports of illness. But newer experiments that actually tested saliva showed that less than a third of marathon runners who thought they had caught a cold actually had. Statistically, their odds of becoming sick were about the same as for anyone else in the race’s host city.

I agree with the concept of free-range parenting, and I see where you're coming from re. civil offenses for frivolous reports, but that carries the burden with it that perhaps some things that should be reported will go unreported. Isn't the reverse better?

The style of writing may well be very attractive, but it's important to remember that you're reading scientific articles written about forty years ago, and above that, in fields that are both advancing very quickly.

I don't have the opportunity to read the linked magazine right now, but I wouldn't be surprised if much of the research cited in it has been disproven.

One of us misread the article. I understood it to say that they want to rewrite the core of the Python code to Rust so that they don't have to wait for the Python interpreter to start every time someone uses the hg command. The Rust binary will be able to call Python code, which is basically a complete reversal of what they have now.

I figured that would be the case so I tried to middle click the pricing page and found that that wouldn't work either

The also have "climate change" in quotes in that article and the phrase is a link to this article:

http://www.shtfplan.com/headline-news/new-climate-study-thro...

It doesn't seem like there is. mozilla.debian.net says:

>Jessie and Stretch backports of Firefox release and beta are gone because of the requirement of rust to build them, which is not available in Jessie or Stretch. Please update your apt sources to use Firefox ESR instead.

I've downloaded the tarball from the firefox homepage, extracted it, and put it in ~/opt, and symlinked it to ~/bin/firefox, which is on my path first.

> and specifically it was obvious after first use what was happening.

Sure, it's obvious after the first use, but if somebody is taking a screenshot of sensitive information, is the best way for them to find this out to show them that they've already uploaded said sensitive information to Mozilla's servers?

I'm really confused by the graphs. The axis are labeled exactly the same, so I don't understand how they're ordering these logos within them.

I've been working my way through the podcast "A history of philosophy without any gaps". I find the episodes are a perfect length for my commute, and the presenter seems to be pretty well informed:

https://historyofphilosophy.net/

Because a kg goes into 5 lbs 2.2679619 times, and 5 lbs goes into 1 kg 0.44092452 times.

Do you know about the `units` command?

  $ units
  Currency exchange rates from www.timegenie.com on 2017-08-24 
  2980 units, 109 prefixes, 96 nonlinear units
  
  You have: 5 lbs
  You want: kg
  	* 2.2679619
  	/ 0.44092452
  You have: 100 furlongs
  You want: meters
  	* 20116.8
  	/ 4.9709695e-05
  You have: 100 miles/hour
  You want: meters/second
  	* 44.704
  	/ 0.022369363
  You have: 2 kiloisraelnewshekels
  You want: picodollars
  	* 5.5271109e+14
  	/ 1.8092635e-15

I don't have any particular advice. I searched the web for astrophotography stacking and used some software I don't remember the name of to do it. Sorry I can't be more helpful!

I'm going to be pedantic and air a pet-peeve of mine. "Raw" isn't an acronym. It's just shorthand for raw image data. It's not even the file extension of most (any?) camera raws. Why does everyone insist on writing it in capital letters?

> don't you need a certain "minimum" time to capture the faintest of stars, because their signal otherwise wouldn't rise above the noise floor?

I'm not an expert or even very knowledgeable on image stacking, but I'll share my experience.

I've taken a stacked picture of the Orion constellation. 15 exposures at 5 seconds each, and combined them to get this photo:

https://www.flickr.com/photos/abliskovsky/31756623694/

In none of the individual exposures is the Orion Nebula visible, but in this photo it's pretty clear. So in the end I'm fairly sure that your statement is true, but the signal required is very, very faint.

> The histogram tells much more of the story (if not the whole truth).

I feel that this is worth expanding on.

Because a raw file isn't actually image data and instead just straight readouts from the sensor, it doesn't make sense to show the histogram of raw data; the data has to be manipulated into a jpeg first. The histogram in the camera will show the lightness values for what the in-camera image processing computer does to convert the raw file into a jpeg, but the in-camera image processor is usually not as advanced as a desktop image processor. It's probably running older image processing algorithms and has to worry about battery life among other things.

So generally what this means is that if your camera is telling you that parts of your image are over or under exposed and therefore clipped, it might still be possible to recover those parts of the image in a more powerful image processor. It's also worthwhile, if you've got really old raw files, to go back and reprocess them with modern software. Raw file processing has come quite a long way in the past decade!

I agree that any company that asks for more than 40 hours should not be allowed to have the work/life balance key value. The profile says that the company eats dinner together and people go home at 8pm. That sounds pretty work centric and not much time for life left after that.

Raymond Hettinger, if I remember correctly, is the person who originally wrote NamedTuple, and he's not shy about reminding people during his talks at conferences. I wonder if his pride or other personal feelings about that particular module could be clouding his judgment over whether or not to optimize it?

This is a very useful site for Debian security issues:

https://security-tracker.debian.org/tracker/source-package/o...

In a similar vein, not letting the camera do the B&W conversion in the viewfinder will train your eye to look for tonal differences and will help you see possible B&W compositions before you bring your camera to your face.

My favorite videos of his are not the ones where he shows off new video games, but the ones where he delves into space history and engineering and astrophysics. He's taught me so much!

This is a great video that explains the current thinking behind the cause of the explosion:

https://www.youtube.com/watch?v=mBcoTqhAM_g

I appreciate what you're trying to do, but unfortunately this is kind of the problem with the Google culture. Everything has to be done with automation and better tools because they simply do not have the ability to go through the massive amounts of customers that they have without them. Unfortunately, at some point you need a human on the other end that can make a decision, especially with refund/warranty cases.

Because encryption can be decrypted with the correct key. A hash can't be reversed once you've hashed something with the pepper.

As long as there's no possibility of a remote exploit, this actually seems pretty cool. You're telling me I can plug a computer into my jeep and automate things?

Maybe I want to have the car roll the windows down for a while if the interior temperature gets too high. Maybe I can get my own version of climate control by controlling the AC via the CAN bus. Or maybe I can use my dashcam and some CV software to automatically switch my high beams on and off for oncoming traffic. It's actually pretty exciting.

In case anybody missed it, Backblaze publishes their raw data, so it should be possible to do this analysis:

https://www.backblaze.com/b2/hard-drive-test-data.html

I like the idea that if you took both necklaces and shuffled them around in a way that neither you nor the shopkeeper knew which was which and then gave them both back to him, you would have essentially robbed him without taking anything from him.