Différences entre versions de « Ownyourdata-fr »
De Mi caja de notas
Ligne 20 : | Ligne 20 : | ||
* [[IndieMark-fr|IndieMark]] | * [[IndieMark-fr|IndieMark]] | ||
__TOC__ | __TOC__ | ||
− | === | + | === Par Silo === |
− | |||
− | + | Engagez-vous à posséder vos données en utilisant votre site, au lieu d'un silo, pour chaque silo que vous utilisez actuellement. | |
+ | Chaque silo que vous arrêtez d'utiliser directement ([[POSSE]]r est ok), et l'utilisation à la place de votre propre site, constitue un pas en avant dans la possession de vos données. | ||
=== Per Post Type === | === Per Post Type === |
Version du 27 octobre 2018 à 07:05
Cette page a démarré sur iwc:ownyourdata
✊ Cet article est une ébauche. Vous pouvez m'aider à l'améliorer et le compléter. Merci.
own your data est un principe IndieWeb avec deux composants-clés : 1) vos données vivent en priorité sur votre propre domaine, et 2) vous maintenez un accès utilisable à ces données au fil du temps.
Pourquoi
First, using your own domain gives you control over where people find and interact with you online. When you migrate to a new hosting provider or CMS, if your site stays on the same domain, everyone will still find you, regardless of whether they follow your site in a reader, land directly on your permalinks from other sites or search engines, or even type your domain directly into a browser.
Second, they say that change is the only constant, and web sites are no exception. Whether you stick with a host or CMS for a year, a decade, or a century, you're likely to change something eventually. When you do, you'll need usable access to all of your existing data. This includes export and import, data formats and standards, tools, protocols, permissions, rate limits, and more.
Also see why.
Comment
Les Fondamentaux
See and follow these in order:
Par Silo
Engagez-vous à posséder vos données en utilisant votre site, au lieu d'un silo, pour chaque silo que vous utilisez actuellement. Chaque silo que vous arrêtez d'utiliser directement (POSSEr est ok), et l'utilisation à la place de votre propre site, constitue un pas en avant dans la possession de vos données.
Per Post Type
Commit to owning each kind of post you publish, by using only your site to publish particular kinds of posts (again, POSSE is ok).
Each kind of post you stop posting directly to any/all silo(s), and use always use your own site to create instead, is a step forward in owning your data.
Per Post Type Per Silo
A more incremental but still significant step is stop posting a particular type of post to a particular silo, and always use your own site to publish that type of post instead of that silo.
IndieWeb Examples
Add yourself here if you:
- have an indieweb site, and
- are using it exclusively to post either
and note what date you started owning your data of what kind(s) of posts, or instead of which silo(s).
For the purpose of this page, please succinctly list, only
- specific silo(s) you have replaced usage of with your own site. E.g.: I use my own site instead of Twitter (notes, replies, favorites)
- post type(s) you use your own site for instead of / before any silo posts. E.g.: I post notes on my own site instead of Twitter, Facebook, Tumblr, etc.
- post type(s) instead of specific silo - what post type you use your own site for instead of / before a specific silo. E.g.: I post notes & replies on my own site instead of Twitter.
Optional details, for each of the above post types / or "instead of silos", optionally note which projects or tools help you do so.
Examples of what doesn't count:
- You post some notes on your own site, and some notes directly to Twitter.
- Why: All or nothing. Either you've committed and are following through with posting all your content of a specific kind to your own site, or you don't yet "own your data" of that type.
Examples of what belongs on your user page instead:
- owned other things besides post types / instead of silos (sites, domain names, project installs)
- what other sites you post to
Examples of what doesn't disqualify you:
- A small number of test posts on any given silo of any given content type, especially if you're doing it as research for how to best POSSE to that silo, especially if you document the results of your research here on the wiki. Though for research purposes, you really should create one or more separate test accounts on silos.
gRegor Morrill
gRegor Morrill has:
Tantek
Tantek Çelik has:
- owned his articles since 2002-08-08.
- owned his notes since 2010-01-01.
- owned his events since 2017-06-26.
- instead of Twitter, posted on his own site:
- notes since 2010-01-01, POSSE to Twitter since 2010-01-26
- @-replies since 2013-05-12, POSSEd to Twitter (same day).
- favorites as likes, since 2014-12-31, using Bridgy Publish to POSSE likes of tweets to favoriting those tweets on Twitter.
Notes:
- not yet ownyourreplies. I can't say I yet I follow "ownyourdata" for ALL my replies, as I have posted replies directly to posts on Facebook, whereas I should be posting even those replies on my own site first, and then POSSEing them to Facebook, perhaps via Bridgy publish. Thus I've scoped my "ownyourdata" of replies to only being a replacement for my use of Twitter to post replies.
- not yet ownyourlikes. I also can't yet say I follow "ownyourdata" for ALL my likes, as I still like photos directly on Instagram, and posts on Facebook.
- not yet ownyourRSVPs. While I have owned my public RSVPs (especially "going") since 2017-01-01, I still RSVP to private events on Facebook. I’m not sure how to avoid this short of giving up on private FB events.
Snarfed
Modèle:Snarfed has:
- owned his articles and notes [2] since 2003-06-29 [3]
- owned his photos [4] since 2003-03-06 [5]
- owned his replies/comments [6] since 2013-10-02 [7]
- owned his likes/favorites [8] since 2014-02-02 [9]
- owned his reposts [10] since 2014-03-13 [11]
- owned his events [12] and rsvps [13] since 2014-01-15 [14]
- instead of Twitter:
- posted notes and photos on his own site always, replies [15] since 2013-10-02 , favorites [16] since 2014-02-02, retweets [17] since 2014-03-13
- POSSEd via Bridgy Publish, backfed via Bridgy
- read his Twitter stream via twitter-atom and responded via web bookmarklets and Android flow instead of Twitter's own web UI and app
- instead of Facebook:
- posted articles, notes, and photos on his own site always, comments [18] since 2013-10-02, likes [19] since 2014-02-02
- POSSEd via Bridgy Publish, backfed via Bridgy
- PESOS backfilled articles and notes between 2009-10-15 [20] and 2012-10-28 [21] with freedom.io
- read his Facebook news feed via facebook-atom and responded via web bookmarklets and Android flow instead of Facebook's own web UI and app
- instead of Instagram, posted:
- posted photos on his own site always [22], POSSEd manually, backfed via Bridgy
- read his Instagram stream via instagram-atom instead of the Instagram app
- instead of Google+, posted on his own site:
- articles, notes, and photos always, POSSEd manually, backfed via Bridgy
Bear
Modèle:Bear has
- owned his articles since 2003-12-18. [23].
- owned his own replies since May of 2014.
- owned his own replies to others since November of 2014 but until I add in-reply-to' markup I cannot call them comments.
Aaron Parecki
- owned his articles since 2006-04-14
- owned his bookmarks since 2010-12-17[24]
- owned his notes and replies, and POSSE to Twitter since 2012-08-19[25]. [26]twitter copy
- owned his photos since 2014-03-08[27] (launched at IndieWebCamp SF 2014) and occassionally manually POSSEs to Twitter since 2014-05-06[28]on Twitter
- owned his biking, running, and driving since 2014-07-30[29]
- owned his videos since 2014-09-10[30]
- owned his food & drink posts since 2014-10-17[31]
- owned his cat since 2014-11-01[32]
- owned his reposts since 2014-11-02[33]
- owned his likes since 2014-12-26[34] (launched as part of the 2015-01-01 commitments)
Kartik
Modèle:Kartik has:
- owned his articles since 2013-06-01. Invictus.
- owned his notes since 2014-03-08. [35].
- instead of Twitter, posted on his own site:
- notes and POSSE to Twitter since 2014-03-20. original twitter copy
- photos and POSSE to Twitter since 2014-07-27. original
- instead of Google+, posted on his own site:
- notes and manual POSSE to Google+ since ??
- instead of on others blogs not supporting webmentions, posted on his own site:
- replies and manual POSSE replies to others blogs not supporting webmentions since 2014-08-28. original
Ben Werdmuller
Ben Werdmüller has since 2013-07-11 using Known:
- instead of Twitter, posted to his own site:
- notes and POSSE to Twitter
- instead of Facebook, posted
- notes and POSSE to Facebook
- instead of LinkedIn, posted
- notes and POSSE to LinkedIn
- instead of Flickr, posted
- photos and POSSE to Flickr
The Dod
Modèle:Thedod has:
- instead of Twitter, posted to his own site:
- notes, replies, repost, favorites and POSSE to Twitter using his RedWind install since November 2014.
- Uses a bookmarklet to reply/reshare/fav stuff (including tweets).
- Uses Bridgy to backfeed Twitter interactions as webmentions
Sebastiaan Andeweg
Modèle:Sebsel has:
- instead of Instagram, posted to his own site:
- photos and POSSE to Instagram (since 2016-11-22, with import of all earlier photos)
... add yourself ...
Hashtag
#ownyourdata is a rallying cry hashtag for aggregating content across indie web sites and 3rd-party silos about "owning your data", "owning your own data" etc.
- Tagboard: #ownyourdata - hashtag aggregator across Twitter, Instagram, Google+.
- Google News Search: ownyourdata
- ...
#ownyourdata posts tend to be a a subset of Posts about the IndieWeb.
Voir aussi
- Posts about the IndieWeb.
- Principes
- http://www.obsoletemedia.org/
- 2018-05-17 Google’s Selfish Ledger is an unsettling vision of Silicon Valley social engineering
Of course, the concept is premised on Google having access to a huge amount of user data and decisions. Privacy concerns or potential negative externalities are never mentioned in the video. The ledger’s demand for ever more data might be the most unnerving aspect of the presentation.
- https://www.lvm.fi/documents/20181/859937/MyData-nordic-model/
- https://mydatafi.wordpress.com/