There are multiple frontends to use with Pleroma to suit all kinds user preferences: Pleroma FE, our 'official' highly customizable frontend. Soapbox, a simple easy to learn and use alternative. Glitch-lily, a Pleroma focused fork of Mastodon 's multi column frontend, forked from Glitch Social.

Apr 2, 2025 · Pleroma 2.1.1 is a security release, fixing 2 DoS vulnerabilities, metadata leak on private instances, a possible OOM with the default HTTP client and bugs found after 2.1.0 release.

Mar 1, 2025 · Release: Pleroma 2.7.1 ### Changed - Accept `application/activity+json` for requests to `/.well-known/nodeinfo` ### Fixed - Truncate remote user fields, avoids them …

Home Quick Navigation Pleroma Clients Installing on Linux using OTP releases Configuration Cheat Sheet Pleroma-FE configuration and customization for instance administrators Community Channels IRC: #pleroma and #pleroma-dev on libera.chat, webchat is available at https://irc.pleroma.social Matrix: #pleroma:libera.chat and #pleroma-dev:libera.chat

Pleroma is a federated social networking platform, compatible with Mastodon and other ActivityPub implementations. It is free software licensed under the AGPLv3.

If you want to open your newly installed instance to the world, you should run nginx or some other webserver/proxy in front of Pleroma and you should consider to create a systemd service file for Pleroma.

This works very simple - custom emoji is defined by its shortcode and an image, so that any shortcode enclosed in colons get replaced with image if such shortcode exist. Let's say there's a :pleroma: emoji defined on an instance. That means First time using :pleroma: pleroma! will become First time using pleroma!

Due to high memory usage, it may be best to set it up on a different machine, if running pleroma on a low-resource computer, and use private key authentication to secure the remote search instance. To use meilisearch, set the search module to Pleroma.Search.Meilisearch: config :pleroma, Pleroma.Search, module: Pleroma.Search.Meilisearch

Pleroma does not store remote/federated media by default. The best way to achieve this is to change Nginx to keep its reverse proxy cache for a year and to activate the MediaProxyWarmingPolicy MRF policy in Pleroma which will automatically fetch all media through the proxy as soon as the post is received by your instance.

Every command should be ran as the pleroma user from it's home directory. For example if you are superuser, you would have to wrap the command in su pleroma -s $SHELL -lc "$COMMAND".