pleroma

Fork of Pleroma with site-specific changes and feature branches https://git.pleroma.social/pleroma/pleroma

rinpatch 2c55f7d7cb Remove FedSockets Current FedSocket implementation has a bunch of problems. It doesn't have proper error handling (in case of an error the server just doesn't respond until the connection is closed, while the client doesn't match any error messages and just assumes there has been an error after 15s) and the code is full of bad descisions (see: fetch registry which uses uuids for no reason and waits for a response by recursively querying a ets table until the value changes, or double JSON encoding). Sometime ago I almost completed rewriting fedsockets from scrach to adress these issues. However, while doing so, I realized that fedsockets are just too overkill for what they were trying to accomplish, which is reduce the overhead of federation by not signing every message. This could be done without reimplementing failure states and endpoint logic we already have with HTTP by, for example, using TLS cert auth, or switching to a more performant signature algorithm. I opened https://git.pleroma.social/pleroma/pleroma/-/issues/2262 for further discussion on alternatives to fedsockets. From discussions I had with other Pleroma developers it seems like they would approve the descision to remove them as well, therefore I am submitting this patch.		vor 3 Jahren
.gitlab	release MR template: add a note about merging stable changes back to	vor 3 Jahren
benchmarks	adding benchmarks in new format	vor 3 Jahren
config	Remove FedSockets	vor 3 Jahren
docs	Remove FedSockets	vor 3 Jahren
installation	Remove FedSockets	vor 3 Jahren
lib	Remove FedSockets	vor 3 Jahren
priv	Merge branch 'sync-stable/2.2.0' into 'develop'	vor 3 Jahren
rel	OTP releases: only set name and distribution type if not set already	vor 4 Jahren
restarter	Merge branch 'develop' into gun	vor 4 Jahren
test	Remove FedSockets	vor 3 Jahren
uploads	fix issues with the uploads directory	vor 5 Jahren
.buildpacks	CI: Add auto-deployment via dokku.	vor 5 Jahren
.credo.exs	Move Consistency.FileLocation to ./test	vor 3 Jahren
.dockerignore	remove docs/ from .dockerignore	vor 4 Jahren
.formatter.exs	HTML: Compile Scrubbers on boot	vor 4 Jahren
.gitattributes	.gitattributes: Treat js/css/source maps as binary files	vor 3 Jahren
.gitignore	added generated `pleroma.env`	vor 3 Jahren
.gitlab-ci.yml	CI: Install libmagic-dev in debian release targets	vor 3 Jahren
.mailmap	add mailmap [ci skip]	vor 4 Jahren
AGPL-3	LICENSE → AGPL-3	vor 5 Jahren
CC-BY-4.0	Add a copy of CC-BY-4.0 to the repo	vor 3 Jahren
CC-BY-SA-4.0	CC-BY-SA-4.0: Add a copy of the CC-BY-SA-4.0 license	vor 5 Jahren
CHANGELOG.md	CHANGELOG.md: Use a period after every bullet point for unreleased sections	vor 3 Jahren
COPYING	Bump copyright dates.	vor 4 Jahren
Dockerfile	Install file-dev in Dockerfile build stage	vor 3 Jahren
Procfile	CI: Add auto-deployment via dokku.	vor 5 Jahren
README.md	Add FreeBSD and alpha sort	vor 3 Jahren
SECURITY.md	SECURITY.md: update supported versions to only 2.2	vor 3 Jahren
coveralls.json	exclude file_location check from coveralls	vor 3 Jahren
docker-entrypoint.sh	Create docker.exs and docker-entrypoint + round out Dockerfile	vor 4 Jahren
elixir_buildpack.config	Upgrade to Elixir 1.9	vor 3 Jahren
mix.exs	Merge branch 'chores/tesla_1.4.0' into 'develop'	vor 3 Jahren
mix.lock	Merge branch 'chores/tesla_1.4.0' into 'develop'	vor 3 Jahren

README.md

About

Pleroma is a microblogging server software that can federate (= exchange messages with) other servers that support ActivityPub. What that means is that you can host a server for yourself or your friends and stay in control of your online identity, but still exchange messages with people on larger servers. Pleroma will federate with all servers that implement ActivityPub, like Friendica, GNU Social, Hubzilla, Mastodon, Misskey, Peertube, and Pixelfed.

Pleroma is written in Elixir and uses PostgresSQL for data storage. It's efficient enough to be ran on low-power devices like Raspberry Pi (though we wouldn't recommend storing the database on the internal SD card ;) but can scale well when ran on more powerful hardware (albeit only single-node for now).

For clients it supports the Mastodon client API with Pleroma extensions (see the API section on https://docs-develop.pleroma.social).

Client Applications for Pleroma

Installation

OTP releases (Recommended)

If you are running Linux (glibc or musl) on x86/arm, the recommended way to install Pleroma is by using OTP releases. OTP releases are as close as you can get to binary releases with Erlang/Elixir. The release is self-contained, and provides everything needed to boot it. The installation instructions are available here.

From Source

If your platform is not supported, or you just want to be able to edit the source code easily, you may install Pleroma from source.

OS/Distro packages

Currently Pleroma is not packaged by any OS/Distros, but if you want to package it for one, we can guide you through the process on our community channels. If you want to change default options in your Pleroma package, please discuss it with us first.

Docker

While we don’t provide docker files, other people have written very good ones. Take a look at https://github.com/angristan/docker-pleroma or https://glitch.sh/sn0w/pleroma-docker.

Compilation Troubleshooting

If you ever encounter compilation issues during the updating of Pleroma, you can try these commands and see if they fix things:

mix deps.clean --all
mix local.rebar
mix local.hex
rm -r _build

If you are not developing Pleroma, it is better to use the OTP release, which comes with everything precompiled.

Documentation

Latest Released revision: https://docs.pleroma.social
Latest Git revision: https://docs-develop.pleroma.social

Community Channels

IRC: #pleroma and #pleroma-dev on freenode, webchat is available at https://irc.pleroma.social
Matrix: https://matrix.to/#/#freenode_#pleroma:matrix.org and https://matrix.to/#/#freenode_#pleroma-dev:matrix.org