

These pubs don’t just open the kimonos of their readers. Irony Alert: the same is true for the Times, along with every other publication that lives off adtech: tracking-based advertising. These are Facebook’s true customers, whom it works hard to please.” Among other things (all correct), Zeynep explains that “Facebook makes money, in other words, by profiling us and then selling our attention to advertisers, political actors and others. I get the feeling that's not going to happen, thus the "use Mapsource" declaration.Let’s start with Facebook’s Surveillance Machine, by Zeynep Tufekci in last Monday’s New York Times. Garmin has developed Basecamp down a path that won't support the Zumo 66x line unless they get back to updating the 66x firmware. :) I don't get the sense there is much momentum to support any of the Zumos other than the recently released model. Then again, I'm not sure anything will be resolved even if a lot of people complain. If nobody complains, or if the issues are not wide spread I get the feeling nothing will get fixed. They are just keeping the details of these issues to themselves. At least they are now telling it like it is, that they know there are issues between the Zum0 66x models and Basecamp. People report issues with the Zumo 66x and Basecamp, Garmin asks for example files, people send them in, Garmin sits on it for a while, then nothing. The spontaneous recalc issue has been around about a year. This has been going on for a while and is not just a recent thing. It would seem that Garmin is leaving Zumo owners out to dry-at least for the time being.
#GARMIN BASECAMP 4.4.2 FULL#
So that I, and I imagine other owners of these devices, can understand fully the nature and extent of the issues and incompatibilities, please could Garmin issue a clear statement setting out the full (technical) details of them, whether it is intended to remedy them, and in what timescale.Īnd if Garmin won't, please could it explain why not.
#GARMIN BASECAMP 4.4.2 UPGRADE#
If it does apply to the 590 (and given how recently that model was introduced) why does the advertising and sales material for the 590 not make it clear that Mapsource is the preferred software package? If it had, it would undoubtedly have affected my decision whether to upgrade from a 660. Which Zumo models does the statement apply to? All of them, or (as appeared to be the original position) just the 660 and earlier? In particular (and with no lack of concern intended or implied for owners of lower spec models) does it apply to the Zumo 590?

original lack of postcode search - which still doesn't work properly) and the failure to carry out any development on Mapsource for a number of years, this unqualified statement that "Mapsource as of now continues to be the application with the Zumo support" is truly startling. After all the pressure to move from Mapsource to BC despite its shorcomings (e.g. I have become increasingly depressed as I have followed this thread. Mapsource as of now continues to be the application with the Zumo support. There are some route differences between what BaseCamp and the Zumo's produce.
