W3C home > Mailing lists > Public > whatwg@whatwg.org > October 2014

Re: [whatwg] (no subject)

From: Nils Dagsson Moskopp <nils@dieweltistgarnichtso.net>
Date: Mon, 13 Oct 2014 03:26:26 +0200
To: Silvia Pfeiffer <silviapfeiffer1@gmail.com>, javascript@riseup.net
Message-ID: <87y4skahfh.fsf@dieweltistgarnichtso.net>
Cc: WHAT Working Group <whatwg@lists.whatwg.org>
Silvia Pfeiffer <silviapfeiffer1@gmail.com> writes:

> On Sun, Sep 14, 2014 at 12:17 PM,  <javascript@riseup.net> wrote:
>>
>>
>> On 9/12/14, Silvia Pfeiffer <silviapfeiffer1@gmail.com> wrote:
>>>
>>> What I'd you're a long way away from any medical help?
>>>
>>
>> What?
>
> s/I'd/if/
>
> (sorry - mobile keyboard)
>
>
>>> In my mind this is part of the larger drive of the web of things (IoT
>>> applied to the web) and needs device APIs. This might not be the right
>>> group to discuss it in though.
>>>
>>
>> Where is the best place to define the APIs for devices to track, monitor,
>> and surveil us?
>>
>> Perhaps the W3C is the best place. It is funded by the very corporations
>> that are making such monitoring devices and with developer relations experts
>> to tell you how. These corporations are backed by  philanthropists, such as
>> William Gates III, whose opposes climate change, whistleblowers, and
>> overpopulation.
>>
>> Sure, Microsoft might've backdoored stuff for the NSA for the past 10 years,
>> and Apple might share your info to the NSA (they'll get it anyway). And
>> Google and the CIA might want info for MindMeld (TM) or Recorded Future,
>> which they openly fund (links below).
>>
>> He who pays the piper calls the tune.
>>
>> You don't have anything to hide, right?
>>
>> Or maybe the question of "how" or where to "best to engineer" this or that
>> new gadget is best answered by first asking how to prevent such engineering
>> from being used by a top-down, "efficient" system.
>>
>> The system is working. That is the problem.
>>
>>
>> http://www.rawstory.com/rs/2014/09/10/cant-wait-for-the-apple-watch-beware-your-fitness-data-may-be-sold-or-used-against-you/
>>
>> http://rt.com/usa/microsoft-nsa-snowden-leak-971/
>>
>> Google & CIA funded MindMeld
>> https://en.wikipedia.org/wiki/Recorded_Future
>>
>> CIA funded MindMeld
>> http://techcrunch.com/2014/07/17/expect-labs-lands-in-q-tel-investment-will-help-u-s-intelligence-integrate-its-mindmeld-technology/
>
>
> If you don't want to give your data to anyone, don't. Nobody is
> forcing you to share your medical data over the Internet.

Nobody is forcing you to share your location data over the Internet as
well – but somehow, flashlight apps for Android seem to do it at times:
<http://www.techrepublic.com/blog/it-security/why-does-an-android-flashlight-app-need-gps-permission/>

If something is possible, users can be tricked into allowing it – or
even pressured. Just look at “enable JavaScript and cookies or a web
site that *could* work without both of these will refuse to do that.”

> I don't see that stopping the world moving forward though. Given that
> it is happening anyway, I'd rather go with an open API than
> proprietary ones where we don't know what is happening.

I question the assumption that an open standard for something ethically
questionable is always desirable. An open standard for voting computers
could, for example, lead to more use of voting computers and thus help
those who wish commit large scale electoral fraud.

I must admit that I am not nearly knowledgeable enough regarding ethical
and legal issues surrounding disclosure of medical data. I just think
that “shoot first, ask questions later” does not fit in there well.

-- 
Nils Dagsson Moskopp // erlehmann
<http://dieweltistgarnichtso.net>
Received on Monday, 13 October 2014 01:27:01 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 17:00:24 UTC