Différences entre versions de « Photo »

De Mi caja de notas

(à continuer)
Ligne 44 : Ligne 44 :
  
 
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 :  
 
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]] - as a native Twitter photo tweet  for your friends on Twitter to see your photos
+
* [[Twitter]] - sous forme de tweet photo natif Twitter pour que vos amis sur Twitter voient vos photos
−
** using TwitterAPI, or
+
** en utilisant TwitterAPI, ou
−
** using Bridgy Publish[https://github.com/snarfed/bridgy/issues/85]
+
** en utilisant Bridgy Publish[https://github.com/snarfed/bridgy/issues/85]
−
* [[Facebook]] - similarly for your friends on Facebook to see your photos
+
* [[Facebook]] - de la même manière pour que vos amis Facebook voient vos 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)
+
** 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 ====
 
==== POSSE tags de personne ====
−
You should POSSE any [[person-tag]]s on your photo to any POSSE copy as well.
+
Vous devriez POSSEr aussi les [[person-tag|tag de personnes]] sur votre photo vers n'importe quelle copie POSSÉE.
  
 
== Exemples IndieWeb ==
 
== Exemples IndieWeb ==

Version du 1 janvier 2017 à 13:29

📷

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 faire

Il existe différentes approches pour poster des photos. Par ex.

  • Sous forme de 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.
  • 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 Amazon S3 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 :

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

POSSEr des posts de photo a du sens pour les silos de photos comme :

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[1]
  • 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

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=3363 »