<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Automattic on Melabit</title>
    <link>https://static.233.196.69.159.clients.your-server.de/en/tags/automattic/</link>
    <description>Recent content in Automattic on Melabit</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Thu, 02 Jan 2025 06:00:00 +0000</lastBuildDate>
    <atom:link href="https://static.233.196.69.159.clients.your-server.de/en/tags/automattic/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>From melabit to melabit: goodbye WordPress, hello Jekyll</title>
      <link>https://static.233.196.69.159.clients.your-server.de/en/2025/01/02/from-melabit-to-melabit-goodbye-wordpress-hello-jekyll/</link>
      <pubDate>Thu, 02 Jan 2025 06:00:00 +0000</pubDate>
      <guid>https://static.233.196.69.159.clients.your-server.de/en/2025/01/02/from-melabit-to-melabit-goodbye-wordpress-hello-jekyll/</guid>
      <description>&lt;p&gt;&lt;img src=&#34;https://static.233.196.69.159.clients.your-server.de/img/2025-01-02-da-melabit-a-melabit-addio-wordpress-ciao-jekyll/phoenix.jpeg&#34; alt=&#34;&#34;&gt;&#xA;&amp;ndash; &lt;em&gt;Image generated by the &lt;a href=&#34;https://designer.microsoft.com/image-creator&#34;&gt;Microsoft Designer&lt;/a&gt; AI.&lt;/em&gt;&lt;/p&gt;&#xA;&lt;p&gt;Eleven years ago, when I started writing in this personal space, I never imagined I would stick with &lt;a href=&#34;https://wordpress.com/&#34;&gt;WordPress.com&lt;/a&gt; for so long. WordPress.com is a convenient and reliable blogging platform, but it has always been &lt;a href=&#34;https://melabit.com/en/2014/08/01/i-limiti-di-wordpress-com/&#34;&gt;ill-suited to my way of working&lt;/a&gt;. Over time, I learned to live with these limitations, but the idea of changing platforms never left my mind.&lt;/p&gt;&#xA;&lt;p&gt;From the start, I had a clear idea of &lt;a href=&#34;https://melabit.com/en/2014/12/31/and-the-winner-is/&#34;&gt;which alternative platform&lt;/a&gt; I wanted to use. A few years later, I revisited the available options and detailed the steps to transition in a &lt;a href=&#34;https://melabit.wordpress.com/2018/04/16/da-melabit-a-melabit-introduzione/&#34;&gt;long series of posts&lt;/a&gt;. Ultimately, though, I didn’t follow through, perhaps because I wasn’t fully convinced about the decision.&lt;/p&gt;&#xA;&lt;p&gt;After all, leaving the comfort zone of a platform that has caused you zero problems over the years to embark on a new journey where you manage everything yourself is no small task.&lt;/p&gt;&#xA;&lt;hr style = &#34;border: none; &#xA;            border-top: 3px double #333; &#xA;            color: #333; &#xA;            overflow: visible; &#xA;            height: 5px; &#xA;            width: 50%; &#xA;            margin-left: auto; &#xA;            margin-right: auto;&#34;&#xA;&gt;&#xA;&#xA;&lt;p&gt;A few months ago, however, &lt;a href=&#34;https://automattic.com/&#34;&gt;Automattic&lt;/a&gt;, the company behind the open-source &lt;a href=&#34;https://wordpress.org/&#34;&gt;WordPress&lt;/a&gt; software and its related products, decided to &lt;a href=&#34;https://www.engadget.com/tumblr-and-wordpress-posts-will-reportedly-be-used-for-openai-and-midjourney-training-204425798.html&#34;&gt;share by default&lt;/a&gt; all content hosted on WordPress.com with &amp;ldquo;third parties.&amp;rdquo; Actually, this means sharing it with AI-powered text generators (think ChatGPT and similar tools) that are constantly hungry for new material to improve their training.&lt;sup id=&#34;fnref:1&#34;&gt;&lt;a href=&#34;#fn:1&#34; class=&#34;footnote-ref&#34; role=&#34;doc-noteref&#34;&gt;1&lt;/a&gt;&lt;/sup&gt; In that moment, my decision was made.&lt;/p&gt;&#xA;&lt;p&gt;As if that weren’t enough, shortly after, Matt Mullenweg, WordPress’s founder, &lt;a href=&#34;https://joshcollinsworth.com/blog/fire-matt&#34;&gt;lost his temper&lt;/a&gt;, highlighting how, despite WordPress being the world’s most popular open-source content management system (CMS), the increasingly centralized and authoritarian control over its development threatens the platform’s open and transparent future.&lt;/p&gt;&#xA;&lt;hr style = &#34;border: none; &#xA;            border-top: 3px double #333; &#xA;            color: #333; &#xA;            overflow: visible; &#xA;            height: 5px; &#xA;            width: 50%; &#xA;            margin-left: auto; &#xA;            margin-right: auto;&#34;&#xA;&gt;&#xA;&#xA;&lt;p&gt;And so, the die is cast! It took a lot of time and effort, but starting today, this little blog has its own home: &lt;a href=&#34;https://melabit.com/en/&#34;&gt;melabit.com/posts/en&lt;/a&gt;, where I can experiment with much greater freedom than before. Let’s see how it goes.&lt;/p&gt;&#xA;&lt;p&gt;The &lt;a href=&#34;https://melabit.com/posts/en&#34;&gt;new site&lt;/a&gt; is still a work in progress. The basic structure is in place, but there will definitely be adjustments and improvements in the coming months. The very first thing to do is to expand the international section, which currently contains only a handful of posts, with several broken links or links to the original posts in italian. Additionally, I would like to implement a system for notifying users of new posts.&lt;/p&gt;&#xA;&lt;p&gt;In the meantime, please don’t hesitate to flag any issues or poorly functioning elements in the comments.&lt;/p&gt;&#xA;&lt;p&gt;For technical details and the transition process, stay tuned for upcoming posts.&lt;/p&gt;&#xA;&lt;p&gt;Rest assured that all old content and comments will remain available on &lt;a href=&#34;https://melabit.wordpress.com/&#34;&gt;melabit.wordpress.com&lt;/a&gt;. At least until Mullenweg kicks me out&amp;hellip; 🤣🤣🤣🤣🤣&lt;/p&gt;&#xA;&lt;div class=&#34;footnotes&#34; role=&#34;doc-endnotes&#34;&gt;&#xA;&lt;hr&gt;&#xA;&lt;ol&gt;&#xA;&lt;li id=&#34;fn:1&#34;&gt;&#xA;&lt;p&gt;While it is true you can opt out of sharing your content—and I did—it’s also true that you must explicitly choose &lt;strong&gt;not to share&lt;/strong&gt; your data, rather than the other way around, which would be more logical. And even then, there’s no guarantee that your content won’t be scraped anyway.&amp;#160;&lt;a href=&#34;#fnref:1&#34; class=&#34;footnote-backref&#34; role=&#34;doc-backlink&#34;&gt;&amp;#x21a9;&amp;#xfe0e;&lt;/a&gt;&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ol&gt;&#xA;&lt;/div&gt;&#xA;</description>
    </item>
  </channel>
</rss>
