Différences entre versions de « Photo »

De Mi caja de notas
(Ménage en cours : synchro + traduction structure pour étude)
Ligne 1 : Ligne 1 :
−
Source [[iwc:photo]] : étude en cours
+
[[Category:PostType]]
−
 
 
−
 
 
 
<span style="float:right;height:128px;font-size:128px;margin:0 0 -64px">📷</span>
 
<span style="float:right;height:128px;font-size:128px;margin:0 0 -64px">📷</span>
  
 
{{stub}}
 
{{stub}}
  
−
<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 [[iwc:multi-photo|multi-photo]].</div>
+
<div class="p-summary">Une '''<dfn>photo</dfn>''' est un [[post-fr|post]] 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 [[iwc:photo upload|téléversement de photo]] est généralement la façon dont les photos sont créées.
+
Un [[photo upload|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 [[iwc:profile photo|photo de profil]].
+
Le terme “photo” peut aussi faire référence à une [[profile photo-fr|photo de profil]].
  
 
== Pourquoi ==
 
== Pourquoi ==
−
Vous devriez posséder vos photos comme vous possédez tous les autres contenus que vous créez. Beaucoup de sites de photos sont [[iwc:site-deaths|tombés]] et partis au cimetière ces dernières années, emportant au passage vos souvenirs inestimables.
+
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 ==
 +
Il There are different approaches to posting photos. E.g.
 +
* As a [[note]] with a primary image
 +
* As an image, with text (caption) only following
 +
** the image is the focus of the post, and text is in service of the image.
 +
* Hosting variations - image files hosted on
 +
** your primary webhost/domain
 +
** a "photos." subdomain of your domain that maps to a cloud/CDN service like [[Amazon]] [[S3]] or [[Akamai]].
 +
** as Creative Commons licensed content uploaded to [[Wikimedia]]
 +
 
 +
=== Tagage ===
 +
Tagging (AKA annotating) photos, initially popularized by [[Flickr]], has become a key motivation for publishing photos. Here are a number of ways you can tag photo posts, both directly in a post, and as a response to a photo post!
 +
 
 +
Implemented / in practice:
 +
* [[tag]] / [[tag-reply]] - tag a photo with a word or phrase
 +
* <span id="People_Tagging">[[person-tag]]</span> / [[person-tag-reply]] - tag a photo with a person
 +
 
 +
Research / Brainstorming:
 +
* [[location]] / [[location-of]] - setting/suggesting the location of a photo is colloquially referred to as tagging a photo with a location.
 +
* [[area-tag]] / [[area-tag#area_tag_reply|area-tag-reply]] - tagging a specific area of a photo, either with text, or a person-tag.
 +
Consider adding research from analyzing [[IIIF]] prior and current work.
 +
 
 +
=== POSSEr ===
 +
[[POSSE]]ing photo posts makes sense certainly to photo [[silos]] like:
 +
* [[Flickr]] - as a backup, for Creative Commons distribution
 +
** Bridgy Publish [https://github.com/snarfed/bridgy/issues/432 supports POSSEing to Flickr]!
 +
* [[Instagram]] (as much as you can fake a POSSE post to Instagram using [[ownyourgram]] to PESOS then link back to the IG photo with [[rel-syndication]])
 +
* [[Wikimedia Commons]] - as a [[commons]] rather than a silo, it may make sense to start POSSEing here as a backup/distribution/CDN mechanism
 +
 
 +
In addition, it makes sense to POSSE to generic silos, despite the fact that they will only retain a (likely) lower resolution copy of your photo:
 +
* [[Twitter]] - as a native Twitter photo tweet  for your friends on Twitter to see your photos
 +
** using TwitterAPI, or
 +
** using Bridgy Publish[https://github.com/snarfed/bridgy/issues/85]
 +
* [[Facebook]] - similarly for your friends on Facebook to see your photos
 +
** using Bridgy Publish[https://github.com/snarfed/bridgy/issues/85] - which also supports copying over person-tags (of anyone person-tagged with their indieweb site who is signed up on Bridgy, or with Facebook profile URLs with profile IDs)
 +
 
 +
==== POSSE tags de personne ====
 +
You should POSSE any [[person-tag]]s on your photo to any POSSE copy as well.
 +
 
 +
== Exemples IndieWeb ==
 +
Sorted by earliest photo posts first.
 +
 
 +
=== Ryan Barrett ===
 +
[[User:Snarfed.org|Ryan Barrett]] uses [[WordPress]] to post photo posts on [https://snarfed.org/pictures snarfed.org/pictures] since around [https://snarfed.org/draw_group 2003-03-06] and [[multi-photo]] posts [https://snarfed.org/2014-12-23_12146 since 2014-12-23]. Examples:
 +
* https://snarfed.org/draw_group
 +
* multi https://snarfed.org/2014-12-23_12146
 +
** very much looks like a photo
 +
** no explicit photo post markup, rather, it's marked up as an [[article]] with a nested [[check-in]] inside.
 +
** Facebook POSSE: https://www.facebook.com/snarfed.org/posts/10101422243050323
 +
*** as a multi-photo post with location information (rather than a check-in) with individual photo permalinks:
 +
*** https://www.facebook.com/212038/posts/10101422242815793
 +
*** https://www.facebook.com/212038/posts/10101422242965493
 +
 
 +
=== Bret Comnes ===
 +
[[User:bret.io|Bret Comnes]] uses [[gitpub]] to post photos directly on bret.io [http://bret.io/2013/02/26/pictures-from-portland/ since 2013-02-26], and started posting photos using [[ownyourgram]] on [http://bret.io/2014/05/18/ownyourgram/ 2014-05-18].  E.g.
 +
* http://bret.io/2013/02/26/pictures-from-portland/ (first photo post)
 +
* http://bret.io/2014/05/18/ownyourgram/ (first photo post with ownyourgram)
 +
 
 +
=== Ben Werdmuller ===
 +
[[User:Werd.io|Ben Werdmuller]] uses [[idno]] to post photos (including taking them with a mobile web upload interface that uses the camera!) on [http://werd.io/ werd.io] (since ????-??-??), and [[POSSE]]s them to [[Facebook]] and [[Flickr]] (since ????-??-??)
 +
* e.g. ??? a photo post permalink on werd.io
 +
* mobile photography and posting demonstrated live at IndieWebCamp [[2013]] in Portland.
 +
 
 +
=== Aaron Parecki ===
 +
{{aaronpk}} has been posting photos to his own site since [[2014/SF|IndieWebCamp SF]] on 2014-03-08, using [[OwnYourGram]] to turn [[Instagram]] into a publishing client.
 +
* e.g. http://aaronparecki.com/notes/2014/05/06/3/iiw-indieweb
 +
 
 +
=== Kyle Mahan ===
 +
{{kylewm}} has been posting photos of his cat since 2014-05-17, using [[OwnYourGram]] and occasionally uploading images directly
 +
* e.g. https://kylewm.com/photo/2014/05/17/1 (OwnYourGram)
 +
* https://kylewm.com/photo/2014/06/29/1 (direct upload)
 +
* multi-photo: https://kylewm.com/2014/06/untitled-1 (possed to Facebook and Twitter as a simple link)
 +
 
 +
=== Jeremy Keith ===
 +
[[User:adactio.com|Jeremy Keith]] uses his own custom [[PHP]]-based CMS to post photos (with [[location]] info!) on adactio.com and [[POSSE]] them to [[Twitter]] since [http://adactio.com/notes/6978/ 2014-07-05] and to [[Flickr]] since [http://adactio.com/notes/7021 2014-07-08]. Examples:
 +
* http://adactio.com/notes/6978/
 +
** POSSE copy: https://twitter.com/adactio/status/485552177080201217
 +
* http://adactio.com/notes/7021 - first photo POSSEd to both Twitter and 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+.
 +
Examples:
 +
* 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]).
 +
Examples:
 +
* 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 ==
 +
The following [[silos]] specialize in photo posting/hosting/sharing:
 +
* [[Flickr]]
 +
* [[Instagram]]
 +
* [[Wikimedia Commons]]
 +
 
 +
In addition, the following silos support photo posts in addition to other types of posts:
 +
* [[Facebook]]
 +
* [[Google+]]
 +
 
 +
Here are some notes on specific silo treatment of photos:
 +
 
 +
=== Facebook ===
 +
With Facebook, you have the options of:
 +
* creating an actual [[photo]] post (preferred)
 +
** Note that the [[POSSE_to_Facebook#See_Original]] trick does not work with photo posts
 +
* or posting a status update ([[note]]) and linking to the original photo or if you're linking to a permalink on your own site (e.g. as part of [[POSSE]]ing), optionally using [[OGP]] to specify the image to use for a preview.<br>[[File:facebook-post-with-preview-image.png|none|thumb|Facebook note with preview image]]
 +
Creating an actual photo post looks much better.
 +
More detail: [[POSSE_to_Facebook#Posting_Photos_via_the_Facebook_API]]
 +
 
 +
== Brainstorming ==
 +
{{main|photo brainstorming}}
 +
 
 +
=== Les Personnes Taguent ===
 +
See: [[area-tag#person_tag_as_area_tag|person tag as area tag]]
 +
 
 +
=== POSSE ===
 +
More brainstorming about POSSEing photos!
 +
 
 +
==== Distinguishing Photos from 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 ===
 +
* When I start hosting my own photos, I have thought about using the Coral CDN. http://www.coralcdn.org/ {{gRegor}}
 +
 
 +
== Logiciel ==
 +
Software you can install on your IndieWeb server to host your own photos
 +
 
 +
* GNU [http://mediagoblin.org/ Mediagoblin]
 +
* [[Photo Project]] (formerly Trovebox, and before that, <span id="OpenPhoto">OpenPhoto</span>)
 +
 
 +
== Sessions ==
 +
IndieWebCamp sessions about photo posts and photos in general:
 +
* [[2016/Dusseldorf/photos]]
 +
 
 +
== Voir aussi ==
 +
* [[multi-photo]]
 +
* [[photo brainstorming]]
 +
* [[photo upload]]
 +
* [[posts]]
 +
* [[notes]]
 +
* [[video]]

Version du 1 janvier 2017 à 13:14

📷

Cet article est une ébauche. Vous pouvez m'aider à l'améliorer et le compléter. Merci.

Une photo est un post est un post dont le contenu primaire est une photographie ou autre image, avec une légende facultative.

Avec plusieurs photographies, cela devient un post multi-photos.

Un 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 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 disparu au fil des ans, emportant au passage des souvenirs personnels inestimables.

Comment

Il There are different approaches to posting photos. E.g.

  • As a note with a primary image
  • As an image, with text (caption) only following
    • the image is the focus of the post, and text is in service of the image.
  • Hosting variations - image files hosted on
    • your primary webhost/domain
    • a "photos." subdomain of your domain that maps to a cloud/CDN service like Amazon S3 or Akamai.
    • as Creative Commons licensed content uploaded to Wikimedia

Tagage

Tagging (AKA annotating) photos, initially popularized by Flickr, has become a key motivation for publishing photos. Here are a number of ways you can tag photo posts, both directly in a post, and as a response to a photo post!

Implemented / in practice:

Research / Brainstorming:

  • location / location-of - setting/suggesting the location of a photo is colloquially referred to as tagging a photo with a location.
  • area-tag / area-tag-reply - tagging a specific area of a photo, either with text, or a person-tag.

Consider adding research from analyzing IIIF prior and current work.

POSSEr

POSSEing photo posts makes sense certainly to photo silos like:

In addition, it makes sense to POSSE to generic silos, despite the fact that they will only retain a (likely) lower resolution copy of your photo:

  • Twitter - as a native Twitter photo tweet for your friends on Twitter to see your photos
    • using TwitterAPI, or
    • using Bridgy Publish[1]
  • Facebook - similarly for your friends on Facebook to see your photos
    • using Bridgy Publish[2] - which also supports copying over person-tags (of anyone person-tagged with their indieweb site who is signed up on Bridgy, or with Facebook profile URLs with profile IDs)

POSSE tags de personne

You should POSSE any person-tags on your photo to any POSSE copy as well.

Exemples IndieWeb

Sorted by earliest photo posts first.

Ryan Barrett

Ryan Barrett uses WordPress to post photo posts on snarfed.org/pictures since around 2003-03-06 and multi-photo posts since 2014-12-23. Examples:

Bret Comnes

Bret Comnes uses gitpub to post photos directly on bret.io since 2013-02-26, and started posting photos using ownyourgram on 2014-05-18. E.g.

Ben Werdmuller

Ben Werdmuller uses idno to post photos (including taking them with a mobile web upload interface that uses the camera!) on werd.io (since ????-??-??), and POSSEs them to Facebook and Flickr (since ????-??-??)

  • e.g. ??? a photo post permalink on werd.io
  • mobile photography and posting demonstrated live at IndieWebCamp 2013 in Portland.

Aaron Parecki

portrait Aaron Parecki has been posting photos to his own site since IndieWebCamp SF on 2014-03-08, using OwnYourGram to turn Instagram into a publishing client.

Kyle Mahan

Modèle:Kylewm has been posting photos of his cat since 2014-05-17, using OwnYourGram and occasionally uploading images directly

Jeremy Keith

Jeremy Keith uses his own custom PHP-based CMS to post photos (with location info!) on adactio.com and POSSE them to Twitter since 2014-07-05 and to Flickr since 2014-07-08. Examples:

Calum Ryan

Modèle:Calumryan has been posting photos directly to his website and then syndicating to Twitter since 2015-07-19. Examples:

Kartik Prabhu

Kartik Prabhu uses Bundle to publish photo posts since 2014-07-27, and multi-photo posts since 2014-07-28. He does the following:

  1. Uploads the photo(s) to G+ albums purely for storage
  2. Publishes a photo(s) post on his own site
  3. (Semi-)automatically POSSEs to Twitter as a photo post via Bridgy, since 2014-08-30
  4. Manually POSSEs to G+.

Examples:

Tantek

portrait Tantek Çelik uses Falcon to publish photo posts since 2015-244 which are note posts with an embedded image that have been auto-upgraded to being photo posts. He does the following:

  1. Usually uses Instagram iOS client to post a photo there.
    • Sometimes to Wikimedia commons instead.
    • Sometimes to IndieWebCamp wiki instead.
  2. 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.
  3. That "note" is auto-upgraded by CASSIS's auto_link function into a photo post by putting the u-photo class name on the auto-embed <img> of the JPG, since it's the first URL in the "note".
  4. Falcon automatically uses Bridgy Publish to POSSE the photo as a photo post to Twitter & Facebook (since 2015-11-08 including POSSEing Facebook person-tags since 2015-12-05), and Flickr (since 2016-02-01, manually since 2016-01-16 of a 2016-01-01 photo), saving the resulting syndication URLs in storage.

Examples:

Since this was an auto-upgrade change, it is likely that there are older notes that got upgraded to photo posts as well.

gRegor Morrill

portrait gRegor Morrill uses ProcessWire to occasionally publish photos.

Ryan Rix

Modèle:Rrix uses Arcology to publish photos through his site and syndicate them out to Facebook and Twitter using Bridgy.

Jay Robinson

Modèle:J4y funabashi is backfilling his site with ~10 years worth of photos

Marty McGuire

portrait Marty McGuire uses Quill with a custom micropub handler to post photos (with notes).

Marty is also displaying interactive 360 photospheres (panoramic images in equirectangular projection, common in cameras like the Ricoh Theta S). In browsers with Javascript enabled, the panoramic images are upgraded to an interactive 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

Barnaby Walters uses Taproot to post photos on waterpigs.co.uk since at least 2012-12-13 as notes with embedded images.

Discussion

  • portrait gRegor Morrill: I don't understand the distinction between 'photo' and 'note with photo.' It was suggested in chat by 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/ — IRC log
  • On a photo post, text is directly "related to the photo", where text in a note can be "conversational" or tangential.

    <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.

    [3]

Silos

The following silos specialize in photo posting/hosting/sharing:

In addition, the following silos support photo posts in addition to other types of posts:

Here are some notes on specific silo treatment of photos:

Facebook

With Facebook, you have the options of:

Creating an actual photo post looks much better. More detail: POSSE_to_Facebook#Posting_Photos_via_the_Facebook_API

Brainstorming

Article principal : photo brainstorming

Les Personnes Taguent

See: person tag as area tag

POSSE

More brainstorming about POSSEing photos!

Distinguishing Photos from 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 posts notes with a u-photo as photo posts.

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-tagging on your POSSE photo copies.

Two reasons why:

  1. 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!)
  2. 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.[4]

Héberger

Logiciel

Software you can install on your IndieWeb server to host your own photos

Sessions

IndieWebCamp sessions about photo posts and photos in general:

Voir aussi

Récupérée de « https://ducamp.me/index.php?title=Photo&oldid=3361 »