Xtof : /* POSSE */

2017-01-03T00:07:23Z

POSSE

Xtof le 2 janvier 2017 à 20:54

2017-01-02T20:54:29Z

Xtof le 2 janvier 2017 à 20:54

2017-01-02T20:54:09Z

Xtof : Page créée avec « voir et traduire iwc:photo upload »

2017-01-02T20:48:54Z

Page créée avec « voir et traduire iwc:photo upload »

Nouvelle page

voir et traduire [[iwc:photo upload]]

@@ Ligne 9 : / Ligne 9 : @@
 == POSSE ==
-It is possible to [[POSSE]] photo uploads via silo-specific APIs to the following:
+Il est possible de [[POSSE]]r les téléversements de photo via des APIs spécifiques aux silos vers ce qui suit :
 * [[Facebook]]
 * [[Flickr]]
-* [[Wikimedia Commons]] - the API is somewhat complex and undocumented, but for some images that meet [http://commons.wikimedia.org/wiki/COM:SCOPE the project scope] and are licensed under free licenses (CC BY-SA, CC BY, CC0/PD or equivalent)
+* [[Wikimedia Commons]] - l'API est un peu complexe et non documenté, mais pour quelques images qui rejoigent le  [http://commons.wikimedia.org/wiki/COM:SCOPE thème du projet] et sont une licence libre (CC BY-SA, CC BY, CC0/PD ou équivalent)
-** So long as images are not deleted, you are able to store images there indefinitely, hot link them and use Commons to retrieve scaled versions.
+** Tant que les images ne sont pas effacées, vous pouvez y stocker des images indéfiniment, hotlinkez les et utilisez les Communs pour retrouver les versions passées à l'échelle.
 == PuPuPu ==

← Version précédente		Version du 2 janvier 2017 à 20:54
Ligne 1 :		Ligne 1 :
−	{{xtof}} pour [[~~100DaysOfPhotos~~]] -> étude d'[[iwc:photo upload]] pour migration après étude sur [[iwc:photo upload-fr]]	+	{{xtof}} pour [[100DaysOfPhoto]] -> étude d'[[iwc:photo upload]] pour migration après étude sur [[iwc:photo upload-fr]]

	{{stub-fr}}		{{stub-fr}}

← Version précédente		Version du 2 janvier 2017 à 20:54
Ligne 1 :		Ligne 1 :
−	voir ~~et traduire~~ [[~~iwc~~:photo upload]]	+	{{xtof}} pour [[100DaysOfPhotos]] -> étude d'[[iwc:photo upload]] pour migration après étude sur [[iwc:photo upload-fr]]
		+
		+	{{stub-fr}}
		+	= téléversement de photo =
		+	Le <dfn>téléversement de photo</dfn> est l'acte de créer un [[post-fr\|post]] dont le contenu primaire est une [[photo-fr\|photo]], généralement généralement capturé par une caméra sur le même périphérique qui crée le message.
		+
		+	Pour les UIs pour [[create-fr\|créer]] une photo, voir :
		+	* [[create-fr#Photo]]
		+
		+	== POSSE ==
		+	It is possible to [[POSSE]] photo uploads via silo-specific APIs to the following:
		+	* [[Facebook]]
		+	* [[Flickr]]
		+	* [[Wikimedia Commons]] - the API is somewhat complex and undocumented, but for some images that meet [http://commons.wikimedia.org/wiki/COM:SCOPE the project scope] and are licensed under free licenses (CC BY-SA, CC BY, CC0/PD or equivalent)
		+	** So long as images are not deleted, you are able to store images there indefinitely, hot link them and use Commons to retrieve scaled versions.
		+
		+	== PuPuPu ==
		+	The popular mobile photo site [[Instagram]] deliberately lacks an API for uploads[http://instagram.com/developer/endpoints/media/]. However it does have an API for real-time notifications of uploads[http://instagram.com/developer/realtime/].
		+
		+	This presents the opportunity to build a [[PuPuPu]] system with Instagram as a publishing client:
		+
		+	* [[Instagram]]
		+	** -> real-time notification to (and post creation on) your own site
		+	*** -> syndication with permalinks to:
		+	**** [[Facebook]]
		+	**** [[Flickr]]
		+	**** [[Twitter]]
		+	**** [[Wikimedia Commons]] (for photos you don't mind contributing as CC BY-SA, CC BY, CC0/PD or equivalent)
		+	**** ...
		+
		+	Technically this would be Push-Push-Publishing, since the notifications from Instagram are done in real-time using the [[PuSH]] protocol.
		+
		+	=== Implementations ===
		+	The [[OwnYourGram]] service enables you to use Instagram as a publishing client for posting photos to your own site.
		+
		+	== HTML5 photo uploads ==
		+	HTML5 extends the input element to permit pages to declaratively attempt photo uploads with:
		+	* <code><input type="file" accept="image/*"></code>
		+	For documentation on how this works in browsers see:
		+	* [https://developer.mozilla.org/en-US/docs/HTML/Element/Input#Image_capture_from_cameras documentation of camera capture on developer.mozilla.org]
		+
		+	== Mobile upload ==
		+	Until in-browser approaches mature, it may be necessary to use native apps (either tied to a service and then [[PESOS]], or a wrapper app around personal blogging web apps to provide camera functionality).
		+
		+	=== HTML5 Mobile browser upload ===
		+	* [https://plus.google.com/115133653231679625609/posts/bWvt1eu4KAn The Current State Of Photo/Video Capture In Mobile Browsers]
		+
		+	=== Other approaches ===
		+	* Email as possible approach? Most smart phones have an email client, and/or have "email this photo" support built-into their native/default camera applications. If you could set-up a custom email address (security through obscurity) on your own domain for receiving photo uploads, you could use that to "upload" photos, and then have your indieweb site POSSE out to the above-mentioned silos.
		+
		+	* [[OwnCloud]] has an Android client which can upload new photos taken on the camera to your own installation,
		+
		+	* Android [http://botsync.com/ BotSync] will watch a subdirectory on your phone and use the <code>scp</code> protocol to transfer new files in that directory to a server, but appears to have some issues with larger files (ie: video).
		+
		+	* The Android app "FolderSync" appears to be a more full-featured alternative to BotSync.
		+
		+	* At the [[2016/Dusseldorf/photos\|IWC Düsseldorf photo session]] multiple people reported that the Dropbox App works most reliably for photo transfer from mobile
		+
		+	* With such sync approaches it makes sense for the UI to offer the user the option to pick an image from the recently uploaded ones
		+
		+	* HTTP uploads (and by extension everything based on them, e.g. [[Micropub]], normal HTML upload forms) by default do not support uploading files bit-by-bit or resuming interrupted uploads, which is a problem esp. for mobile connections. A common solution seems to be to allow multiple requests with offsets to write parts of the file, and server implementations that also write data from aborted requests. (Examples: [https://www.dropbox.com/developers/documentation/http/documentation#files-upload_session-start dropbox API], [http://tus.io/ tus.io protocol] (attempt to standardize such a protocol))
		+
		+	== Desktop upload ==
		+	Some browsers support uploading images from a laptop/monitor camera:
		+	* [http://www.w3.org/TR/html-media-capture/ HTML Media Capture] API — W3C Candidate Recommendation, implemented in Chrome desktop, [https://bugzilla.mozilla.org/show_bug.cgi?id=741393 feature request bug for Firefox].
		+
		+	== See also ==
		+	* [[create#Photo]]
		+	* [[photo]]
		+	* [[post]]
		+	* [[POSSE]]
		+	* [[PESOS]]
		+	* [[PuPuPu]]

Photo upload-fr - Historique des versions

Xtof : /* POSSE */

Xtof le 2 janvier 2017 à 20:54

Xtof le 2 janvier 2017 à 20:54

Xtof : Page créée avec « voir et traduire iwc:photo upload »