Blogger - Historique des versions

Xtof le 15 février 2020 à 19:16

2020-02-15T19:16:52Z

Xtof le 15 février 2020 à 19:12

2020-02-15T19:12:27Z

Xtof : Page créée avec « {{iwc}} »

2020-02-07T01:20:56Z

Page créée avec « {{iwc}} »

Nouvelle page

@@ Ligne 2 : / Ligne 2 : @@
 [[Category:silo]]
 <span style="float:right">http://uploads.pixyblog.com/news/logo-blog-blogger.png</span>
-'''<dfn>[http://blogger.com/ Blogger]</dfn>''' is a blog content hosting [[silo]] owned by [[Google]].
+{{stub-fr}}
 "Blogger" était le nom d’une des premières applications de service de blogging ([http://en.wikipedia.org/wiki/Software_as_a_service SaaS]) qui utilisait votre propre domaine et votre propre fournisseur d’[[hosting-fr|hébergement]] pour le stockage de votre blog, et FTP comme une API pour éditer votre site. Si l’application Blogger tombait, votre site fonctionnait encore (pour servir servir vos posts) - la seule chose que vous ne pouviez par faire était d’utiliser l’application pour éditer ou publier de nouveaux posts. En ce sens, le Blogger original était tout à fait un outil complètement IndieWeb - vous possédiez et contrôliez toujours entièrement votre contenu, car tout était stocké chez votre propre hébergeur.
@@ Ligne 16 : / Ligne 18 : @@
 __TOC__
 == Hébergement de domaine ==
-It is possible to setup Blogger to serve your blog on your own domain for free to [[get started]] on the IndieWeb.
+Il est possible de paramétrer Blogger pour servir gratuitement votre blog sur votre propre domaine pour [[get started-fr|démarrer]] sur l’IndieWeb.
 * http://support.google.com/blogger/bin/static.py?hl=en&ts=1233381&page=ts.cs
-See in particular this tutorial:
+Regardez en particulier ce tutoriel  :
-* '''[[Tutorial Set up an Indie Website using Blogger|Tutorial: Set up an Indie Website using Blogger]]'''
+* '''[[Tutorial Set up an Indie Website using Blogger-fr|Tutoriel : Paraméter un site Indieweb en utilisant Blogger]]'''
 === Problèmes ===
-Issues folks have run into with Blogger's custom domain support.
+Les problèmes que les personnes ont rencontrés avec le support de domaine personnalisé chez Blogger.
 * Blogger defaults to dynamic templates, which create pages without HTML content (they are dynamically generated by [[JavaScript]] API calls). Example: lizasperling.com (fetching lizasperling.com?m=1 will get the mobile version, which does contain HTML).
@@ Ligne 39 : / Ligne 41 : @@
 </blockquote>
-== Exportation de Data Export ==
+== Exportation de Data ==
 You can export Blogspot-hosted content by logging into blogger.com and going to ''Settings'', then ''Other'' for each blog, then choosing ''Back up content''. This will generate an XML file with your site's content and template. You can also manage videos from the same settings view. The backup does not include any images.

← Version précédente		Version du 15 février 2020 à 19:12
Ligne 1 :		Ligne 1 :
−	{{~~iwc~~}}	+	Cette page a démarré sur [[iwc:Blogger]] et migrera après traduction sur [[iwc:Blogger-fr]]
		+
		+	[[Category:silo]]
		+	<span style="float:right">http://uploads.pixyblog.com/news/logo-blog-blogger.png</span>
		+	{{stub}}
		+
		+	'''<dfn>[http://blogger.com/ Blogger]</dfn>''' is a blog content hosting [[silo]] owned by [[Google]].
		+
		+	"Blogger" était le nom d’une des premières applications de service de blogging ([http://en.wikipedia.org/wiki/Software_as_a_service SaaS]) qui utilisait votre propre domaine et votre propre fournisseur d’[[hosting-fr\|hébergement]] pour le stockage de votre blog, et FTP comme une API pour éditer votre site. Si l’application Blogger tombait, votre site fonctionnait encore (pour servir servir vos posts) - la seule chose que vous ne pouviez par faire était d’utiliser l’application pour éditer ou publier de nouveaux posts. En ce sens, le Blogger original était tout à fait un outil complètement IndieWeb - vous possédiez et contrôliez toujours entièrement votre contenu, car tout était stocké chez votre propre hébergeur.
		+
		+	Google a fermé l'application Blogger le 2010-05-01.[http://en.wikipedia.org/wiki/Blogger_%28service%29]
		+
		+	L'équipe Blogger a créé "Blogspot.com" comme une version hébergée ([[silo]]) de l'application Blogger, qui a ensuite été diffusée à partir de blogger.com puis renommée "Blogger", remplaçant ainsi la signification d'origine et la fonctionnalité de l'application web avec un [[silo]].
		+
		+
		+	__TOC__
		+	== Hébergement de domaine ==
		+	It is possible to setup Blogger to serve your blog on your own domain for free to [[get started]] on the IndieWeb.
		+	* http://support.google.com/blogger/bin/static.py?hl=en&ts=1233381&page=ts.cs
		+
		+	See in particular this tutorial:
		+	* '''[[Tutorial Set up an Indie Website using Blogger\|Tutorial: Set up an Indie Website using Blogger]]'''
		+
		+	=== Problèmes ===
		+	Issues folks have run into with Blogger's custom domain support.
		+
		+	* Blogger defaults to dynamic templates, which create pages without HTML content (they are dynamically generated by [[JavaScript]] API calls). Example: lizasperling.com (fetching lizasperling.com?m=1 will get the mobile version, which does contain HTML).
		+	* Blogger adds a rel="me" link to your Google+ profile URL, but it uses the long form (21 digit number), not the human readable name, thus confusing IndieAuth.
		+
		+	== webmention ==
		+	Blogger doesn't have built in support for [[webmention]]s, but [[Bridgy]] can send, receive, and display webmentions for Blogger blogs. You can also receive webmentions with [[webmention.io]] and [https://webmention.herokuapp.com/ webmention.herokuapp.com].
		+
		+	== Les utilisateurs possèdent leur contenu ==
		+	[http://www.google.com/intl/en/policies/terms/ Google's TOS] ([https://support.google.com/blogger/answer/41935?hl=en&ref_topic=12467 which cover Blogger directly]; checked 2014-07-21) assert that users retain ownership and copyright over all content and intellectual property they post. From
		+	[http://www.google.com/intl/en/policies/terms/#toc-content Your Content in Our Services]:
		+
		+	<blockquote>
		+	Some of our Services allow you to upload, submit, store, send or receive content. You retain ownership of any intellectual property rights that you hold in that content. In short, what belongs to you stays yours.
		+	</blockquote>
		+
		+	== Exportation de Data Export ==
		+
		+	You can export Blogspot-hosted content by logging into blogger.com and going to ''Settings'', then ''Other'' for each blog, then choosing ''Back up content''. This will generate an XML file with your site's content and template. You can also manage videos from the same settings view. The backup does not include any images.
		+
		+	Google Takeout for Blogger will export both your content and your activity such as commenting on other blogs. Your blog content will be in ATOM format, while other information like followers and settings are in CSV. Your comments are provided in ATOM format. While videos should be included, again images are not.
		+
		+	Other options:
		+
		+	* https://github.com/otherjoel/blogger2kirby - python scripts to export your Blogger blog posts with images and comments to a bunch of [[Markdown]] files[https://twitter.com/joeld/status/534797720955781120]
		+	* https://github.com/cheshrkat/blogger-archive-converter - nodejs scripts to convert exported blogger/blogspot XML files and download images. Outputs to HTML, Markdown and JSON. See project readme for more details.
		+
		+	== Micropub ==
		+	It is possible to use [[Micropub]] clients like Quill to post to Blogger sites using [[Feverdream]] as a bridge.
		+
		+	== PubSubHubbub ==
		+
		+	Uses [[PubSubHubbub]] to publish Atom feeds since [http://buzz.blogger.com/2009/08/blogger-joins-hubbub.html 2009-08-17]
		+
		+	== Critique ==
		+	=== blogs disappeared ===
		+	* 2016-07-24 The New Yorker: [https://www.newyorker.com/culture/culture-desk/why-did-google-erase-dennis-coopers-beloved-literary-blog Why Did Google Erase Dennis Cooper’s Beloved Literary Blog?]
		+	* 2016-07-29 NYT: [https://www.nytimes.com/2016/07/30/opinion/sunday/the-blog-that-disappeared.html The Blog That Disappeared]([https://twitter.com/edsu/status/759543775161180161 via @edsu #indieweb]) <blockquote>On June 27, Mr. Cooper’s Google account was deactivated, he has said. He lost 14 years of his blog archives, creative work, email and contacts.</blockquote> … <blockquote>Google has not responded beyond saying there was a violation of the Terms of Service agreement. It has neither identified the specific violation nor indicated why it also deleted Mr. Cooper’s email account. It has not provided Mr. Cooper with the ability to download his personal information so he might rebuild his blog and email account elsewhere.</blockquote> … <blockquote>Mr. Cooper’s is not the only blog that has been deleted over the years. There are reports here and there across the internet about blogs, mostly, being deleted for violations of Terms of Service. What is happening to Mr. Cooper, though, in terms of lack of an explanation, seems to be unprecedented, and he has, as of yet, the highest profile of those who have experienced this measure of data loss.</blockquote> … <blockquote>The idea of a cloud benevolently storing our personal information, our work, our photos, our music, so much of our lives, is also really nice, but as users, we have no control over the cloud.</blockquote>
		+
		+	=== les modèles utilisent XML ===
		+	Blogger templates still require use of their custom XML, which has inconveniences like:
		+	<blockquote>blogger templates are still xml, so I have to CDATA escape the javascript ... [http://indiewebcamp.com/irc/2014-04-18/line/1397880406]</blockquote>
		+
		+	== Voir aussi ==
		+	* [[Getting Started-fr\|Démarrer sur indieweb]]
		+	* [[Google-fr\|Google]]
		+	* [[silo-fr\|silo]]
		+	* [[site-deaths-fr\|cimetière des sites]]
		+	* [https://drmacsspot.blogspot.com/2019/02/mrkndvs-making-indieweb-blogger-theme.html @mrkndvs Making an #IndieWeb Blogger Theme]
		+	* [[Tutorial Set up an Indie Website using Blogger-fr\|Tutoriel : Paramétrer un site Indieweb en utilisant Blogger]]