<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="https://shkspr.mobi/blog/wp-content/themes/edent-wordpress-theme/rss-style.xsl" type="text/xsl"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	    xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	     xmlns:dc="http://purl.org/dc/elements/1.1/"
	   xmlns:atom="http://www.w3.org/2005/Atom"
	     xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	  xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>
<channel>
	<title>IndieWebCamp &#8211; Terence Eden’s Blog</title>
	<atom:link href="https://shkspr.mobi/blog/tag/indiewebcamp/feed/" rel="self" type="application/rss+xml" />
	<link>https://shkspr.mobi/blog</link>
	<description>Regular nonsense about tech and its effects 🙃</description>
	<lastBuildDate>Thu, 02 Oct 2025 07:09:48 +0000</lastBuildDate>
	<language>en-GB</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.4</generator>

<image>
	<url>https://shkspr.mobi/blog/wp-content/uploads/2023/07/cropped-avatar-32x32.jpeg</url>
	<title>IndieWebCamp &#8211; Terence Eden’s Blog</title>
	<link>https://shkspr.mobi/blog</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title><![CDATA[]]></title>
		<link>https://shkspr.mobi/blog/2024/05/49911/</link>
					<comments>https://shkspr.mobi/blog/2024/05/49911/#comments</comments>
				<dc:creator><![CDATA[@edent]]></dc:creator>
		<pubDate>Thu, 02 May 2024 11:34:51 +0000</pubDate>
				<category><![CDATA[/etc/]]></category>
		<category><![CDATA[blogging]]></category>
		<category><![CDATA[HTML]]></category>
		<category><![CDATA[IndieWebCamp]]></category>
		<guid isPermaLink="false">https://shkspr.mobi/blog/?p=49911</guid>

					<description><![CDATA[While attending IndieWebCamp in Brighton a few weeks ago, a bunch of us were talking about blogging. What is post? What should it contain? What&#039;s optional?  Someone (probably Jeremy Keith said:  A blog post doesn&#039;t need a title.  In a literal sense, he was wrong. The HTML specification makes it clear that the &#60;title&#62; element is mandatory. All documents have title.  But, in a practical sense, he…]]></description>
										<content:encoded><![CDATA[<p>While attending IndieWebCamp in Brighton a few weeks ago, a bunch of us were talking about blogging. What is post? What should it contain? What's optional?</p>

<p>Someone (probably <a href="https://adactio.com/">Jeremy Keith</a> said:</p>

<blockquote><p>A blog post doesn't need a title.</p></blockquote>

<p>In a literal sense, he was wrong. The <a href="https://html.spec.whatwg.org/multipage/semantics.html#the-head-element">HTML specification</a> makes it clear that the <code>&lt;title&gt;</code> element is mandatory. All documents have title.</p>

<p>But, in a practical sense, he was right. This blog post has an empty <code>&lt;h1&gt;</code> element - the document might be semantically invalid, it might reduce accessibility, but the <em>post</em> is still available.</p>

<p>A blog post can be a plain text document uploaded to a server. It can be an image hosted on a social network. It can be a voice note shared with your friends.</p>

<p>Title, dates, comments, links, and text are all <em>optional</em>.</p>

<p>No one is policing this.</p>

<p>Go create something which doesn't fit properly with the rest of the world.</p>
<img src="https://shkspr.mobi/blog/wp-content/themes/edent-wordpress-theme/info/okgo.php?ID=49911&HTTP_REFERER=RSS" alt="" width="1" height="1" loading="eager">]]></content:encoded>
					
					<wfw:commentRss>https://shkspr.mobi/blog/2024/05/49911/feed/</wfw:commentRss>
			<slash:comments>12</slash:comments>
		
		
			</item>
		<item>
		<title><![CDATA[Caboom! Comment Anywhere, Bring Onto Own Media]]></title>
		<link>https://shkspr.mobi/blog/2024/03/caboom-comment-anywhere-bring-onto-own-media/</link>
					<comments>https://shkspr.mobi/blog/2024/03/caboom-comment-anywhere-bring-onto-own-media/#respond</comments>
				<dc:creator><![CDATA[@edent]]></dc:creator>
		<pubDate>Thu, 21 Mar 2024 12:34:02 +0000</pubDate>
				<category><![CDATA[/etc/]]></category>
		<category><![CDATA[blogging]]></category>
		<category><![CDATA[IndieWebCamp]]></category>
		<guid isPermaLink="false">https://shkspr.mobi/blog/?p=49892</guid>

					<description><![CDATA[In the IndieWeb movement there&#039;s a concept of &#34;POSSE&#34; - Publish Once, Simultaneously Syndicate Elsewhere.  You should publish your words, pictures, songs, reviews on your own site. And then you can choose to share them out to where your audience is. Perhaps that&#039;s posting the link on Facebook, or a copy of a photo on Instagram, or sharing the episode on YouTube.  There&#039;s no shame in meeting your…]]></description>
										<content:encoded><![CDATA[<p>In the IndieWeb movement there's a concept of "POSSE" - <a href="https://indieweb.org/POSSE">Publish Once, Simultaneously Syndicate Elsewhere</a>.</p>

<p>You should publish your words, pictures, songs, reviews on your <em>own</em> site. And then you can choose to share them out to where your audience is. Perhaps that's posting the link on Facebook, or a copy of a photo on Instagram, or sharing the episode on YouTube.</p>

<p>There's no shame in meeting your audience where they are - but the canonical version should be somewhere you control.</p>

<p>But what about the conversation? Social media is about socialising. People who comment on LinkedIn can't see the comments on Mastodon and vice versa.</p>

<p>This is where the concept of "CABOOM!" (exclamation optional) comes in<sup id="fnref:liz"><a href="https://shkspr.mobi/blog/2024/03/caboom-comment-anywhere-bring-onto-own-media/#fn:liz" class="footnote-ref" title="As suggested by my wife" role="doc-noteref">0</a></sup>. As far as practical, you should bring the various comment threads together so everyone can see them<sup id="fnref:backfeed"><a href="https://shkspr.mobi/blog/2024/03/caboom-comment-anywhere-bring-onto-own-media/#fn:backfeed" class="footnote-ref" title="The technical term is, apparently, backfeed - which sounds a little too like backwash for my liking!" role="doc-noteref">1</a></sup>.</p>

<p>There are a few ways to do this - choose whichever is right for you.</p>

<h2 id="do-nothing"><a href="https://shkspr.mobi/blog/2024/03/caboom-comment-anywhere-bring-onto-own-media/#do-nothing">Do Nothing</a></h2>

<p>Let people self-discover that you syndicate. Perhaps they'll stumble upon a bunch of people discussing your post over on Slashdot.  That's fine, but a little hard work.</p>

<h2 id="point-to-your-syndication-sites"><a href="https://shkspr.mobi/blog/2024/03/caboom-comment-anywhere-bring-onto-own-media/#point-to-your-syndication-sites">Point to your syndication sites</a></h2>

<p>At the bottom of your post, you can say "Click here to read the comments on MySpace!"</p>

<h2 id="find-other-sources"><a href="https://shkspr.mobi/blog/2024/03/caboom-comment-anywhere-bring-onto-own-media/#find-other-sources">Find other sources</a></h2>

<p>Did someone share your post to HackerNews? Add a link on your page to the orange-site so that others can read what's being said.</p>

<h2 id="convert-comments-to-webmentions"><a href="https://shkspr.mobi/blog/2024/03/caboom-comment-anywhere-bring-onto-own-media/#convert-comments-to-webmentions">Convert comments to WebMentions</a></h2>

<p>Using a service like <a href="https://brid.gy/">Brid.gy</a> you can "upgrade" external comments to <a href="https://www.w3.org/TR/webmention/">WebMentions</a>.  They will appear on your post as normal comments, but with a link back to their original location.</p>

<h2 id="abuse-apis"><a href="https://shkspr.mobi/blog/2024/03/caboom-comment-anywhere-bring-onto-own-media/#abuse-apis">(Ab)use APIs</a></h2>

<p>Services like Reddit have APIs. You could pull in a complete comment thread and present it on your own site.</p>

<h2 id="make-backups"><a href="https://shkspr.mobi/blog/2024/03/caboom-comment-anywhere-bring-onto-own-media/#make-backups">Make backups</a></h2>

<p>Some of those external sites are going to break one day. Take a backup using <a href="https://archive.org">Archive.org</a> or snap a screenshots.  Perhaps link to those if the original goes away.</p>

<h2 id="be-mindful-of-others-feelings"><a href="https://shkspr.mobi/blog/2024/03/caboom-comment-anywhere-bring-onto-own-media/#be-mindful-of-others-feelings">Be mindful of others' feelings</a></h2>

<p>I've previously discussed <a href="https://shkspr.mobi/blog/2022/12/the-ethics-of-syndicating-comments-using-webmentions/">the ethics of syndicating comments using WebMentions</a>. Not everyone wants their comment copied back to your site. Some people regularly delete comments. Or they may have valid copyright concerns.  Just because someone has written something in public, it doesn't mean it is in the public domain. Be kind to your commenters and respect their wishes.</p>

<h2 id="have-fun"><a href="https://shkspr.mobi/blog/2024/03/caboom-comment-anywhere-bring-onto-own-media/#have-fun">Have fun</a></h2>

<p>There is literally no-one policing this. If you don't want to do it, that's fine. If you want to give it your best effort, that's also fine.</p>

<div id="footnotes" role="doc-endnotes">
<hr aria-label="Footnotes">
<ol start="0">

<li id="fn:liz">
<p>As suggested by <a href="https://web.archive.org/web/20240403222815/https://mymisanthropicmusings.org.uk/">my wife</a>&nbsp;<a href="https://shkspr.mobi/blog/2024/03/caboom-comment-anywhere-bring-onto-own-media/#fnref:liz" class="footnote-backref" role="doc-backlink">↩︎</a></p>
</li>

<li id="fn:backfeed">
<p>The technical term is, apparently, <a href="https://indieweb.org/backfeed">backfeed</a> - which sounds a little too like backwash for my liking!&nbsp;<a href="https://shkspr.mobi/blog/2024/03/caboom-comment-anywhere-bring-onto-own-media/#fnref:backfeed" class="footnote-backref" role="doc-backlink">↩︎</a></p>
</li>

</ol>
</div>
<img src="https://shkspr.mobi/blog/wp-content/themes/edent-wordpress-theme/info/okgo.php?ID=49892&HTTP_REFERER=RSS" alt="" width="1" height="1" loading="eager">]]></content:encoded>
					
					<wfw:commentRss>https://shkspr.mobi/blog/2024/03/caboom-comment-anywhere-bring-onto-own-media/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
