<?xml version="1.0" encoding="utf-8" standalone="yes"?><?xml-stylesheet type="text/xsl" href="/pretty-feed-v3.xsl"?>
<rss
  version="2.0"
  xmlns:atom="http://www.w3.org/2005/Atom"
  xmlns:content="http://purl.org/rss/1.0/modules/content/"
  xmlns:source="https://source.scripting.com/"
>
  <channel>
    <title>Paul Tibbetts</title>
    <link>https://paultibbetts.uk/2025/09/09/</link>
    <description>Posts by Paul Tibbetts published on Tuesday, September 9, 2025</description>
    <generator>Hugo</generator>
    <language>en-gb</language>
    <atom:link href="https://paultibbetts.uk/2025/09/09/feed.xml" rel="self" type="application/rss+xml" /><item>
      <title>Getting My Own Site</title>
      <link>https://paultibbetts.uk/2025/09/09/getting-my-own-site/</link>
      <pubDate>Tue, 09 Sep 2025 20:00:00 +0100</pubDate>
      <guid>https://paultibbetts.uk/2025/09/09/getting-my-own-site/</guid>
      <category>IndieWeb</category>
      <category>meta</category>
      <description>The second step to getting on the IndieWeb is to have your own site.
This is easier said than done, and there are lots of different ways of doing it.
This is what I did.</description>
      <content:encoded><![CDATA[<p>The second step to <a href="https://indieweb.org/Getting_Started">getting on the IndieWeb</a>
 is to have your own site.</p>
<p>This is easier said than done, and there are lots of different ways of doing it.</p>
<p>This is what I did.</p>
<h2 id="as-a-web-developer">As a web developer</h2>
<p>There are three paths to getting your own site.</p>
<h3 id="service">Service</h3>
<p>You could use an existing service like <a href="https://micro.blog/">Micro.blog</a>
 to host your site.</p>
<p>I already do this for my <a href="https://micro.paultibbetts.uk/">microblog</a>
 because it comes with a bunch of features out of the box and gets me onto the IndieWeb, even while I don&rsquo;t yet support all the IndieWeb features on my main site.</p>
<h3 id="cms">CMS</h3>
<p>An alternative path is to use an existing content management system and add on IndieWeb features with plugins.</p>
<p>I&rsquo;ve done this in the past with <a href="https://wordpress.org/">WordPress</a>
 but I moved on from the WordPress world a while ago.</p>
<h3 id="self-starter">Self-starter</h3>
<p>I decided I was more comfortable writing and doing it myself.</p>
<h2 id="what-it-needs-to-do">What it needs to do</h2>
<p>Before I wrote any code I made sure to cover the basics.</p>
<h3 id="information-about-me">Information about me</h3>
<p>The homepage of my site needs to include a <a href="https://indieweb.org/h-card">h-card</a>
 with my name, an icon, and <a href="https://indieweb.org/rel-me">rel-me</a>
 links to my social network profiles.</p>
<p>This is not only useful for humans but I can also use it to sign in to other sites using <a href="https://indieweb.org/IndieAuth">IndieAuth</a>
.</p>
<p>I used <a href="https://indiewebify.me/">IndieWebify.me</a>
 to check I&rsquo;d done it correctly.</p>
<h3 id="publish-content">Publish content</h3>
<p>My posts should be marked up using <a href="https://indieweb.org/h-entry">h-entry</a>
 so that others can understand my content.</p>
<p>The original site design had words with titles, which makes them technically &ldquo;articles&rdquo;, although that could change in the fture.</p>
<h2 id="how-the-site-works">How the site works</h2>
<p>There are lots of different ways to do this.</p>
<p>In fact there are too many, so I kept it as simple as I could.</p>
<h3 id="static-site-generator">Static site generator</h3>
<p>I want to write my content in <a href="https://www.markdownguide.org/">Markdown</a>
, I would prefer doing that on my laptop instead of my phone, and I&rsquo;m ok running commands to publish things.</p>
<p>Which means I can use a <a href="https://en.wikipedia.org/wiki/Static_site_generator">static site generator</a>
 like <a href="https://gohugo.io">Hugo</a>
 to turn my markdown files into HTML.</p>
<h2 id="hosting">Hosting</h2>
<p>One of the best parts about using a static site generator is that it makes hosting simpler.</p>
<p>Once you have generated a static site you can upload the files to a web host and you&rsquo;re done.</p>
<p>And you can automate it, so all you do is update it and it gets deployed automatically.</p>
<h3 id="github-pages">GitHub pages</h3>
<p>I host copies of my code on GitHub so that others can view the source and I was planning on doing the same with my site.</p>
<p>This meant I could use one of GitHub&rsquo;s other features, which is <a href="https://pages.github.com/">free hosting for static content</a>
.</p>
<p>All I would need to do is add a <a href="https://github.com/paultibbetts/paultibbetts.uk/blob/a24aa42e17d0b8f059d9f12118fd69147b3fa12b/.github/workflows/hugo.yaml">workflow</a>
 for GitHub Actions to perform each time the code gets updated and the site gets deployed automatically.</p>
<h2 id="indiemark">IndieMark</h2>
<p>There&rsquo;s no official measure of a site&rsquo;s &ldquo;IndieWebness&rdquo; but the closest right now is the still-in-development <a href="https://indieweb.org/IndieMark">IndieMark</a>
 which would score me a level 1.</p>
<p>Level 0 involves owning your own domain, something I have <a href="https://paultibbetts.uk/2025/09/09/getting-my-own-domain/">written about before</a>
, and having a personal site at that domain.</p>
<p>Level 1 involves:</p>
<ul>
<li><strong>identity</strong>, I&rsquo;ll be using this at my primary domain</li>
<li><strong>authentication</strong> using <a href="https://indieweb.org/rel-me">rel-me</a>
 links to my external social network profiles</li>
<li><strong>posts</strong> with <strong>permalinks</strong>, <strong>h-entry</strong> markup and other <strong>microformats</strong></li>
<li><strong>searchable</strong> by <strong>allowing robots to index my site</strong>, my <strong>content is written in HTML</strong> and <strong>no JavaScript is required to read it</strong></li>
</ul>
<h2 id="view-source">View source</h2>
<p>You can <a href="https://github.com/paultibbetts/paultibbetts.uk">view the source code</a>
 to see how I&rsquo;ve abused Hugo and <a href="https://tailwindcss.com/">TailwindCSS</a>
 into creating my own site, hosted on GitHub Pages.</p>]]></content:encoded><source:markdown>
The second step to [getting on the IndieWeb](https://indieweb.org/Getting_Started) is to have your own site.

This is easier said than done, and there are lots of different ways of doing it.

This is what I did.

&lt;!--more--&gt;

## As a web developer

There are three paths to getting your own site.

### Service

You could use an existing service like [Micro.blog](https://micro.blog/) to host your site.

I already do this for my [microblog](https://micro.paultibbetts.uk/) because it comes with a bunch of features out of the box and gets me onto the IndieWeb, even while I don&#39;t yet support all the IndieWeb features on my main site.

### CMS

An alternative path is to use an existing content management system and add on IndieWeb features with plugins.

I&#39;ve done this in the past with [WordPress](https://wordpress.org/) but I moved on from the WordPress world a while ago.

### Self-starter

I decided I was more comfortable writing and doing it myself.

## What it needs to do

Before I wrote any code I made sure to cover the basics.

### Information about me

The homepage of my site needs to include a [h-card](https://indieweb.org/h-card) with my name, an icon, and [rel-me](https://indieweb.org/rel-me) links to my social network profiles.

This is not only useful for humans but I can also use it to sign in to other sites using [IndieAuth](https://indieweb.org/IndieAuth).

I used [IndieWebify.me](https://indiewebify.me/) to check I&#39;d done it correctly.

### Publish content

My posts should be marked up using [h-entry](https://indieweb.org/h-entry) so that others can understand my content.

The original site design had words with titles, which makes them technically &#34;articles&#34;, although that could change in the fture.

## How the site works

There are lots of different ways to do this.

In fact there are too many, so I kept it as simple as I could.

### Static site generator

I want to write my content in [Markdown](https://www.markdownguide.org/), I would prefer doing that on my laptop instead of my phone, and I&#39;m ok running commands to publish things.

Which means I can use a [static site generator](https://en.wikipedia.org/wiki/Static_site_generator) like [Hugo](https://gohugo.io) to turn my markdown files into HTML.

## Hosting

One of the best parts about using a static site generator is that it makes hosting simpler.

Once you have generated a static site you can upload the files to a web host and you&#39;re done.

And you can automate it, so all you do is update it and it gets deployed automatically.

### GitHub pages

I host copies of my code on GitHub so that others can view the source and I was planning on doing the same with my site.

This meant I could use one of GitHub&#39;s other features, which is [free hosting for static content](https://pages.github.com/).

All I would need to do is add a [workflow](https://github.com/paultibbetts/paultibbetts.uk/blob/a24aa42e17d0b8f059d9f12118fd69147b3fa12b/.github/workflows/hugo.yaml) for GitHub Actions to perform each time the code gets updated and the site gets deployed automatically.

## IndieMark

There&#39;s no official measure of a site&#39;s &#34;IndieWebness&#34; but the closest right now is the still-in-development [IndieMark](https://indieweb.org/IndieMark) which would score me a level 1.

Level 0 involves owning your own domain, something I have [written about before](https://paultibbetts.uk/2025/09/09/getting-my-own-domain/), and having a personal site at that domain.

Level 1 involves:

- **identity**, I&#39;ll be using this at my primary domain
- **authentication** using [rel-me](https://indieweb.org/rel-me) links to my external social network profiles
- **posts** with **permalinks**, **h-entry** markup and other **microformats**
- **searchable** by **allowing robots to index my site**, my **content is written in HTML** and **no JavaScript is required to read it**

## View source

You can [view the source code](https://github.com/paultibbetts/paultibbetts.uk) to see how I&#39;ve abused Hugo and [TailwindCSS](https://tailwindcss.com/) into creating my own site, hosted on GitHub Pages.
</source:markdown></item><item>
      <title>Getting My Own Domain</title>
      <link>https://paultibbetts.uk/2025/09/09/getting-my-own-domain/</link>
      <pubDate>Tue, 09 Sep 2025 15:53:46 +0100</pubDate>
      <guid>https://paultibbetts.uk/2025/09/09/getting-my-own-domain/</guid>
      <category>IndieWeb</category>
      <category>meta</category>
      <description>The first step to getting on the IndieWeb is to have your own domain.
I’ve already got one, so I thought I’d explain how I got it.</description>
      <content:encoded><![CDATA[<p>The first step to <a href="https://indieweb.org/Getting_Started">getting on the IndieWeb</a>
 is to have your own domain.</p>
<p>I&rsquo;ve already got one, so I thought I&rsquo;d explain how I got it.</p>
<h2 id="ruler">Ruler</h2>
<p>Years ago I registered my name as my domain.</p>
<p>I&rsquo;m not a company, so I didn&rsquo;t want <code>.com</code>, but there weren&rsquo;t many options, and so to make me &ldquo;Paul Tibbetts from the UK&rdquo; I went with <code>.co.uk</code>.</p>
<p>Some time later <code>.uk</code> was made available and to make it fair to the <code>.co.uk</code> owners who wanted to drop the <code>.co</code> you had to also own the <code>.co.uk</code> version to register it, so for a while I owned both.</p>
<p>This was all before the newer extensions like <code>.blog</code> and <code>.dev</code> came out. When they did I considered changing but decided against it.</p>
<h2 id="registrar">Registrar</h2>
<p>I registered my domain with <a href="https://www.heartinternet.uk/">Heart Internet</a>
 because that&rsquo;s who we used at work and I didn&rsquo;t have any kind of preference.</p>
<p>They don&rsquo;t expose my personal data when you run a <a href="https://www.whois.com/whois/paultibbetts.uk">whois query on the domain</a>
 so I haven&rsquo;t found a reason to move away from them.</p>
<p>Renewals are £9.99 per year.</p>
<h2 id="management">Management</h2>
<p>For a while I managed the domain using the interface on Heart Internet but since then I&rsquo;ve moved it to <a href="https://www.cloudflare.com/">Cloudflare</a>
.</p>
<p>To do this I changed the nameservers that the domain uses from Heart Internet&rsquo;s to Cloudflare&rsquo;s.</p>
<h2 id="records">Records</h2>
<p>There aren&rsquo;t that many records right now.</p>
<h3 id="heading">@</h3>
<p>The apex domain, as in the bare one without any subdomains (<code>https://paultibbetts.uk</code>), points to a really small landing page I made for myself.</p>
<p>I&rsquo;ll be redoing this soon so I won&rsquo;t talk about it yet.</p>
<h3 id="www">www</h3>
<p>I <strong>don&rsquo;t</strong> use the <code>www</code> subdomain.</p>
<p>I know there are people who think this is wrong but growing up sharing links with others the moment I discovered you could get rid of it I did and haven&rsquo;t looked back.</p>
<p>Maybe one day I will revisit this.</p>
<h3 id="micro">micro</h3>
<p><code>micro.paultibbetts.uk</code> is powered by <a href="https://micro.blog">Micro.blog</a>
.</p>
<p>I <em>could</em> run my main domain with Micro.blog but I want to have a go at doing that myself.</p>
<p>I followed <a href="https://help.micro.blog/t/custom-domain-names/53">the Micro.blog guide to set up a custom domain</a>
 and used a <code>CNAME</code> on my domain to point <code>micro</code> to <code>https://paultibbetts.micro.blog</code>.</p>
<h2 id="emails">Emails</h2>
<p>Once upon a time I hosted my own email server.</p>
<p>The company I worked at, Sixth Story, had an email address <code>iwanttowork @ sixthstory</code> that I thought was clever, so I wanted <code>hire @ paultibbetts</code> for myself. Applying for jobs as a web developer I thought it would help me stand out.</p>
<p>Even after all the work though I still found myself using my regular Apple email address because I knew it was more stable, and less likely to get marked as spam, so when Apple announced <a href="https://support.apple.com/en-us/102540">you can use custom domains with iCloud mail</a>
 I got rid of my email server and used Apple&rsquo;s instead.</p>
<p>This means I have some <code>MX</code> and <code>TXT</code> records to allow that to work.</p>
<h2 id="in-review">In review</h2>
<p>I have always been jealous of others with better domains than me.</p>
<h3 id="difficult-to-spell">Difficult to spell</h3>
<p>I have trouble getting people to spell my surname correctly.</p>
<p>I don&rsquo;t blame them, there&rsquo;s lots of Bs and Ts, and saying &ldquo;technically there&rsquo;s 3 Ts&rdquo; isn&rsquo;t helpful when they&rsquo;re typing the double T towards the end.</p>
<h4 id="potential-fix">Potential fix</h4>
<p>Aral&rsquo;s <code>ar.al</code> domain is much better than mine. It&rsquo;s short and easy to spell.</p>
<p>Maybe I could find a short domain and set it up to redirect?</p>
<p>Time for another disappointing trip to <a href="https://iwantmyname.com/">IWantMyName</a>
 to see all the good domains have been taken.</p>
<h3 id="did-you-mean-the-other-one">Did you mean the other one?</h3>
<p>I share a name with someone way more famous than me.</p>
<p>It&rsquo;s spelt a little different but search engines will assume you meant the other Paul.</p>
<h4 id="potential-fix-1">Potential fix</h4>
<p>There are a few ways I can improve my search engine rankings.</p>
<p>I&rsquo;m going to try writing lots of content to go on my domain, hoping that does it.</p>
<p>I will <strong>not</strong> do what the other guy did.</p>
<h3 id="dot-uk">dot UK</h3>
<p>My <code>.uk</code> address works whilst I live here but it wouldn&rsquo;t if I moved.</p>
<h4 id="potential-fix-2">Potential fix</h4>
<p>I don&rsquo;t have any immediate plans to move abroad so I&rsquo;m not too concerned with this.</p>
<p>If I ever did I can setup redirects.</p>
<h3 id="not-a-cool-internet-name">Not a cool internet name</h3>
<p>Jeremy Keith&rsquo;s <code>adactio.com</code> domain regularly reminds me I&rsquo;m not creative enough to come up with a cool internet name.</p>
<h4 id="potential-fix-3">Potential fix</h4>
<p>Maybe another decade of thinking about it will help.</p>
<h2 id="reposted">Reposted</h2>
<p>This was originally posted on my <a class="u-repost-of" href="https://micro.paultibbetts.uk/2025/01/02/getting-my-own-domain.html">microblog</a> before this site existed and I wanted a copy of it here.</p>]]></content:encoded><source:markdown>
The first step to [getting on the IndieWeb](https://indieweb.org/Getting_Started) is to have your own domain.

I&#39;ve already got one, so I thought I&#39;d explain how I got it.

&lt;!--more--&gt;

## Ruler

Years ago I registered my name as my domain.

I&#39;m not a company, so I didn&#39;t want `.com`, but there weren&#39;t many options, and so to make me &#34;Paul Tibbetts from the UK&#34; I went with `.co.uk`.

Some time later `.uk` was made available and to make it fair to the `.co.uk` owners who wanted to drop the `.co` you had to also own the `.co.uk` version to register it, so for a while I owned both.

This was all before the newer extensions like `.blog` and `.dev` came out. When they did I considered changing but decided against it.

## Registrar

I registered my domain with [Heart Internet](https://www.heartinternet.uk/) because that&#39;s who we used at work and I didn&#39;t have any kind of preference.

They don&#39;t expose my personal data when you run a [whois query on the domain](https://www.whois.com/whois/paultibbetts.uk) so I haven&#39;t found a reason to move away from them.

Renewals are £9.99 per year.

## Management

For a while I managed the domain using the interface on Heart Internet but since then I&#39;ve moved it to [Cloudflare](https://www.cloudflare.com/).

To do this I changed the nameservers that the domain uses from Heart Internet&#39;s to Cloudflare&#39;s.

## Records

There aren&#39;t that many records right now.

### @

The apex domain, as in the bare one without any subdomains (`https://paultibbetts.uk`), points to a really small landing page I made for myself.

I&#39;ll be redoing this soon so I won&#39;t talk about it yet.

### www

I **don&#39;t** use the `www` subdomain.

I know there are people who think this is wrong but growing up sharing links with others the moment I discovered you could get rid of it I did and haven&#39;t looked back.

Maybe one day I will revisit this.

### micro

`micro.paultibbetts.uk` is powered by [Micro.blog](https://micro.blog).

I _could_ run my main domain with Micro.blog but I want to have a go at doing that myself.

I followed [the Micro.blog guide to set up a custom domain](https://help.micro.blog/t/custom-domain-names/53) and used a `CNAME` on my domain to point `micro` to `https://paultibbetts.micro.blog`.

## Emails

Once upon a time I hosted my own email server.

The company I worked at, Sixth Story, had an email address `iwanttowork @ sixthstory` that I thought was clever, so I wanted `hire @ paultibbetts` for myself. Applying for jobs as a web developer I thought it would help me stand out.

Even after all the work though I still found myself using my regular Apple email address because I knew it was more stable, and less likely to get marked as spam, so when Apple announced [you can use custom domains with iCloud mail](https://support.apple.com/en-us/102540) I got rid of my email server and used Apple&#39;s instead.

This means I have some `MX` and `TXT` records to allow that to work.

## In review

I have always been jealous of others with better domains than me.

### Difficult to spell

I have trouble getting people to spell my surname correctly.

I don&#39;t blame them, there&#39;s lots of Bs and Ts, and saying &#34;technically there&#39;s 3 Ts&#34; isn&#39;t helpful when they&#39;re typing the double T towards the end.

#### Potential fix

Aral&#39;s `ar.al` domain is much better than mine. It&#39;s short and easy to spell.

Maybe I could find a short domain and set it up to redirect?

Time for another disappointing trip to [IWantMyName](https://iwantmyname.com/) to see all the good domains have been taken.

### Did you mean the other one?

I share a name with someone way more famous than me.

It&#39;s spelt a little different but search engines will assume you meant the other Paul.

#### Potential fix

There are a few ways I can improve my search engine rankings.

I&#39;m going to try writing lots of content to go on my domain, hoping that does it.

I will **not** do what the other guy did.

### dot UK

My `.uk` address works whilst I live here but it wouldn&#39;t if I moved.

#### Potential fix

I don&#39;t have any immediate plans to move abroad so I&#39;m not too concerned with this.

If I ever did I can setup redirects.

### Not a cool internet name

Jeremy Keith&#39;s `adactio.com` domain regularly reminds me I&#39;m not creative enough to come up with a cool internet name.

#### Potential fix

Maybe another decade of thinking about it will help.

## Reposted

This was originally posted on my &lt;a class=&#34;u-repost-of&#34; href=&#34;https://micro.paultibbetts.uk/2025/01/02/getting-my-own-domain.html&#34;&gt;microblog&lt;/a&gt; before this site existed and I wanted a copy of it here.
</source:markdown></item><item>
      <title>IndieWeb: Why</title>
      <link>https://paultibbetts.uk/2025/09/09/indieweb-why/</link>
      <pubDate>Tue, 09 Sep 2025 15:50:00 +0100</pubDate>
      <guid>https://paultibbetts.uk/2025/09/09/indieweb-why/</guid>
      <category>IndieWeb</category>
      <description>The IndieWeb is a people-focused alternative to the “corporate web”.
I’ve been a believer for over a decade.
Here’s why.</description>
      <content:encoded><![CDATA[<p>The <a href="https://indieweb.org/">IndieWeb</a>
 is a people-focused alternative to the &ldquo;corporate web&rdquo;.</p>
<p>I&rsquo;ve been a believer for over a decade.</p>
<p>Here&rsquo;s why.</p>
<h2 id="i-own-my-data">I own my data</h2>
<p>I used to use the social networks. They&rsquo;d make money from me being there, and that was my price of admission. Everybody did it. It was normal.</p>
<p>Except it isn&rsquo;t normal, and it shouldn&rsquo;t be thought of as normal.</p>
<p>We gave up our ownership for ease of use, and I think that&rsquo;s wrong.</p>
<p>The IndieWeb puts content ownership first.</p>
<h2 id="i-am-better-connected">I am better connected</h2>
<p>Since Musk bought Twitter I haven&rsquo;t been able to view any tweets on my phone. It complains about me using an adblocker and refuses to load the page, even though I&rsquo;m not using one.</p>
<p>I left Instagram before they stopped letting you include links in your posts.</p>
<p>And I&rsquo;ve ran out of free Medium articles to read this month, so I can&rsquo;t read your latest post on that platform.</p>
<p>But I&rsquo;ve never had a problem using other people&rsquo;s personal sites.</p>
<p>Everyone else being on the IndieWeb helps me, so I do the same for them.</p>
<h2 id="i-am-in-control">I am in control</h2>
<p>On the IndieWeb it&rsquo;s up to me to choose how I&rsquo;m represented online and what gets made available.</p>
<p>Which is how the web should be.</p>
<h2 id="i-want-the-web-to-be-more-open">I want the web to be more open</h2>
<p>The web was built on openness. Anyone could publish a page and send it to others.</p>
<p>Since then it&rsquo;s consolidated into a handful of platforms that dictate how things happen and how posts get seen, if they get seen at all.</p>
<p>Which means the IndieWeb is more than having your own site, it&rsquo;s a movement, to restore the web&rsquo;s original promise: to be a network that connects people.</p>
<h2 id="if-you-agree">If you agree</h2>
<p><a href="https://indieweb.org/Getting_Started">Here&rsquo;s how you can join in</a>
.</p>]]></content:encoded><source:markdown>
The [IndieWeb](https://indieweb.org/) is a people-focused alternative to the &#34;corporate web&#34;.

I&#39;ve been a believer for over a decade.

Here&#39;s why.

&lt;!--more--&gt;

## I own my data

I used to use the social networks. They&#39;d make money from me being there, and that was my price of admission. Everybody did it. It was normal.

Except it isn&#39;t normal, and it shouldn&#39;t be thought of as normal.

We gave up our ownership for ease of use, and I think that&#39;s wrong.

The IndieWeb puts content ownership first.

## I am better connected

Since Musk bought Twitter I haven&#39;t been able to view any tweets on my phone. It complains about me using an adblocker and refuses to load the page, even though I&#39;m not using one.

I left Instagram before they stopped letting you include links in your posts.

And I&#39;ve ran out of free Medium articles to read this month, so I can&#39;t read your latest post on that platform.

But I&#39;ve never had a problem using other people&#39;s personal sites.

Everyone else being on the IndieWeb helps me, so I do the same for them.

## I am in control

On the IndieWeb it&#39;s up to me to choose how I&#39;m represented online and what gets made available.

Which is how the web should be.

## I want the web to be more open

The web was built on openness. Anyone could publish a page and send it to others.

Since then it&#39;s consolidated into a handful of platforms that dictate how things happen and how posts get seen, if they get seen at all.

Which means the IndieWeb is more than having your own site, it&#39;s a movement, to restore the web&#39;s original promise: to be a network that connects people.

## If you agree

[Here&#39;s how you can join in](https://indieweb.org/Getting_Started).
</source:markdown></item>
  </channel>
</rss>
