jbg_

I don’t know much about GPS jamming, but I know a fair bit about how airliners navigate. GPS is usually not used for final approach, which is typically either visual or ILS (a radio signal transmitted from the ground). This in contrast to the earlier stages of approach which may use GPS depending on the airport and the specific approach in use. If you can keep the jamming signal contained to the immediate airport vicinity and a few thousand feet above, there should be little or no impact on (non-drone) aircraft navigation.

I received this mail from Namecheap today with the subject line "Important: Potential Internet Access Issues".

Apart from the weirdly misleading subject line, the advice in the mail is really misguided IMO. If your ISP fails to update their trust anchor, disabling DNSSEC entirely for your domain will indeed let you access it again, but it won't do anything for other sites that you can't access, and it rather defeats the purpose of enabling DNSSEC in the first place if your first troubleshooting step is to turn it off again.

Many of the products Google has already shut down would easily have passed a reasonable good faith judgement that they were too expensive to keep running. I don't see how this would be any different. I know that "reasonable good faith" is a legal term of art, and I'm saying that I don't think Google would struggle to meet that standard if they needed to shut one of these services down.

... unless they decide that giving one year of notice would be too expensive or hard.

It doesn't seem relevant to the subject of the article, and it's private, so I don't see why it should be detailed...

Betteridge's law.

Chances are, a smartphone isn't going to give you the DoF you want (except by "faking it" using post-processing). There's a direct relationship between aperture for a given focal length and the front diameter of the lens. With a tiny lens and a low f-number, you're going to have a small focal length and therefore a wide DoF.

Non-AMP URL: https://www.washingtonpost.com/business/2018/08/06/how-year-...

On a single project, I agree. But each time I start a new pet/side project I like to use a different stack. It's a good motivation to learn new technologies, and you learn more about them by using them "in anger" than you do in a purely theoretical environment.

I know several people that are dual citizens of China and US. China doesn't recognise the second citizenship, but that doesn't prevent you having it. If China finds out, though, they'll apparently strip you of your Chinese citizenship.

There's no such thing as serverless, just someone else's server.

Wait... people who bought into a currency that is majority-owned by one entity would like some say in how that entity spends it?

OT but what do you mean by "English speaker with no accent"? Clearly every person has an accent, and every system that understands language must be able to understand the various accents that people have.

which will, of course, trigger the reminder as you walk down the street away from home, forcing you to go back and get the change of clothes that you forgot.

when in major cities in China, my experience is that Google Maps is almost unusable (not due to the censorship, as I use a roaming SIM which avoids those problems, but rather due to wildly incorrect data, missing metro lines, etc), and Apple Maps is at least on par with the quality that Google Maps achieves in other countries, and often much better.

I find it interesting that Google doesn't care enough to add the most recent several metro lines in (for example) Beijing or Shanghai, considering that many people try to use Google Maps in China when visiting and usually seem to end up switching to Apple Maps as a result of the complete trash the Google Maps experience is there. I wonder if they switch back when they go home.

yes, I've done this

You left out the very important detail that practically speaking, your content also needs to be hosted on Google's CDN if you want to get any of the benefits that content creators are likely to care about (being boosted in SERPs).

There's a recurring theme in the discussion of this (and actually any time there is a discussion about email), that self-hosting email is really hard. That hasn't been my experience. I've been self-hosting four mail accounts (with moderate to high usage) on one server since about 2007. I briefly tried gmail when it came out but never switched to it.

In 11 years of self-hosting my mail I've had one deliverability problem, which was when outlook.com users stopped receiving our mail. I wrote to outlook.com, and it was resolved within 24 hours. This is possibly because my server is located in a reputable, but relatively small, datacentre, and not on the likes of AWS.

I use the zen.spamhaus.org DNS blacklist to reject connections from spammers outright, and do SPF checks. These two methods alone (no Bayesian or similar filtering) mean I get about one spam message per two days on average, which I just delete.

I estimate that I spend about half an hour a month on keeping the server up-to-date etc.

I consider the downsides extremely small in comparison to the benefits of controlling your own email setup. I encourage anyone with even basic server administration skills to try it. Email is a fantastically decentralised system and we should take advantage of that.

Just wait until Angular 2 hasn't been cool for a while and you can't find any JS developers who are interested in maintaining your software rather than rewriting it in xyz_latest_fad_framework.

I've known plenty of developers whose automatic response to `packagemanager install packagename` failing is `sudo packagemanager install packagename`.

The article is fictional - but designed to sound plausible in order to make web developers think about a problem.

Out of interest, do you know if the game data uses XMPP or if it just uses the same port?

Right, but the address is "One Ferry Building" which works fine on Apple Maps. Not "One San Francisco Bay Trail", which only appears on Google Maps. So the problem seems not to be the vanity address per se, but possibly the way that Google has accidentally combined part of the vanity address with the "street" that it thinks the building is on.

The problem actually seems to be that "One San Francisco Bay Trail" is not the address of the building. Only Google Maps shows that address. So, ironically, what the OP thinks is an Apple Maps issue may actually be a Google Maps issue.

At least for me, next to each result is a list of the engines that returned that result. I run searx through Tor, so I occasionally find that Google stops returning results for a few minutes.

It doesn't happen often, but it's easy to tell when it does because none of the first page results have "google" next to them, while of course normally most of them would.

This is not how searx works.

I also run searx self-hosted, configured to proxy all its queries through Tor. Occasionally one of the engines doesn't return results (probably due to blocking), which is barely noticeable since several others still work, but normally all the engines including Google return results.

Since searx doesn't store cookies returned by the search engines, and I'm using it through Tor, I think this is a significant improvement over sending all my search queries to Google directly from my laptop.

A fingerprint is just a really complex password that you leave on everything you touch. Your face is just a really complex password that is written on the front of your head.

It should be self-evident that neither of these is "secure" for some level of "security", but they might be perfectly fine for the level of threat that you face, which is not likely to be particularly high. But I don't know you, so maybe you face a higher-than-average level of threat, in which case, yes, a sufficiently long password/passphrase that you memorise is probably the best option for your mobile device.

Well, functionally that would be the same as if you just don't grant the permission to any other app than microG. Unless you don't trust that Android's permissions work properly, but then I think you have much bigger problems.

This doesn't make sense to me. You already have other permissions (draw on top of other apps, full filesystem access, etc) that could be catastrophic to grant to malicious apps. If you don't trust yourself not to grant them, or you don't trust the Android permissions system itself to be implemented correctly, it's already game over.

(Edit to add: I agree with everything in your second paragraph.)