Pleroma is a social networking software written in Erlang for federated communication. It's lightweight design makes it suitable for low resource environments such as Raspberry Pi increasing the number of nodes. Rather than participating on centralized microblogging platforms in a filter bubble, you may set up a self-hosted server using this guide or register at a public server and reach out via my fediverse handle:

@this@ven.uber.space

Refer to official documentation such as Installing on Arch Linux and the Pleroma — UberLab 7 documentation or use a platform specific guide, e.g. for Pleroma Hosting on Raspberry Pi

There's a cheat sheet for overview as well as a commented sample config available.

I recommend setting up Multi-factor authentication in Security section of Settings and considering further hardening.

Although there's a setting for disabling public access to the local timeline and known network, you might want to fine-tune some details. This is why several values for restrict_unauthenticated can be adapted. In order to show local content, but prevent unauthenticated users from accessing remote activites, profiles and timelines use the following configuration:

config :pleroma, :restrict_unauthenticated,
  timelines: %{local: false, federated: true},
  profiles: %{local: false, remote: true},
  activities: %{local: false, remote: true}

Note: To make these settings effective, :public: true must be set in config :pleroma, :instance.

Branding can be done via adding files in static directory and adding values for pleroma_fe: in the configuration.

For logging e.g. only critical messages change the value of your logger level to e.g. config :logger, :console, level: :critical.

Category: Services