Silo-fr

Cet article est une débauche. Vous pouvez m’aider à l'améliorer.

Cette page a démarré sur iwc:silo et migrera après traduction sur iwc:silo-fr

Un silo, ou silo d'hébergement de contenu web, dans le contexte de l'IndieWeb, est un site web centralisé (comme la plupart des médias sociaux) généralement détenu par une société à but lucratif qui revendique le contenu contribué et restreint en quelque sorte l'accès (il a des murs).

Les silos sont caractérisés par ce qui suit :

• ils vous obligent à créer un compte spécifique à ce site pour l'utiliser (silo d'identité)
• ils vous autorisent à interagir sur le site uniquement avec d'autres personnes ayant des comptes sur le site (contacts de silo / réseau social)
• ils vous autorisent à poster certains types de contenus (texte, hypertexte, images, vidéos)
• et généralement un ou plusieurs des éléments suivants :
  • un mur d’accès qui empêche l’indexation (au moins une partie) du contenu que vous contribuez
  • des conditions générales d'utilisation restrictives (CGU)
  • revendication d'un droit de propriété ou d'une licence sur tout contenu que vous créez dans le silo
  • restriction de votre capacité à importer/exporter votre contenu, ou du contenu relatif à votre contenu (par exemple les commentaires et mots-clés.)

Mettez ça en perspective avec les : communs.

Perspectives

What are the silos? Control. The silos are computer-generated dream worlds built to keep us under control in order to change a human being into this.
[holds up chart showing clicks on ad units]
(with apologies to [1])

[2]

Historique

Article principal : History

Pour un bref historique de la montée et de la chute de divers silos, voir la page Historique pour les années / dates de lancement, d’acquisition, de décès et de zombification. Voir cimetière des sites pour les décès à venir et passés des silos.

Silos Populaires

http://geekandpoke.typepad.com/.a/6a00d8341d3df553ef0147e0e1aec2970b-300wi?x=.jpg

Ces silos sont à la fois populaires, et utilisés par un certain nombre des membres de la communauté indiewebcamp (souvent via POSSE) pour rester en contact avec leurs amis.

• Facebook
• Flickr
• Google+
• Instagram
• Medium
• Pinterest
• Tumblr
• Twitter
• WordPress.com - parmi tous ces silos, WordPress.com dispose du meilleur support import/export, très petits murs pour un jardin clos.
• ...

Si vous avez des amis actifs sur un silo populaire, sentez-vous à l'aise pour les ajouter à cette liste.

Silos Spécialisés

• Netflix - Movie ratings and reviews
• Nike+ - tracks some exercise information
• Strava - GPS sport tracking
• Geocaching.com - geocaching activity tracking
• ...

Add any silo to this list that you're an active user of and especially if you can document how to export data from it.

Silo Flexibility

A few silos have given users tremendous flexibility in the look and feel of their experience and the content they post.

Currently:

• Blogger - quite a bit of control via templates
• Tumblr - also lots of control via templates
• WordPress.com - some choice of free templates, and more choices as a paid option

Historically (but no longer)

• MySpace (~2002-2009?) - so much control over the HTML and CSS of your profile page that many compared it to GeoCities, and not in a flattering way.

Innovations des Silos

Les silos ont innové l'UX depuis 2003 bien plus que les "communautés" de blogueurs/RSS/Atom.

Voici quelques exemples d'innovations UX que les silos ont soit créé, popularisé ou raffiné pour être bien plus utilisable, classés par ordre d'apparition.

• favoriss - Flickr (2004)
• Integrated reading/creating UI - LiveJournal, Delicious (2004), Tumblr, Twitter (2006), Facebook (2006? when did Facebook launch their Newsfeed?)
• checkins - Dodgeball (2005), Foursquare (2009?), copied by Facebook (2010?)
• scrobbles - Last.fm (2000-2005? what year exactly?)
• block - Flickr (2005-07-27 per [3], before that they had an ignore feature (superseded by block) which sounds like a harsher form of mute)
• likes - introduced by FriendFeed 2007-10-03[4], then copied soon after by Facebook which quickly popularized them.
• reply-context - Twitter (20??-??-??). It was a small but important incremental step to go from reply posts on their own pages (see "User Innovation Inside Silos" below) to displaying the context of what those reply posts (tweets) were in reply to.
  • recursive reply-contexts - Twitter. Another incremental if obvious step, Twitter started displaying the reply contexts of reply contexts themselves, all the way on up to an original tweet.
    • Aaron Swartz invented this first - example
• legacy contact - Facebook (introduced 2015-02-12)
• ... ajoutez-en et attribuez-les au silo innovant

User Innovations Inside

Despite silos typically exerting tight control over their look, feel, and overall user experience, users have found ways of innovating inside silos, which silos have often adopted and integrated into their UX.

• reply permalinks - Twitter - reply posts on their own permalinks instead of just fragment links on a post.
  • Specifically, @-replies, were previously "only" in comments (e.g. comments in MySpace and Flickr used @-name conventions to indicate who they were responding to in a thread). When Twitter users started using @-reply syntax[5][6] in tweets to intentionally direct their tweets at particular people, Twitter adopted this in multiple ways:
    • auto-link @-mentions to profile pages (was in response to user-behavior)
    • show @-reply tweets only to those who followed both the replier and the user being replied to.[7]
    • auto-fill "Reply" textarea underneath a tweet with @-mention of the tweet author
    • auto-fill "Reply" textarea also with @-mentions of anyone else mentioned in the tweet.
• hashtags - as proposed by Chris Messina[8] on Twitter, then adopted by users, then eventually auto-linked by Twitter to search results for mentions of that hashtag.
• retweets - the "RT @-name:" syntax (originally ReTweet:) was purely a user innovation to indicate that they were passing along text/content from another user. Twitter both:
  • codified "RT" into a one-click button (so easy to use as to cause million+ retweeted posts)
  • showed the original author of the tweet, when presenting the retweet in others' reading views.
• 🍞 for like - Ello users in Germany adopted a convention of typing ":bread:" to generate a bread emoji (🍞) in a comment as a simple indicator of "liking" a post, since Ello lacks an explicit like/favorite feature.
• ... add more user innovation inside silos with attribution to user(s) if known, and inside which silo.

Criticism

See why for more common issues with silos in contrast to having your own website.

Linkwrapping

Many silos wrap any links posted on them with their own domains or link-wrapping domains, sometimes in an attempt to make links shorter, sometimes to provide a bottleneck which they can use to mass disable spam/phishing links.

Downsides:

• Breaks link referrals (you just see the silo wrapper, not the actual post that linked to your domain)
• Fragile for all the usual link-shorteners by a site other than the owner are fragile problem. As well as their typical use of database ids.

Examples:

• Facebook: m.facebook.com/l.php...[9]
• Twitter: t.co
• Feedly: Feedly Short URL fail
• ... others?

Artificially Slow UI

• 2016-07-06 The UX Secret That Will Ruin Apps For You

  Facebook actually slows down its interface to make users feel safe, a Facebook spokesperson confirmed in an email.
  
  ... various services on the web including travel sites, mortgage engines, and security checks are all making a conscious effort to slow down their omnipotent minds because our puny human brains expect things to take longer.
  
  ... companies introduce what Kowitz calls an "artificial waiting" pattern into their interfaces. These are status bars, maybe a few update messages, to construct a facade of slow, hard, thoughtful work, even though the computer is done calculating your query.

Another good reason to use your own tools (if it's faster than expected, you feel accomplished, not distrusting), or at least re-use indieweb software etc. that others are selfdogfooding because you know they won't be (or there's at least less chance of them) deliberately slowing it down.

Quitter les Silos

Un certain nombre d'individus, plus on moins célèbres ont quitté publiquement différents silos

• silo-quits

Silos Arlésiennes

From time to time, silo projects are announced without shipping, and often never ship. As this list grows we can consider creating a separate vaporware-silos page.

• Cybe appears to be a splash screen and silo at cybe.me with a ton of rhetoric ("manifesto", "vision", etc.) but no product. Their Twitter hasn't been updated in over a year.
• ... add other silos that have been announced but not shipped, preferably with a citation to the announcement, preferably date-stamped.

Articles and Talks

• 2017-04-18 Maciej Cegłowski talk: Build a Better Monster: Morality, Machine Learning, and Mass Surveillance
• 2017-05-23 Eric Petitt: Browse Against the Machine

See Also

• bulshytt
• history
• sites with data portability
• site deaths
• site changes
• commons
• monoculture
• 2017-12-03 Joshua Topolsky / The Outline: The death of the internet / If we lose this, we lose everything.
• https://www.eff.org/the-story-of-wael-abbas
• 2017-10-30 The Web began dying in 2014, here's how