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 faire
Il existe différentes approches pour poster des photos. Par ex.
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.
Variations 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 AmazonS3 ou Akamai.
sous forme de contenu licencié 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
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 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
Facebook - de la même manière pour que vos amis Facebook voient vos photos
en utilisant Bridgy Publish[2] - 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 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.
Ben Werdmuller utilise idno pour poster des photos (y compris en les prenant avec une interface web mobile qui utilise l'appareil photo !) sur werd.io (depuis ????-??-??), et les POSSEs 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.
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:
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 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".
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.
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
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.
<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.
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.
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 POSSEr), en utilisant OGP (facultatif) pour spécifier l'image à utiliser pour une prévisualisation .
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.
(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 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:
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.[4]
This article is a stub. You can help the IndieWeb wiki by expanding it.
A photo is a post whose primary content is a photograph or other image, with an optional caption. With multiple photographs it becomes a multi-photo post.
A photo upload is typically how photo posts are created.
You should own your photos like you own any other content you create. Many photos sites have gone down over the years, taking invaluable personal memories with them.
How
There are different approaches to posting photos. E.g.
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 AmazonS3 or Akamai.
as Creative Commons licensed content uploaded to Wikimedia
How to markup
(stub section)
Be sure to markup your actual photo image (or hyperlink to higher quality image) class="u-photo". A photo post could look like this:
<div class="h-entry">
<img class="u-photo" src="photo.jpg">
<p class="p-content">Look at this awesome sunset!</p>
<p>published on <time class="dt-published">2013-03-07</time> by <a href="/" class="u-author">me</a>
</div>
(could be rephrased better) This also means, don't go marking up every random image in every random post with "u-photo", unless you really want every random post being mistaken for a photo post.
Tagging
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
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 person tags
You should POSSE any person-tags on your photo to any POSSE copy as well.
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.
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:
Writes & posts a note on his own site that starts with a direct .jpg URL of a medium-sized photo image, then alt text inside parentheses with a space on both sides, then a space or linebreak, then direct .jpg URL of the full size photo image, then linebreak, then caption.
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". Alt text (if any) is also similarly recognized and added to the img tag, as well as the subsequent link, as a hyperlink around the img tag.
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.
Each Photo is some kind of post which can contain multiple images and/or additionally some description. On mouse hover a title and description for the photo 'post' is shown.
Dries Buytaert the Founder and Project Lead of Drupal. He is also Co-founder and CTO of Acquia. Dries has been working on Open Source and an Open Web for 20+ years. He blogs at https://dri.es/. Dries uses Drupal to manage his photo albums and his photo stream, complete with an RSS feed just for photos. Dries been posting photos on my website for more than 20 years. After uploading photos to his website, he occasionally POSSEs a photo to his Instagram. In November 2022, he had over 10,000 photos on his website, and around 300 photos on Instagram. His website is my primary platform for sharing photos. Dries describes his approach and rationale at https://dri.es/a-photo-stream-for-my-site.
2022-08-09: this link was listed as the multi-photo but it appears to be an RSVP; I think the previous link in list was the multi-photo so I updated accordingly gRegor Morrill 11:26, 9 August 2022 (PDT)
Site no longer active, verified 2021-08-20
Bret Comnes
Bret Comnes used gitpub to post photos directly on bret.io since 2013-02-26, and started posting photos using ownyourgram on 2014-05-18. E.g.
I think this is the first photo I posted http://j4y.co/p/20160405164556_5703ddb45dbf0 (could not find this specific post on Internet Archive)
Jay's site is not retrievable as of 2021-08-20. Their wiki user page indicates they've migrated to https://jay.funabashi.co.uk/, but that is not retrievable as of 2022-12-07.
Notes with image examples
Notes with embedded photos that are not marked up with u-photo are similar to photo posts.
2017-07-21: the image src in this post is dead currently
Discussion
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
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.
<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.
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.
Kylewm.com: I would consider this post about going to a museum a note with a photo that is not a photo post — The text stands alone; the image is secondaryA note with a photo
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 POSSEing), optionally using OGP to specify the image to use for a preview. Facebook note with preview image
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.
(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 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:
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.[5]
Tantek Çelik use-case is I want sometimes I want to post a bunch (a ton?) of photos and not worry that it would be "filling up" my homepage or stream etc. related: publics - concerns about overposting.
Aaron Parecki Ah yeah the "dump lots of photos" problem i can relate to
Concerns:
Aaron Parecki: "I often have unrelated photos in a sequence on my home page and I don't want them to cluster in a way that implies they are related"
Approaches:
If the photos share a hashtag which is used in <10% of photo posts, then cluster them.
that way if they really were "unrelated" photos, they wouldn't get clustered
Workaround:
Aaron Parecki "if I wanted photos to be clustered I would make an album post instead"
Hosting my own photos has been something I've been wanting to do for a while. This is partly because I'm unhappy with most of the silos I've used:
Instagram — fine for the odd snap, but I use it in private mode because there's no easy way of having privacy controls.
Facebook — fine for putting up photos of friends, but... it's Facebook and they creep me out.
Flickr — one word: Yahoo! It's been redesigned a couple of times now, not necessarily for the better.
Wikimedia Commons — I'm reasonably confident Commons will stick around, but am unhappy with some of the administrative politics (and deeply distrust some of the administrators), and it has a limited scope—hosting only "freely-licensed educational media content". Commons is a great place to host some but not all content I wish to post. Commons is also very rigid about copyright: it attempts to adhere to copyright in both the United States and in the country where the photograph was taken. Some photos taken in France, Belgium, Italy and (with obscure exceptions) the Netherlands which do not have freedom of panorama cannot be hosted on Commons even though the images are legal in my country of citizenship, the United Kingdom.
Ideally, I want to host my own photos and have some of them stored elsewhere. The ones I don't want to be public are probably best stored on Facebook.
Urban75 — Urban75 is an old-school staple of British independent web publishing. The layout is very 90s but the photography is pretty good, and the information architecture makes me want to explore it more.
How to take photos
Some tips here for how as an indie photographer you can instruct your subjects:
The acts of capturing (taking) photos, then selecting which ones to post where, then editing them how and why, are essential to the overall task of publishing photos, yet most of the documentation we have is about once you have a photo that you want to post, how do you post it.
This brainstorming section is meant to capture everything between when you first think of taking a photo (and why), and when you have a photo ready to publish.
Capturing:
Tantek Çelik I take photos quite often, whenever I feel I see something "interesting" and can do so without badly interrupting the flow of whatever I happen to be doing. I also quite regularly take photos of food and drink I’m consuming, menus of restaurants I visit, and maps when visiting other cities. I usually take photos with HDR explicitly selected to "On" on my iPod Touch.
non-HDR versions of photos (exceptions: sometimes with motion, the non-HDR version is higher quality, or has fewer artifacts and is preferred. Sometimes sunrise / sunset photos look better in the non-HDR version, especially with colors, brightness, and lens flare effects).
non-best photos of something - If I have a series of photos of the same thing at around the same time, with similar framing, I’ll likely delete all but the best / most representative photo of that "moment".
photos making people look bad - photos that capture an unfortunate, awkward, or embarrassing facial expression or posture, either of others or myself.
Selecting:
Tantek Çelik I go through photos of an event or activity and favorite (heart) some of them in the iOS Photos app as a way of choosing which ones I may or likely do want to post publicly in a photo or multiphoto post.
More broadly, I select photos that won't violate someone's privacy for online upload / archival. Because I archive on Swarm/Foursquare (not the most reliable), access is a limited set of friends-only, so I feel fairly confident with uploading most photos without fear. I may keep or delete other photos, typically only keeping those that have a personal/private significance.
I go through the photos I intend to upload/archive online and recent "favorited" (in iOS Photos app) photos, and do basic corrective edits of:
rotating to align horizon and some minimal cropping to remove extraneous things on the edges.
if a photo is close to a good alignment of horizon (e.g. 50% or on one of the thirds lines), I’ll likely rescale the photo and pan it to align the horizon accordingly.
For photos I intend to publish, I do a bit more thorough editing, specifically:
deciding on a possible alternative cropping (from the original landscape/portrait crop), e.g. square or 16:9, depending on the subject matter and how well the cropping frames the context and subject of the photo.
after cropping I may pan the image to align one more more subjects / points of interest in the image with either one of the thirds lines, or middle of the image (horizontally and/or vertically).
Uploading / archival:
Tantek Çelik since I don't yet have a Media upload Micropub endpoint, I use Swarm for limited friends-only uploading / archival of my photos
Tantek Çelik I'm hosting by using static private igx.4sqi.net JPG URLs currently (occasionally similar direct static JPG URLs from Wikimedia posts or IndieWeb uploads), but want to switch to my own images.tantek or photos.tantek etc. URLs that redirect.
We need to collect the different ways people are marking up the caption of a photo post, e.g. in which properties (name, summary, content, several thereof?), in same property as u-photo images themselves (e.g. in e-content), and then come up with one or a few recommended ways to markup the caption of a photo.
Inside the e-content
I have been wrapping the img class="u-photo" and caption in the e-content[6]. Mainly because I initially set up my templates to wrap the post's content that way -- for use with notes and articles. I'm open to changing that for photos. Currently, removing the e-content and putting the caption in a p-name p-summary sounds like a good recommendation. gRegor Morrill 18:25, 22 December 2017 (PST)
add other variation
...
Attribution
We currently do not have a way to identify the photographer if not the h-entry author.
I just use HTML and do not worried about nested h-entries but I am not sure if this is true anymore as parsers handle nested h-entries
I utilize the CC flickr attribution tool and then generate the attribution included:
<small><a title="my-url-is from SXSW2003" href="https://flickr.com/photos/tantek/7727729324"><img src="https://live.staticflickr.com/8166/7727729324_f6f44b6c72_z.jpg" /></a><br /><small><a title="my-url-is from SXSW2003" href="https://flickr.com/photos/tantek/7727729324">“my-url-is from SXSW2003”</a> by <a href="https://flickr.com/people/tantek">tantek</a> is licensed under <a href="https://creativecommons.org/licenses/by-nc/2.0/">CC BY-NC</a> </small></p>
Software
Software you can install on your IndieWeb server to host your own photos
"We have normalised taking pictures and videos of people without consent. We’ve made it socially acceptable to capture strangers going about their day to post to audiences that they themselves are unaware they’re “entertaining”. There is an entitlement to these actions." @kylemalanda November 12, 2021
if you're not sure if a note you are publishing is a photo post or not, then it's a note post, not a photo post.
tof : cette page a démarré sur photo et reste à synchroniser et traduire. Merci.
📷
Aaron Parecki poste des photos sur son propre site depuis IndieWebCamp SF le 2014-03-08, en utilisant OwnYourGram pour transformer Instagram en client de pubication.
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:
gRegor Morrill uses ProcessWire to occasionally publish photos.
Marty McGuire uses Quill with a custom micropub handler to post photos (with notes).
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.
Calum Ryan has been posting photos directly to his website and then syndicating to Twitter since 2015-07-19. Examples:
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:
gRegor Morrill uses ProcessWire to occasionally publish photos.
Jason Garber uses FrancisCMS to publish photo posts to his website https://sixtwothree.org since 2015-12-18.
Max Dietrich uses Strapi to publish photos on https://mxd.codes/photos.
Anthony Ciccarello has published photo posts since 2021-06-21 and has an instagram-style gallery page. These include posts with video and multi-photo posts (though not formatted to the standard) He also backfilled Instagram posts.
Kyle Mahan has been posting photos of his cat since 2014-05-17, using OwnYourGram and occasionally uploading images directly
