That's much better, but it is still a free VPN that bypasses network security measures. I can even imagine a threat actor deploying firefox for their command and control infra.
It isn't recording surreptitiously. The data was collected as part of an optional feature which is a very intentional process where you start a scan and then move around the object being scanned to get data from multiple angles, and then click to upload the data to Niantic. The uploading is called out specifically as a separate step (at least early on it was common for uploads to fail, so it had the option to save the scan to upload later when you had better signal). There is nothing secret about the fact that Niantic is collecting this data.
The lack of transparency is about how Niantic is using the data, selling it to third parties for purposes unrelated to the game. And I agree with the parent that this is a fair trade for a free game, especially since that part is optional, but more transparency would be better.
It is not at all clear that the mapping is for purposes other than the AR features in the game itself though. In fact Niantic advertised the scanning field research as helping them make richer experience at PokeStops (which they did).
Niantic was much more upfront about this with Ingress, so people who know the company's history will likely guess that Pokemon Go is serving the same purpose, but for someone coming into the game without that background, there is nothing in the game itself that indicates that data is being collected for other commercial purpose.
Right, but it sounds like the data collection itself was pretty well communicated. So nobody should be surprised it gets used for some other (legal) purpose than was originally intended.
Yeah. My problem with the em-dash is that it has too many uses (parenthetical statements, independent clause, verbal pauses) and as a reader you don't always know which one is intended until after you've read a bit past the em-dash, and might need to go back and reread the sentence once you figure out how it is supposed to be parsed. Use of semicolon and parenthesis are much clearer in contrast. The comma has the same problem to some extent. I would be happy if we could settle on consistently replacing some specific uses of comma with em-dash to make writing less ambiguous, but in the real world I find it clearer to just avoid the em-dash all around.
Neat. Even knowing about niche optimization I would have guessed that you could fit 7 Options - one bit for each. But the developers were smart enough to take advantage of the fact that you can't have a Some nested below a None, so you only need to represent how many Somes there are before you reach None (or the data), allowing 254 possibilities.
I doubt they were thinking about Option<bool> when making niches work like this.
Option<NonZeroU32> seems like a much more reasonable to justify this with. Also, enums can easily have invalid bit patterns that are unused without there being any specific bit that is always available. All you need is a single variant of the enum to have a free bit, and you have a niche to shove None into.
They intentionally made the menu longer to look worse by selecting some text first. So it is showing four sets of contextual actions: For the Link, the Image, the Selection, and the Page.
Also a few of the menu items are new since the latest ESR (the AI stuff in particular), so you won't see them if you are running v140.
That statement by itself wouldn't warrant an article, and it would be difficult to include a statement like that in a larger article about the event, without implying more than that.
reply