paritybit.ca

Unnamed repository; edit this file 'description' to name the repository.
Log | Files | Refs | README | LICENSE

commit 2e44f91d44ce989c9d5023d963276f15c6be8962
parent f1dabd4ba43899cf276603eca84c996c1fcf9766
Author: Jake Bauer <jbauer@paritybit.ca>
Date:   Thu, 23 Jul 2020 12:14:35 -0400

Publish new blog post

Diffstat:
Mpages/blog.md | 1+
Mpages/blog/mastodon-to-pleroma-2-customizing-my-instance.md | 58+++++++++++++++++++++++++++++++++-------------------------
Mpages/home.md | 4++--
Mpublic/feeds/sitewide-feed.xml | 33+++++++++++++++++++++++++++++++++
Apublic/img/logo-pleroma-128.png | 0
Apublic/img/logo-pleroma-32.png | 0
Apublic/img/logo-pleroma-512.png | 0
Mpublic/sitemap.xml | 1+
8 files changed, 70 insertions(+), 27 deletions(-)

diff --git a/pages/blog.md b/pages/blog.md @@ -27,6 +27,7 @@ href="https://pleroma.paritybit.ca/jbauer">Pleroma</a>. ### 2020 <ul> + <li>2020-07-23 <a href="blog/mastodon-to-pleroma-2-customizing-my-instance">Mastodon to Pleroma — 2 — Customizing My Instance</a></li> <li>2020-07-21 <a href="blog/mastodon-to-pleroma-1-setting-up-a-pleroma-server">Mastodon to Pleroma — 1 — Setting up a Pleroma Server</a></li> <li>2020-07-19 <a href="blog/two-months-with-aerc">Two Months with aerc</a></li> <li>2020-07-17 <a href="blog/my-attempts-to-fix-my-mastodon-instance">My Attempts to Fix My Mastodon Instance</a></li> diff --git a/pages/blog/mastodon-to-pleroma-2-customizing-my-instance.md b/pages/blog/mastodon-to-pleroma-2-customizing-my-instance.md @@ -8,42 +8,47 @@ <div class="byline"> <b>Written By:</b> Jake Bauer | - <b>Posted:</b> [DATE] | - <b>Last Updated:</b> [DATE] + <b>Posted:</b> 2020-07-23 | + <b>Last Updated:</b> 2020-07-23 </div> +<p class="note">Since this is a Mastodon to Pleroma conversion, followers will +not auto-migrate. You should [follow me on Pleroma +here](https://pleroma.paritybit.ca/jbauer) and unfollow me on Mastodon.</p> + Now that I have a Pleroma instance up and running with an account, it's time to make that instance my own through backend and frontend customizations. Pleroma provides so many customization options, it took me a while to go through all of them and customize my instance to my liking. That is by no means a bad -thing; it was a really enjoyable process and it feels like it's social media but -for hackers (not the Hollywood kind). +thing; it was a really enjoyable process and it makes it feel like it's social +media but for hackers (not the Hollywood kind). There weren't many backend customizations I wanted to do. For one, the default -character limit of 5000 is more than enough for me, and far less -restrictive-feeling than Mastodon's unchangeable 500. I turned off the chat room -(which I think is a really cool feature) and closed registrations because I -didn't need those features on a single-person instance. I was pretty satisfied -with pretty much everything and found it really cool to see an option for -[exposing my instance over +character limit of 5000 is more than enough for me, and far less restrictive +feeling than Mastodon's unchangeable 500. I turned off the chat room (which I do +think is a really cool feature) and closed registrations because I didn't need +those features on my single-person instance. I was pretty much satisfied with +the rest of the defaults. I want to point out that I found it really cool to see +an option for [exposing my instance over Tor](https://docs.pleroma.social/backend/configuration/onion_federation/) as a hidden service as well as an option to expose my instance over the Gopher -protocol. +protocol. That's rare to see for a web application, and really makes me like +Pleroma a lot more (even if I don't end up using those features). As far as customizing the frontend, well, this is where it got fun and interesting. I could change pretty much anything I wanted about the instance's frontend down to the UI itself (though I stuck with the default Pleroma frontend because I actually quite like it). I changed the favicon of the site (something -I couldn't do with Mastodon), the background for the entire instance, the logo -for the site as it appears at the top-center of the page, and even the default -theme for the UI. +I couldn't do at all with Mastodon), the background for the entire instance, the +logo for the site as it appears at the top-center of the page, and even the +default theme for the UI. I created a new logo for my Pleroma instance just like I did with my Mastodon instance: <figure> - <a href="/img/logo-pleroma-128.png"><img src="/img/logo-pleroma-512.png" + <a href="/img/logo-pleroma-512.png"><img src="/img/logo-pleroma-128.png" alt="My Pleroma instance's logo: A black circle around a dark red circle all encircling a yellow circle which has a black coloured Pleroma logo in the centre."/></a> @@ -51,20 +56,23 @@ instance: I also set the background of both my profile and my Pleroma instance to a 1 pixel by 1 pixel solid colour image. I liked the background colour that I used -for my profile banner on Mastodon, and wanted to keep it for this new instance. +for my profile banner on Mastodon and wanted to keep it for this new instance. The colour is: <span style="colour:#fff;background-color:#282c37">#282c37</span>, in case you're curious. -Finally, for the theme, I landed on the Vulpes One theme created by -@Feuerfuchs@fedi.vulpes.one which I found via -[plthemes.vulpes.one](https://plthemes.vulpes.one/), and added it to my instance -by once again following the [Pleroma documentation on adding +Finally, for the theme, I landed on the Vulpes One theme created by <a +href="https://pleroma.paritybit.ca/users/9xJeso1U3l4rBr2o4W">@Feuerfuchs@fedi.vulpes.one</a> +which I found via [plthemes.vulpes.one](https://plthemes.vulpes.one/), and added +it to my instance by following the [Pleroma documentation on adding themes](https://docs-develop.pleroma.social/backend/configuration/howto_theming_your_instance/). +I think it's a great theme that complements the colour scheme I went for well. As far as emoji packs, just like with Mastodon one can also add custom emoji to Pleroma instances. I'm not a big user of emoji though, so I didn't really bother -for my instance. +for my instance. I will say, though, that I really like the old [blob +emoji](https://en.wikipedia.org/wiki/Blob_emoji) and I think the blobcats are +really cute. Except for profile-specific settings, all of the above customizations were accomplished by putting files into the "static directory", a place the Pleroma @@ -79,10 +87,10 @@ instance-specific panel, and updating the About page for the instance. The more I use Pleroma, the more I like it. It allows me to customize so much that I can truly make an instance feel like my own rather than yet another -Mastodon instance. The plethora of tunables and customizables from things like -the number of options once can add to a poll to even being able to turn off -federation all-together, really make it feel like the hacker's version of -Mastodon. +instance using the same software. The plethora of tunables and customizables +from things like the number of options one can add to a poll to even being able +to turn off federation all-together, really make it feel like the hacker's +version of Mastodon. _Disclaimer: I am in no way trying to disparage the effort's of the Mastodon folk, I just really like Pleroma and I am realizing it's the better choice for diff --git a/pages/home.md b/pages/home.md @@ -18,6 +18,8 @@ This site will soon™️ be available over Gopher and Gemini. <a class="rss-icon" href="/feeds/sitewide-feed.xml"> <img src="/img/feed-icon.png" width="15" height="15" alt="Click for RSS Feed"/> </a> </div> +2020-07-23 <a class="feed-item" href="blog/mastodon-to-pleroma-2-customizing-my-instance">Mastodon to Pleroma — 2 — Customizing My Instance</a> + 2020-07-21 <a class="feed-item" href="blog/mastodon-to-pleroma-1-setting-up-a-pleroma-server">Mastodon to Pleroma — 1 — Setting up a Pleroma Server</a> 2020-07-19 <a class="feed-item" href="blog/two-months-with-aerc">Two Months with aerc</a> @@ -36,8 +38,6 @@ This site will soon™️ be available over Gopher and Gemini. 2020-07-12 <a class="feed-item" href="blog/new-server-checklist">New Server Checklist</a> -2020-07-12 <a class="feed-item" href="blog/machine-hostnames">Machine Hostnames</a> - ### What is a Parity Bit? It is a bit (in the 1's and 0's sense) used in checking for errors in digital diff --git a/public/feeds/sitewide-feed.xml b/public/feeds/sitewide-feed.xml @@ -7,6 +7,39 @@ <description>The feed that covers all notable additions, updates, announcements, and other changes for the entire paritybit.ca website.</description> <item> + <title>Mastodon to Pleroma — 2 — Customizing My Instance</title> + <link>https://www.paritybit.ca/blog/mastodon-to-pleroma-2-customizing-my-instance</link> + <guid>https://www.paritybit.ca/blog/mastodon-to-pleroma-2-customizing-my-instance</guid> + <pubDate>Thu, 23 Jul 2020 00:42:21 -0400</pubDate> + <description><![CDATA[<h2 id="mastodon-to-pleroma-2-customizing-my-instance">Mastodon to Pleroma — 2 — Customizing My Instance</h2> +<div class="byline"> +<p><b>Written By:</b> Jake Bauer | <b>Posted:</b> 2020-07-23 | <b>Last Updated:</b> 2020-07-23</p> +</div> +<p class="note"> +Since this is a Mastodon to Pleroma conversion, followers will not auto-migrate. You should <a href="https://pleroma.paritybit.ca/jbauer">follow me on Pleroma here</a> and unfollow me on Mastodon. +</p> +<p>Now that I have a Pleroma instance up and running with an account, it’s time to make that instance my own through backend and frontend customizations.</p> +<p>Pleroma provides so many customization options, it took me a while to go through all of them and customize my instance to my liking. That is by no means a bad thing; it was a really enjoyable process and it feels like it’s social media but for hackers (not the Hollywood kind).</p> +<p>There weren’t many backend customizations I wanted to do. For one, the default character limit of 5000 is more than enough for me, and far less restrictive feeling than Mastodon’s unchangeable 500. I turned off the chat room (which I do think is a really cool feature) and closed registrations because I didn’t need those features on my single-person instance. I was pretty much satisfied with the rest of the defaults. I want to point out that I found it really cool to see an option for <a href="https://docs.pleroma.social/backend/configuration/onion_federation/">exposing my instance over Tor</a> as a hidden service as well as an option to expose my instance over the Gopher protocol. That’s rare to see for a web application, and really makes me like Pleroma a lot more (even if I don’t end up using those features).</p> +<p>As far as customizing the frontend, well, this is where it got fun and interesting. I could change pretty much anything I wanted about the instance’s frontend down to the UI itself (though I stuck with the default Pleroma frontend because I actually quite like it). I changed the favicon of the site (something I couldn’t do at all with Mastodon), the background for the entire instance, the logo for the site as it appears at the top-center of the page, and even the default theme for the UI.</p> +<p>I created a new logo for my Pleroma instance just like I did with my Mastodon instance:</p> +<figure> +<a href="/img/logo-pleroma-512.png"><img src="/img/logo-pleroma-128.png" + alt="My Pleroma instance's logo: A black circle around a dark red circle all + encircling a yellow circle which has a black coloured Pleroma logo in the + centre."/></a> +</figure> +<p>I also set the background of both my profile and my Pleroma instance to a 1 pixel by 1 pixel solid colour image. I liked the background colour that I used for my profile banner on Mastodon and wanted to keep it for this new instance. The colour is: <span style="colour:#fff;background-color:#282c37">#282c37</span>, in case you’re curious.</p> +<p>Finally, for the theme, I landed on the Vulpes One theme created by <a +href="https://pleroma.paritybit.ca/users/9xJeso1U3l4rBr2o4W"><span class="citation" data-cites="Feuerfuchs">@Feuerfuchs</span><span class="citation" data-cites="fedi.vulpes.one">@fedi.vulpes.one</span></a> which I found via <a href="https://plthemes.vulpes.one/">plthemes.vulpes.one</a>, and added it to my instance by once again following the <a href="https://docs-develop.pleroma.social/backend/configuration/howto_theming_your_instance/">Pleroma documentation on adding themes</a>. I think it’s a great theme that complements the colour scheme I went for well.</p> +<p>As far as emoji packs, just like with Mastodon one can also add custom emoji to Pleroma instances. I’m not a big user of emoji though, so I didn’t really bother for my instance. I will say I really like the old <a href="https://en.wikipedia.org/wiki/Blob_emoji">blob emoji</a> and I think the blobcats are really cute.</p> +<p>Except for profile-specific settings, all of the above customizations were accomplished by putting files into the “static directory”, a place the Pleroma server looks to serve custom resources. I set mine at <code>/var/lib/pleroma/static</code> because that’s what the installation instructions used and I didn’t have a reason to change it.</p> +<p>Some other minor changes I made were: setting the default page to show non-logged-in users (i.e. anyone who isn’t me but is visiting pleroma.paritybit.ca in their browser) my profile page, turned off showing the instance-specific panel, and updating the About page for the instance.</p> +<p>The more I use Pleroma, the more I like it. It allows me to customize so much that I can truly make an instance feel like my own rather than yet another Mastodon instance. The plethora of tunables and customizables from things like the number of options once can add to a poll to even being able to turn off federation all-together, really make it feel like the hacker’s version of Mastodon.</p> +<p><em>Disclaimer: I am in no way trying to disparage the effort’s of the Mastodon folk, I just really like Pleroma and I am realizing it’s the better choice for me.</em></p> +<p><em>This is my seventy-seventh post for the <a href="https://social.paritybit.ca/tags/100DaysToOffload">#100DaysToOffload</a> challenge. You can learn more about this challenge over at <a href="https://100daystooffload.com">https://100daystooffload.com</a>.</em></p>]]></description> + </item> +<item> <title>Mastodon to Pleroma — 1 — Setting up a Pleroma Server</title> <link>https://www.paritybit.ca/blog/mastodon-to-pleroma-1-setting-up-a-pleroma-server</link> <guid>https://www.paritybit.ca/blog/mastodon-to-pleroma-1-setting-up-a-pleroma-server</guid> diff --git a/public/img/logo-pleroma-128.png b/public/img/logo-pleroma-128.png Binary files differ. diff --git a/public/img/logo-pleroma-32.png b/public/img/logo-pleroma-32.png Binary files differ. diff --git a/public/img/logo-pleroma-512.png b/public/img/logo-pleroma-512.png Binary files differ. diff --git a/public/sitemap.xml b/public/sitemap.xml @@ -3,6 +3,7 @@ <url><loc>https://www.paritybit.ca</loc></url> <url><loc>https://www.paritybit.ca/home</loc></url> <url><loc>https://www.paritybit.ca/blog</loc></url> + <url><loc>https://www.paritybit.ca/blog/mastodon-to-pleroma-2-customizing-my-instance</loc></url> <url><loc>https://www.paritybit.ca/blog/mastodon-to-pleroma-1-setting-up-a-pleroma-server</loc></url> <url><loc>https://www.paritybit.ca/blog/two-months-with-aerc</loc></url> <url><loc>https://www.paritybit.ca/blog/my-attempts-to-fix-my-mastodon-instance</loc></url>