Skip to content
This repository has been archived by the owner on Jan 10, 2021. It is now read-only.
hugoroy edited this page Oct 4, 2012 · 12 revisions

Convert mailing list discussions to put on the website

Here’s how you can help!

JSONify list threads

When you find something relevant in the mailing list that should become a data point:

  1. Create a file in /points that matches the mailing list thread (Please read the documentation about the JSON format for points in /points/README.md)
  2. Run 'node buildIndexes.js' inside the repository directory
  3. Make sure the service(s) you reference in the points file exist as a json file in /services, and the topic you assign should exist in /topics

(If you can't get the script to run, then just only create the points files, commit and push, and we’ll debug it afterwards.)

Progress

Please put your name next to the ML thread you are JSONifying, then we can work through the list together. when done, strike it through, with a note 'done' behind it.

  • (information) Flickr users are subject to Yahoo!'s PP and ToS (1)
  • (bad) Flickr: pro accounts cannot be canceled (1)
  • (good) Flickr gives you a choice: with whom you share your photos (1)
  • Flickr ToS & PP (3)
  • Comparison between GitHub and Steam (2)
  • tosdr.co-ment.com is "Not Active" (1) [not a data point] pantsburgh
  • Standardized list of minimum ToS data point topics (2) [not a data point] pantsburgh
  • Steam - users defend and indemnify Valve (4)
  • (bad) Wordpress.com ToS can change without notice, viewing a new ...
  • (copyright license) You License Freely Your Contributions (copyleft) (1)
  • (readability, good) Wikipedia ToU are translated in 20 languages (1)
  • Wikipedia's Terms of Use were drafted collaboratively by the community (1)
  • Github can suspend your service and delete your data any time for any reason (3) (no subject) Brandon Howell
  • ~~timestamps and versions (2) ~~ [not a data point] pantsburgh
  • Re: [bad] delicious new terms 2. no right to leave the service (3)
  • Steam Subscriber Agreement & Privacy Policy (5) - done
  • BitBucket TOS (1)
  • (bad) Only VIP accounts will receive notice before potential termination (1)
  • Wikipedia ToU & PP (1)
  • Netflix ToU & PP (1)
  • ~~Please do assess Wikipedia (3) ~~ [not a data point] pantsburgh
  • [Good] Craigslist drops exclusive license to your posts
  • [bad] Google Chrome now forces you to use Chrome Web Store as only choice (1)
  • GitHub's definition of cookies is… interesting (4)
  • ~~Idea - in addition to classification letters (6) ~~ [not a data point] pantsburgh
  • [Bad] Goodreads owns most of your content in perpetuity (2)
  • Congratulations (8) [not a data point] pantsburgh
  • eff tosback2 (1)
  • Salesforce/Chatter (1)
  • EFF publishes report about companies practices regarding handing over ... [not a data point] pantsburgh
  • Crashplan Rating? (3)
  • http://tos-dr.info/ doesn't work in Internet Explorer apparently? (3) [not a data point] pantsburgh
  • [Good] The user can leave Xing without cause (2)
  • Gravatar: Takes copyright, can transfer copyright, can sublicense (1)
  • [Bad] Facebook give personal details to 3rd Party by default (1)
  • [Bad] You will not provide any false personal information on Facebook (1)
  • Chrome Browser Plugin (2) [not a data point] pantsburgh
  • Developers specific rating for Terms of Services and policy : focus on APIs (1)
  • Twitpic choice of law clause and choice of jurisdiction: Delaware (2)
  • Legal eagle. (1) [not a data point] pantsburgh
  • Idea - Privacy Watch website (tosdr@googlegroups.com) (1)
  • [Good] Xing value the data privacy of their users
  • [Bad] The user has to use at Xing his/her real name (1)
  • Google Transparency Report (2)
  • Youluh, focusing on EULAs (10)
  • Roadmap, your help and feedback is needed! (5)
  • Twitter publishes 'Transparency Report' on government requests and DMCA notices (1)
  • How GitHub deals with your data and legal requests or obligation (2)
  • GitHub provides detailed information about their security policy and practices
  • Github, in case of business transfer (1)
  • Github explains why hte information is used and collected (1)
  • Github can change the terms without notice (2)
  • GitHub choice of law (no jurisdiction) (1)
  • GitHub doesn't ask for a copyright license (1)
  • GitHub wants you to defend and indemnify them (1)
  • no pseudos allowed on GitHub (1)
  • [good enough?] Twitter notifies users by a tweet or by email when ToS are changed (3)
  • soundcloud privacy: use and share of personal information (1)
  • soundcloud privacy: information collected automatically (1)
  • soundcloud privacy: pseudos allowed (1)
  • soundcloud termination (1)
  • soundcloud jurisdication and applicable law (1)
  • soundcloud indemnification (1)
  • soundcloud copyright license is one of best i have seen so far (1)
  • soundcloud changes in terms: 6 weeks ultimatum (1)
  • readability is good on soundcloud terms of service (1)
  • soundcloud community guidelines (1)
  • Coming To Terms (1)
  • 500px Store: moral rights waiver (on photographs) (2)
  • [feedback wanted] 500px: waiver of legal action (2)
  • 500px copyright license scope (1)
  • 500px isn't open to anyone (1)
  • [good] 500px pseudonyms are allowed (1)
  • [mediocre] 500px terms can change at any time (1)
  • [good] Google notice of changes in the ToS (1)
  • Google helps you stay secure and control some of your information (1)
  • Targeted ad via facebook's cookies [similar to Google DoubleClick Ad Exchange] (1)
  • Millions Will Flow to Privacy Groups Supporting Weak Facebook Settlement (1)
  • Facebook doesn't allow pseudonyms and asks users to point them out (3)
  • [good] Twitter does not requrie cookies (7)
  • an article about google ToS & Privacy Policy on BBC (1)
  • an opportunity to integrate tos-dr in the browser (1)
  • [good] reddit.com (2)
  • Fwd: [Freedombox-discuss] UUID tracked (2)
  • [Good] Facebook educate their users about how to be safe (7)
  • ToS; Didn't Read & Tosback 2 [need more legal participation from US]
  • ~~Similar-ish project: tl;dr legal (1) ~~ [not a data point] pantsburgh
  • Twitpic privacy policy (1)
  • "Deleted Images" are not really deleted (1)
  • Question: can Twitpic reduce the prescription of legal action? (1)
  • More madness from Twitpic: indemnification from claims related to user content (1)
  • [alert] Twitpic takes credit for user pictures (1)
  • Fwd: Lightning Talks (1)
  • Adding CC-BY-SA license information to .json files (1) [not a data point] pantsburgh
  • Fwd: US-Canada statement of privacy principles (1) [not a data point] pantsburgh
  • tossos (3)
  • personal data and business transfers twitter, google, delicious and al. (3)
  • Twitpic copyright license also granted to their "partners" (1)
  • Google: changes in ToS (1)
  • Google: choice of law and choice of jurisdiction clause (1)
  • Google: copyright scope of the general ToS (1)
  • a good article with real life examples with broad copyright licenses from Twitpic, twitter (1)
  • should we have a twitter button on the website? (3)
  • AT&T, Verizon, Sprint, T-Mobile: sharing your location data, but not with you (1)
  • [Good] list of websites that don't store your primary nor your secondary data (4)
  • is using webserver logs ok? (1)
  • let's crowd-read (in German) the mitfahrgelegenheit ToS update (1)
  • Delicious class D (2)
  • Gravatar: no right to leave the service?
  • Instagram copyright license: no transfer, no sublicense (1)
  • Facebook's tracking "Like" buttons, to become even more pervasive with OpenGraph API
  • Sonic.net (ISP) deletes logs after 2 weeks (1)
  • Twitter's practice to notify changes in ToS [Fwd: [IFOSSLR Ed-Com] Updates to ...
  • Re: [Good] Facebook educate their users about how to be safe, [Bad] doesn’t use ...
  • Delicious previous terms (1)
  • [good] SeenThis allows you to export your data in XML (6)
  • [Good] OwnCube (1)
  • [Good] Newsblur allows import & export, is open source (1)
  • [bad] delicious new terms 4. cookies will be used for targeted ad! (4)
  • [bad] delicious new terms 5. third party services get access to personal information (2)
  • [bad] delicious new terms 6. Personal information will be sold in case of ...
  • [bad] delicious new terms 3. your right to use the service only for personal ...
  • [bad] delicious new terms 2. no right to leave the service (1)
  • [bad] delicious new terms 1. copyright license (1)
  • Fwd: US Congressmen send letter on Do Not Track to W3C (2)
  • [good] Widget Data is kept a maximum of 10 days (and opt-out) (2)
  • SeenThis: class A ? (2)
  • [Bad] Facebook tracks non-users, creates shadow-profiles
  • What's the right balance in a copyright license for publishing over "social networks"?* [Bad] Google keeps your Searches forever (2)
  • [Bad] Facebook automatically shares your information (2)
  • [bad] Flattr could do better to handle age limit (8)
  • [good] List of services providing archives of their ToS (3)
  • Mozilla's Privacy Icons (9)
  • Diaspora Pod Ratings (1)
  • Fwd: criteria to (not) add (3)
  • Re: [unhosted] first progress on http://tos-dr.info/ (1)
  • [bad] Your copyright license to Twitter does not end when you deactive your accont (6)
  • [bad] Twitter copyright license: very broad scope and 3rd parties (5)
  • Article: What Facebook knows (data mining, etc;) (1)
  • [Bad] Google - wikipedia page summarizing criticism of Google (2)
  • [Good] DuckDuckGo doesn't track you (2)
  • [Good] identi.ca and joindiaspora.com have a federated architecture (1)
  • A clause in the TOS may contradict law in a country and therefore be void. (3)
  • Facebook "help" page about the tracking "Like" buttons (aka "social plugins") (1)
  • [Good] Facebook sollicited public feedback before launching new ToS
  • [Bad] Facebook UI induces oversharing (5)
  • [Good] 500px terms of service (2)
  • [Good] Flattr fights hard to make their ToS consumer-rights friendly (2)
  • [Good] Wikipedia doesn't use cookies
Clone this wiki locally