b11e8888d1
Two related changes that ensure remote images render inline in timelines instead of as clickable links. reverse_proxy: always force inline for whitelisted content types When `inline_content_types` is configured as a whitelist, the upstream's `content-disposition` header used to be passed through unchanged. Some origins send `content-disposition: attachment` for media we want embedded, so the proxy now always emits `content-disposition: inline` for whitelisted types (overriding the upstream header), deriving a filename from `MIME.extensions/1` (e.g. `inline.gif`) so browsers have something to use for "Save As". When the type has no known extension, the bare token `inline` is emitted. The `inline_content_types: true` (pass-through) and `:false` (always attachment) behaviours are unchanged. ActivityPub: sniff MIME type for extensionless/generic attachments Some remotes (e.g. extensionless Cloudflare Images URLs) ship attachments with no usable `mediaType` (missing, empty, or `application/octet-stream`), which would render as links instead of inline images. `AttachmentValidator.fix_media_type/1` now fetches the first 8 KB of the URL and runs it through libmagic when the declared type carries no real information. Only `image/*` results replace the declared type; any other result, non-2xx response, transport error, or exception yields `nil` and the original type is kept, so ingestion never blocks and non-image media is never reclassified. Present real types are left untouched (no fetch is attempted). The new logic lives in `Pleroma.Web.ActivityPub.ObjectValidators.AttachmentTypeSniffer`. Tests: comprehensive coverage of both changes, including a dedicated suite for the sniffer covering happy paths, non-image bodies, HTTP failures, raised exceptions, guard clauses, and verification that the Range header is sent; AttachmentValidator tests for mimeType fallback, empty-string mediaType, multi-URL sniffing, and HTTP-failure fallback; ReverseProxy tests for inline_content_types `true`/`false`/custom whitelists, bare-inline for types without a MIME extension, and attachment_name handling. |
||
|---|---|---|
| .forgejo | ||
| .gitlab | ||
| .woodpecker | ||
| benchmarks | ||
| changelog.d | ||
| ci | ||
| config | ||
| docs | ||
| installation | ||
| lib | ||
| priv | ||
| rel | ||
| restarter | ||
| supplemental/search/fastembed-api | ||
| test | ||
| tools | ||
| .buildpacks | ||
| .credo.exs | ||
| .dialyzer_ignore.exs | ||
| .dockerignore | ||
| .formatter.exs | ||
| .gitattributes | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| .mailmap | ||
| .rgignore | ||
| AGPL-3 | ||
| CC-BY-4.0 | ||
| CC-BY-SA-4.0 | ||
| CHANGELOG.md | ||
| COPYING | ||
| coveralls.json | ||
| docker-entrypoint-e2e.sh | ||
| docker-entrypoint.sh | ||
| Dockerfile | ||
| Dockerfile-e2e | ||
| elixir_buildpack.config | ||
| mix.exs | ||
| mix.lock | ||
| Procfile | ||
| README.md | ||
| SECURITY.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).
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 packaged for YunoHost, NixOS, Gentoo through GURU and Archlinux through AUR. You may find more at https://repology.org/project/pleroma/versions.
If you want to package Pleroma for any OS/Distros, 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.
Raspberry Pi
Community maintained Raspberry Pi image that you can flash and run Pleroma on your Raspberry Pi. Available here https://github.com/guysoft/PleromaPi.
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 --allmix local.rebarmix local.hexrm -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 libera.chat, webchat is available at https://irc.pleroma.social
- Matrix: #pleroma:libera.chat and #pleroma-dev:libera.chat