Hi Brad: The software is distributed under the terms of the GPL which means that you are free to change it according to your wishes and needs.
Thus, if you want to make OSM usable again, just add a decent RFC
2616-compliant user-agent header, e.g. by running (on Linux or OS X)
<snip>
for n in *.cpp ; do sed -e 's/\(QNetworkRequest[
\t]*\)\([a-z]*\);/\1\2;\n\t\2.setRawHeader("User-Agent",
"QLandkarteGT\/1.7");/' -i $n; done
</snip>
in the src folder, and re-build the application.
With this fix, I am now able to use OSM as TMS map through e.g.
<https://c.tile.openstreetmap.org/%1/%2/%3.png>.
I *strongly* recommend to use the encrypted form of the service, as we know [1]
that the combination of geo data and IP address is being intercepted regularly.
Although these documents focus on Google only, I think we should persume that
OSM accesses are also under surveillance. Thanks to the efforts of the OSM
people, this service offers strong encryption with Perfect Forward Secrecy
(PFS).
Hth,
Albrecht.
[1]
<http://www.theguardian.com/world/2014/jan/27/nsa-gchq-smartphone-app-angry-birds-personal-data>
Am 21.02.14 15:54 schrieb(en) brad:
I personally do not see the issue. What OSM is requesting is very reasonable. I appreciate the hard word you've done on this application, but forcing the occasional user like me to figure this out and add this in is not a good idea in my opinion.
pgpdxD7fTfmoy.pgp
Description: PGP signature
------------------------------------------------------------------------------ Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk
_______________________________________________ Qlandkartegt-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qlandkartegt-users
