Voir la source de Photo

[[Category:PostType]]
<span style="float:right;height:128px;font-size:128px;margin:0 0 -64px">📷</span>

{{stub-fr}}


<div class="p-summary">Une '''<dfn>photo</dfn>''' est un [[post-fr|post]] dont le contenu primaire est une photographie ou autre image, avec une légende facultative. Avec plusieurs photographies, cela devient un post [[multi-photo-fr|multi-photos]].

Un [[photo upload-fr|téléversement de photo]] est généralement la façon dont les photos sont créées.

Le terme “photo” peut aussi faire référence à une [[profile photo-fr|photo de profil]].

== Pourquoi ==
Vous devriez posséder vos photos comme vous possédez tout autre contenu que vous créez. 
Beaucoup de sites de photos ont [[site-deaths|disparu]] au fil des ans, emportant au passage des souvenirs personnels inestimables.

== Comment faire ==
Il existe différentes approches pour poster des photos. Par ex. 
* Sous forme de [[note-fr|note]] avec une image primaire
* Sous forme d'image, avec un texte (légende) suivant 
** l'image est le coeur du post, et le texte est au service de l'image.
* Variantes d'hébergement - les fichiers images sont hébergés sur 
** votre domaine/hébergeur primaire
** un sous-domaine "photos." de votre domaine qui pointe vers un service cloud/CDN comme [[Amazon]] [[S3]] ou [[Akamai]].
** sous forme de contenu sous licence Creative Commons téléversé sur [[Wikimedia]]

=== Tagage ===
Taguer (ou annoter) les photos, initialement popularisé par [[Flickr]], est devenu une motivation clé pour la publication de photos. 
Voici un certain nombre de façons de taguer des messages photo, soit directement dans un message, soit en réponse à un message photo !

Implémenté / en pratique : 
* [[tag]] / [[tag-reply]] - taguer une photo avec un mot ou phrase
* <span id="People_Tagging">[[person-tag]]</span> / [[person-tag-reply]] - taguer une photo avec une personne 

Recherche / Brainstorming:
* [[location]] / [[location-of]] - réglage/suggestion du lieu d'une photo fait référence à marquer une photo avec un endroit.
* [[area-tag]] / [[area-tag#area_tag_reply|area-tag-reply]] - taguer une aire spécifique d'une photo, soit avec du texte, soit avec un tag-personne.
Considérez d'ajouter la recherche à partir de l'analyse d'[[IIIF]] et du travail en cours.

=== POSSEr ===
[[POSSE]]r des posts de photo a du sens pour les [[silos]] de photos comme :
* [[Flickr]] - comme sauvegarde, pour la distribution en Creative Commons
** Bridgy Publish [https://github.com/snarfed/bridgy/issues/432 supporte le POSSE vers Flickr]!
* [[Instagram]] (tant que vous pouvez simuler un faux post POSSE vers Instagram en utilisant [[ownyourgram]] pour PESOS alors faites un lien retour vers la photo IG avec [[rel-syndication]])
* [[Wikimedia Commons]] - en tant que [[commons|commun]] plutôt qu'un silo, cela peut avoir du sens de démarrer le POSSE ici comme mécanisme de sauvegarde/distribution/CDN

En outre, cela a du sens de POSSer vers les silos génériques, malgré le fait qu'ils ne retiendront (probablement) qu'une copie de plus faible résolution de votre photo : 
* [[Twitter]] - sous forme de tweet photo natif Twitter pour que vos amis sur Twitter voient vos photos
** en utilisant TwitterAPI, ou
** en utilisant Bridgy Publish[https://github.com/snarfed/bridgy/issues/85]
* [[Facebook]] - de la même manière pour que vos amis Facebook voient vos photos
** en utilisant Bridgy Publish[https://github.com/snarfed/bridgy/issues/85] - qui supporte aussi de copier sur les person-tags (de quiconque personne-tagué avec son site indieweb qui soit enregistré sur Bridgy, ou avec des URLs de profil avec des IDs de profil)

==== POSSE tags de personne ====
Vous devriez POSSEr aussi les [[person-tag|tag de personnes]] sur votre photo vers n'importe quelle copie POSSÉE.

== Exemples IndieWeb ==
Triés en remontant les posts de photos les plus récents tout en haut.

=== Ryan Barrett ===
[[User:Snarfed.org|Ryan Barrett]] utilise [[WordPress]] pour poster des posts de photos sur [https://snarfed.org/pictures snarfed.org/pictures] depuis le [https://snarfed.org/draw_group 2003-03-06] et les posts [[multi-photo]]  [https://snarfed.org/2014-12-23_12146 depuis le 2014-12-23]. Exemples :
* https://snarfed.org/draw_group
* multi https://snarfed.org/2014-12-23_12146
** ressemble vraiment à une photo
** pas de maquage explicite du post de photo, à la place, il est balisé sous forme d'un [[article]] avec un [[check-in]] embarqué à l'intérieur : 
** Facebook POSSE : https://www.facebook.com/snarfed.org/posts/10101422243050323
*** sous forme de post multi photo avec information de localisation (plutôt qu'un check-in) avec permaliens individuels de photo : 
*** https://www.facebook.com/212038/posts/10101422242815793
*** https://www.facebook.com/212038/posts/10101422242965493

=== Bret Comnes ===
[[User:bret.io|Bret Comnes]] utilise [[gitpub]] pour poster des photos directement sur bret.io [http://bret.io/2013/02/26/pictures-from-portland/ depuis 2013-02-26], et à commencer à poster des photos en utilisant [[ownyourgram]] sur  [http://bret.io/2014/05/18/ownyourgram/ 2014-05-18].  par ex.
* http://bret.io/2013/02/26/pictures-from-portland/ (premier post photo)
* http://bret.io/2014/05/18/ownyourgram/ (premier post photo avec ownyourgram)

=== Ben Werdmuller ===
[[User:Werd.io|Ben Werdmuller]] utilise [[idno]] pour poster des photos (y compris en les prenant avec une interface web mobile qui utilise l'appareil photo !) sur [http://werd.io/ werd.io] (depuis ????-??-??), et les [[POSSE]]s sur  [[Facebook]] et [[Flickr]] (depuis ????-??-??)
* par ex ??? un permalien de post photot sur werd.io
* photographie mobile et post démontré en live à l'IndieWebCamp [[2013]] à Portland.

=== Aaron Parecki ===
{{aaronpk}} poste des photos sur son propre site depuis [[2014/SF|IndieWebCamp SF]] le 2014-03-08, en utilisant  [[OwnYourGram]] pour transformer [[Instagram]] en client de pubication.
* par ex.. http://aaronparecki.com/notes/2014/05/06/3/iiw-indieweb

=== Jeremy Keith ===
[[User:adactio.com|Jeremy Keith]] utilise son propre CMS basé-sur-[[PHP]] pour poster des photos (avec l'info de [[location-fr|geoloc]] !) sur adactio.com les et  [[POSSE]] vers [[Twitter]] depuis [http://adactio.com/notes/6978/ 2014-07-05] et vers [[Flickr]] depuis [http://adactio.com/notes/7021 2014-07-08]. Exemples :
* http://adactio.com/notes/6978/
** Copie POSSE : https://twitter.com/adactio/status/485552177080201217
* http://adactio.com/notes/7021 - première photo POSSÉe à la fois sur Twitter et Flickr :
** https://twitter.com/adactio/status/486617601167339521
** https://www.flickr.com/photos/adactio/14604446101

=== Calum Ryan ===
{{calumryan}} has been posting photos directly to his website and then syndicating to Twitter since 2015-07-19. Examples:
* https://calumryan.com/note.php?noteId=115
** POSSE copy: https://twitter.com/calum_ryan/status/622793683147091968

=== Kartik Prabhu ===
[[User:kartikprabhu.com|Kartik Prabhu]] uses [[Bundle]] to publish photo posts [https://kartikprabhu.com/notes/dusty-rhodes-watershed since 2014-07-27], and [[multi-photo]] posts [https://kartikprabhu.com/notes/owen-engine since 2014-07-28]. He does the following:
* Uploads the photo(s) to G+ albums purely for storage
* Publishes a photo(s) post on his own site
* (Semi-)automatically POSSEs to Twitter as a photo post via [[Bridgy]], [https://twitter.com/kartik_prabhu/status/505886569085939712 since 2014-08-30]
* Manually POSSEs to G+. 
Exemples:
* 2014-07-27 single https://kartikprabhu.com/notes/dusty-rhodes-watershed
** POSSEd as a note to Twitter: https://twitter.com/kartik_prabhu/status/493622610929152000
** POSSEd as photo to G+: https://plus.google.com/117114060857732496623/posts/h73UJiUcCvU
* 2014-07-28 multi https://kartikprabhu.com/notes/owen-engine
** POSSEd as a note to Twitter: https://twitter.com/kartik_prabhu/status/493868886283280384
** POSSEd as multiple photos to G+: https://plus.google.com/+KartikPrabhu/posts/abVAnynme5w

=== Tantek ===
{{t}} uses [[Falcon]] to publish photo posts [http://tantek.com/2015/244/t1/did-entire-npsf-trackattack since 2015-244] which are [[note]] posts with an embedded image that have been auto-upgraded to being photo posts. He does the following:
* Usually uses [[Instagram]] iOS client to post a photo there.
** Sometimes to Wikimedia commons instead.
** Sometimes to IndieWebCamp wiki instead.
* Writes & posts a [[note]] on his own site that starts with a direct .jpg URL of the photo image, then a space/linebreak, then permalink of the Instagram post, then caption.
* That "note" is auto-upgraded by [[CASSIS]]'s <code>auto_link</code> function into a photo post by putting the <code>u-photo</code> class name on the [[auto-embed]] <code>&lt;img&gt;</code> of the JPG, since it's the first URL in the "note".
* Falcon automatically uses [[Bridgy]] Publish to [[POSSE]] the photo as a photo post to [[Twitter]] & [[Facebook]] ([http://tantek.com/2015/312/t2/yesterday-cat-mocha-caturday since 2015-11-08] including POSSEing Facebook person-tags [http://tantek.com/2015/339/t2/w3c-social-web-working-group-mozilla since 2015-12-05]), and [[Flickr]] ([http://tantek.com/2016/032/t1/mothership-bowl-second-breakfast since 2016-02-01], manually [https://www.flickr.com/photos/tantek/23803704613/ since 2016-01-16] of a [http://tantek.com/2016/001/t1/gregorian-january-lego-calendar 2016-01-01 photo]), saving the resulting syndication URLs in storage.
** Previously: 2015-09-01: *optionally* manually [[Bridgy]] Publish to [[POSSE]] the photo as a photo post to [[Facebook]] ([http://tantek.com/2015/311/t3/indiewebcamp-mit-the-album until 2015-11-07]).
Exemples:
* 2015-244 (09-01) http://tantek.com/2015/244/t1/did-entire-npsf-trackattack
** POSSEd as note to Twitter: https://twitter.com/t/status/638755285159559168
*** abbreviated text, with permashortlink to full post on own site
** Manually POSSEd as photo to Facebook: https://www.facebook.com/photo.php?fbid=10101862796233213
*** with entirety of text, including whitespace like line-breaks.
* 2015-254 (09-10) http://tantek.com/2015/253/t1/wakeupthesun-gasworkspark-np-sea
** POSSEd as complete note to Twitter: https://twitter.com/t/status/641956534994501632
** Manually POSSEd as photo to Facebook: https://www.facebook.com/photo.php?fbid=10101877363580133
Since this was an auto-upgrade change, it is likely that there are older notes that got upgraded to photo posts as well.
* 2015-312 (11-08) http://tantek.com/2015/312/t2/yesterday-cat-mocha-caturday
** POSSEd automatically as a photo to [https://twitter.com/t/status/663448949307543552 Twitter] and [https://www.facebook.com/photo.php?fbid=10101964022220523 Facebook] (via Bridgy Publish)
* multi-photo: http://tantek.com/2015/352/t1/building-lights-clouds-heels-cab
** has two photos
** only first was POSSEd via Bridgy Publish to Twitter and Facebook
* with person-tags: http://tantek.com/2015/352/t2/freedom-tower-np-nyc-winter
** though none of the person-tags made it through
* 2015-346 (12-12) http://tantek.com/2015/346/t2/eiffel-tower-small-world
** Photo posted/hosted at Wikimedia commons instead of Instagram

=== gRegor Morrill ===
{{gRegor}} uses [[ProcessWire]] to occasionally publish photos.
* First self-hosted photo: http://gregorlove.com/2015/08/i-found-some-silers/
* Earliest example with photo hosted on Flickr: http://gregorlove.com/2014/07/ladies-via-sarah5/

=== Ryan Rix ===

{{rrix}} uses [https://indiewebcamp.com/User:Notes.whatthefuck.computer#Arcology Arcology] to publish photos through his site and syndicate them out to Facebook and Twitter using [[Bridgy]].

=== Jay Robinson ===

{{j4y_funabashi}} is backfilling his site with ~10 years worth of photos
* I think this is the first photo I posted http://j4y.co/p/20160405164556_5703ddb45dbf0

=== Marty McGuire ===

{{martymcguire}} uses [[Quill]] with a custom micropub handler to post photos (with notes).
* First example: https://martymcgui.re/2016/04/28/133049/

Marty is also displaying interactive 360 photospheres (panoramic images in [https://en.wikipedia.org/wiki/Equirectangular_projection equirectangular projection], common in cameras like the [https://theta360.com/en/about/theta/ Ricoh Theta S]). In browsers with Javascript enabled, the panoramic images are upgraded to an interactive [https://github.com/google/vrview Google VR View].
* First example: https://martymcgui.re/2016/08/28/114014/
* Panoramas work like a regular photo post with a couple of exceptions:
** The large image size can lead to failed uploads or server rejections
** A panoramic photo is differentiated from a non-panoramic photo by EXIF XMP tag "ProjectionType=equirectangular"

== Notes with photos examples ==
Not quite photo posts, but similar, [[notes]] with embedded photos are another approach to photo-like posts.

=== Barnaby Walters ===
[[User:Waterpigs.co.uk|Barnaby Walters]] uses [[Taproot]] to post photos on [http://waterpigs.co.uk waterpigs.co.uk] since at least [http://waterpigs.co.uk/notes/686/ 2012-12-13] as notes with embedded images.

== Discussion ==
* {{gRegor}}: I don't understand the distinction between 'photo' and 'note with photo.' It was suggested in chat by [[User:Mowens.com|mko]] that a 'photo' post would be a photo with no other content. However, this page indicates caption text may follow the photo. Per discussion, the caption would be the p-summary/p-name of the photo post. This seems to make it no different than a regular note, then, as far as microformat parsing. Example: http://gregorlove.com/notes/2014/07/15/2/ — [http://indiewebcamp.com/irc/2014-07-15#t1405445144 IRC log]
** Per further discussion, mko explained that the caption would not appear in the e-content, as it does in my example. He offered these code examples to demonstrate the difference: https://gist.github.com/mko/f05e8cb0d2423f6deaa7

* On a photo post, text is directly "related to the photo", where text in a note can be "conversational" or tangential. <blockquote>&lt;mko> Another example, from my own experience. I was the design lead at hi5. We did research into how users were using the Photos feature versus the Status Update feature (which had the ability to post a photo). Users posted photos without any text the vast majority of the time. When users posted status updates with photos, on the other hand, they almost never did so without accompanying text. On top of that, we found that when there was text accompanying a photo in the Photos section, it was almost always a caption related to the photo (with very few exceptions), whereas those in a status update that would go on the Friend Feed typically was conversational and not directly related to the photo.</blockquote>[http://indiewebcamp.com/irc/2014-07-15#t1405447134]

* [[User:kartikprabhu.com|Kartik]]: I do not understand what would be the UI/UX difference in posting/reading a "photo with caption" vs "note with photo" ? Some examples (silo/indieweb) distinguishing these cases would be good.
** [[User:Kylewm.com|Kylewm.com]]: I would consider [https://kylewm.com/note/2014/05/05/1 this post about going to a museum] a note with a photo that is not a photo post &mdash; The text stands alone; the image is secondary[[File:kylewm-note-with-photo-2014-07-15.png|none|thumb|A note with a photo]]
** [[User:Wwelves.org perpetual-tripper|Wwelves.org perpetual-tripper]] facebook  [https://www.facebook.com/social.w3.org/posts/869811893104078 example of posting with embedded photo, which in turn has its own description] [[File:posting+embedded-photo.png|none|thumb]]

== Silos ==
Les [[silos]] qui suivent sont spécialisés dans le postage/hébergement/partage : 
* [[Flickr]]
* [[Instagram]]
* [[Wikimedia Commons]]

En outre, les silos suivants supportent les post de photo en plus d'autres types de posts :
* [[Facebook]]
* [[Google+]]

Voici quelques notes sur le traitement spécifique par silo des photos : 

=== Facebook ===
Avec Facebook, vous avez les options de 
* créer un véritable post [[photo]] post (préféfé)
** Notez que le truc [[POSSE_to_Facebook#See_Original]] ne fonctionne pas avec les posts photo
* ou poster une mise à jour de statut ([[note]]) et lier vers la photo originale ou si vous faites un lien vers un permalien vers votre votre site (par ex. comme une partie de [[POSSE]]r), en utilisant [[OGP]] (facultatif) pour spécifier l'image à utiliser pour une prévisualisation .<br>[[File:facebook-post-with-preview-image.png|none|thumb|Facebook note avec image de prévisualisation]]
Créer un véritable post de photo rend beaucoup mieux.
Plus de détails : [[POSSE_to_Facebook#Posting_Photos_via_the_Facebook_API]]

== Brainstorming ==
{{main|photo brainstorming}}

=== Tags de personnes ===
Voir : [[area-tag#person_tag_as_area_tag|person tag as area tag]]

=== POSSE ===
Plus de brainstorming pour POSSEr des photos !

==== Distinguer les Photos des Notes ====
[[Bridgy]] Publish has a concrete use-case where it would be useful to mechanically differentiate posts where the photo is primary, vs. notes with an included image that is not the focus of the note. Photo posts should be POSSEd as '''native''' photo post types on [[Facebook]] and included as attached media on [[Twitter]]. POSSEd notes would prefer to link to the original post, and possibly include the image as a [[link-preview]].

The problem is that both types have the same mf2 representation: p-name/e-content for caption and u-photo for the image.

Simplest solution is to treat all <strike>posts</strike> notes with a <code>u-photo</code> as photo posts.
* [https://github.com/snarfed/bridgy/issues/85 Bridgy resolution on this in GitHub.]

==== Pourquoi POSSEr plutôt que TwitterCard ====
(Not sure if this belongs here or on [[Twitter]] page, but capturing as part of this for now.)
Advantages to POSSEing actual photos to Twitter, rather than just a link to a photo post on your site with Twitter [[Cards]] metacrap markup:
* Further distribute the use of Twitter kind of like a CDN for your photos
* People see a larger version of the photo via a phototweet than a Twittercard
* Usual avoid [[metacrap]] (silo-specific meta tags) advantage
* Photo tweets appear inline in tweet list views (e.g. Twitter timeline / homepage) whereas twitter cards won't appear inline automatically (require twiddling open).
* Photo tweets work immediately, whereas photo cards require that Twitter whitelist your domain for cards in general (and maybe in particular for photo cards?)
* Using the TwitterAPI hides the proprietariness, whereas using twittercards means your own website has proprietary metacrap on it
* Twittercards set a worse example (proprietary metacrap) for others that may view source

=== backfeed person tags ===
If you're POSSEing photo posts, in addition to normal backfeed support of silo [[like]], [[repost]], [[reply]] responses, you should also support backfeeding [[person-tag]]ging on your POSSE photo copies.

Two reasons why:
* Your own convenience / ease of use. Some silos have nice/easy person-tagging UIs, i.e. that often auto-suggest who to tag in a photo with a simple one button (Yes) UI to do it (as you select/hover faces), e.g. [[Facebook]]. Thus it may be easier to implement backfeeding person-tags than implementing your own person-tagging UI (and facial recognition support too!)
* Person-tags from friends. Some silos let your friends tag people they know in your photos (e.g. [[Facebook]], [[Flickr]]), and thus they're likely to do so. You should backfeed these person-tags from your friends back to your original photo post.

Bridgy backfeed does not yet support backfeeding person tags from POSSE copies of photo posts.[http://indiewebcamp.com/irc/2015-09-01#t1441140760078]
* https://github.com/snarfed/bridgy/issues/488

=== Héberger ===
* Quand j'ai commencé à héberger mes propres photos, j'ai pensé à utiliser le CDN Coral http://www.coralcdn.org/ {{gRegor}}

== Logiciel ==
Le logiciel que vous installez sur votre serveur IndieWeb pour héberger vos propres photos

* GNU [http://mediagoblin.org/ Mediagoblin]
* [[Photo Project]] (formerly Trovebox, and before that, <span id="OpenPhoto">OpenPhoto</span>)

== Sessions ==
Les sessions IndieWebCamp concernant les posts de photo et les photos en général :
* [[2016/Dusseldorf/photos]]

== Voir aussi ==
* [[multi-photo-fr|multi-photo]]
* [[photo brainstorming|brainstorming photo]]
* [[photo upload|téléversement de photos]]
* [[posts-fr|posts]]
* [[notes-fr|notes]]
* [[video-fr|vidéo]]