paritybit.ca

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

commit 99b75e4f76916dd6f51174ca57d191da9a2b036f
parent bf9095562f1b5590ed0804d14d8a35b7dc050cac
Author: Jake Bauer <jbauer@paritybit.ca>
Date:   Wed, 22 Jul 2020 23:39:50 -0400

Fix issues in first m-p blog post

Diffstat:
Mpages/blog/mastodon-to-pleroma-1-setting-up-a-pleroma-server.md | 7++++---
1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/pages/blog/mastodon-to-pleroma-1-setting-up-a-pleroma-server.md b/pages/blog/mastodon-to-pleroma-1-setting-up-a-pleroma-server.md @@ -53,9 +53,10 @@ the number of settings you can change on your server give a sense of having a lot more freedom in making an instance _your instance_. For example, through adding resources to a customizations directory called the "static directory", I am able to add custom themes to the frontend that ships with Pleroma, and change -the background, favicon, and logo site-wide (as opposed to just for my profile). -One can also use different frontends with Pleroma; it notably ships with a -version of the Mastodon frontend in addition to the default Pleroma frontend. +the background, favicon, and logo site-wide (as opposed to just my profile +background and avatar). One can also use different frontends with Pleroma; it +notably ships with a version of the Mastodon frontend in addition to the default +Pleroma frontend. So, now that you know why I wanted to switch to Pleroma, let's look at installing a server: