of our APIs allow the submission of content. Google does not acquire any ownership of any intellectual property rights in the content that you submit to our APIs through your API Client, except as expressly provided in the Terms. For the sole purpose of enabling Google to provide, secure, and improve the APIs (and the related service(s)) and only in accordance with the applicable Google privacy policies, you give Google a perpetual, irrevocable, worldwide, sublicensable, royalty-free, and non-exclusive license to Use content submitted, posted, or displayed to or from the APIs through your API Client. ”Use” means use, host, store, modify, communicate, and publish. Before you submit content to our APIs through your API Client, you will ensure that you have the necessary rights (including the necessary rights from your end users) to grant us the license.
of our APIs allow the submission of content. Google does not acquire any ownership of any intellectual property rights in the content that you submit to our APIs through your API Client, except as expressly provided in the Terms. For the sole purpose of enabling Google to provide, secure, and improve the APIs (and the related service(s)) and only in accordance with the applicable Google privacy policies, you give Google a perpetual, irrevocable, worldwide, sublicensable, royalty-free, and non-exclusive license to Use content submitted, posted, or displayed to or from the APIs through your API Client. ”Use” means use, host, store, modify, communicate, and publish. Before you submit content to our APIs through your API Client, you will ensure that you have the necessary rights (including the necessary rights from your end users) to grant us the license.
post photos, exercise regimens, food logs, recipes, comments, and other content (“Your Content”) to the Fitbit Service. You retain all rights to Your Content that you post to the Fitbit Service. By making Your Content available on or through the Fitbit Service you grant to Fitbit a non- exclusive, transferable, sublicensable, worldwide, royalty-free license to use, copy, modify, publicly display, publicly perform and distribute Your Content only in connection with operating and providing the Fitbit Service. 30
WORTH), LOCATION CAN BE INFERRED, POTENTIALLY LEADING TO PRIVACY DISCLOSURES Liccardi et al, 2016. I Know Where You Live: Inferring Details of People's Lives by Visualizing Publicly Shared Location Data (CHI '16).
LIST TO EXTRACT THE HEALTH RECORD OF THE GOVERNOR OF MASSACHUSETTS Sweeney, L. k-anonymity: a model for protecting privacy. Int. J. Uncertainty Fuzziness and Knowledge-Based Systems 10, 557–570 (2002) 33
USED TO ESTIMATE SOMEONE’S AVERAGE INCOME […], AVERAGE HOUSING COST, DEBT, […] POLITICAL VIEWS ETC. Liccardi et al, 2016. I Know Where You Live: Inferring Details of People's Lives by Visualizing Publicly Shared Location Data (CHI '16). 34
‘APPS’ FIT INTO A PRIVACY FRAMEWORK NOT LIMITED TO HIPPA ▸ Surveillance (unauthorised collection) ▸ Identification ▸ Insecurity (lack of encryption) ▸ Disclosure (of sensitive data to third parties) ▸ Aggregation (consumer profiles) 36
programming knowledge at the level of CS 50 (or above), and statistics knowledge at the level of Stat 100 (or above). ▸ Stats 110: sample spaces, naive definition of probability, counting, sampling, random variables, CDFs, PMFs, discrete vs. continuous, Hypergeometric, Poisson distribution, Poisson approximation, standard Normal, Normal normalizing constant, Markov chains, transition matrix, stationary distribution, Chi-Square, Student-t, Multivariate Normal 59
OF SOFTWARE SYSTEMS, WHO ARE ACTING AS NON-PROFESSIONAL SOFTWARE DEVELOPERS, AT SOME POINT TO CREATE, MODIFY, OR EXTEND A SOFTWARE ARTIFACT. Lieberman et al. 2006
OF SOFTWARE SYSTEMS, WHO ARE ACTING AS NON-PROFESSIONAL SOFTWARE DEVELOPERS, AT SOME POINT TO CREATE, MODIFY, OR EXTEND A SOFTWARE ARTIFACT. Lieberman et al. 2006
to a file and send it to a server ‣ Do analysis directly on the phone; necessary if you need to do real time: see Jan Machacek's Exercise Analysis talk. ‣ You probably want to use MQTT
a notification from Node-RED with AeroGear Push Server ‣ Get it on the phone with App Inventor Work In Progress! Node-RED node for Notifications: https://github.com/CLDTio/node-red-contrib-aerogear-notifications App Inventor Component for AeroGear: https://github.com/josmas/app-inventor/tree/aerogear
there are plenty, and now you know better so you can make an informed decision if you want to use it or not! ▸ iSense (read T&Cs first) ▸ Your own backend with Parse, MIT Solid, or any other solution you like (including rolling your own) 93
josmas
monochromegane
trafficbrain
langstat
.png){kind=avatar}
satai
eumesy
sgk
sansan_randd
asonas
cocomoff
yuukit
kuri8ive
kneath
jmmastey
jonyablonski
colly
thoeni
lara
notwaldorf
samanthasiow
bkeepers
rasmusluckow
eileencodes
