338612d72b
During attachment upload Pleroma returns a "description" field. * This MR allows Pleroma to read the EXIF data during upload and return the description to the FE using this field. * If a description is already present (e.g. because a previous module added it), it will use that * Otherwise it will read from the EXIF data. First it will check -ImageDescription, if that's empty, it will check -iptc:Caption-Abstract * If no description is found, it will simply return nil, which is the default value * When people set up a new instance, they will be asked if they want to read metadata and this module will be activated if so There was an Exiftool module, which has now been renamed to Exiftool.StripLocation |
||
---|---|---|
benchmarks | ||
ci | ||
config | ||
docker-resources | ||
docs | ||
installation | ||
lib | ||
priv | ||
rel | ||
restarter | ||
test | ||
uploads | ||
.buildpacks | ||
.credo.exs | ||
.dockerignore | ||
.formatter.exs | ||
.gitattributes | ||
.gitignore | ||
.mailmap | ||
.woodpecker.yml | ||
AGPL-3 | ||
CC-BY-4.0 | ||
CC-BY-SA-4.0 | ||
CHANGELOG.md | ||
CODE_OF_CONDUCT.md | ||
COPYING | ||
coveralls.json | ||
docker-compose.yml | ||
docker-entrypoint.sh | ||
Dockerfile | ||
elixir_buildpack.config | ||
Makefile | ||
mix.exs | ||
mix.lock | ||
Procfile | ||
README.md | ||
SECURITY.md | ||
SIGNING_KEY.pub |
akkoma
a smallish microblogging platform, aka the cooler pleroma
About
This is a fork of Pleroma, which 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. Akkoma will federate with all servers that implement ActivityPub, like Friendica, GNU Social, Hubzilla, Mastodon, Misskey, Peertube, and Pixelfed.
Akkoma is written in Elixir and uses PostgresSQL for data storage.
For clients it supports the Mastodon client API with Pleroma extensions (see the API section on https://docs.akkoma.dev/stable/).
Installation
OTP releases (Recommended)
If you are running Linux (glibc or musl) on x86, the recommended way to install Akkoma 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 Akkoma from source.
- Alpine Linux
- Arch Linux
- Debian-based
- Debian-based (jp)
- FreeBSD
- Gentoo Linux
- NetBSD
- OpenBSD
- OpenBSD (fi)
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 Akkoma, you can try these commands and see if they fix things:
mix deps.clean --all
mix local.rebar
mix local.hex
rm -r _build