No description
Find a file
Oneric f5898ab0fb
Fix malformed is_active qualifiers in User.Query usages
While "is_active" is a property of users, it is not a recognised keyword
for the User.Query helper; instead "deactivated" with negated value must
be used.
This arose because originally the user property was also called
"deactivated" until it was renamed adn negated five years ago
in 860b5c7804. This included renaiming
the parameter in most but not all User.Query usages.
Notably the parameter in User.get_followers_query was renamed
but not in User.get_friends_query (friends == following).
The accepted query parameter in User.Query however was not changed.
This lead to the former mistakenly including deleted users causing
too large values to be reported in the ActivityPub follower, but not
following collection as reported in #1078.

In Masto API responses filtering by `User.is_visible` weeded out
the extra accounts before they got displayed to API users.

On the surface it might seem logical to align the name of the User.Query
parameter with the actual property name. However, User.Query already
accepts an "active" parameter which is an alias for limiting to accounts
which are neither deleted nor deactivated by moderators (both indicated
by is_active) and also are not newly created account requests still
pending an admin approval (is_approved) or necessary email confirmation
(is_confirmed); in short as the alias suggests whether the account is
active. Two highly similar parameter names like this would be much too
confusing.

The renamed "is_active" on the other hand does not actually suffice to
say whether an account is actually active, only whether it has (not yet)
ceased to be active (by its own volition or moderator action).
Meaning its "new" name is actively misleading. Arguably the rename
made things worse for no reason whatsoever and should not ever have
happened.

For now, we’ll just revert the incorrect query helper parameter renames.

Fixes: https://akkoma.dev/AkkomaGang/akkoma/ issues/ 1078
(cherry picked from commit a899663ddc0e3a2084a239eabd79608a94ac5493)
2026-10-27 17:24:58 +04:00
.forgejo comment out stuff 2026-02-18 13:37:10 +01:00
.gitlab Update MR template to include the type 'change' 2023-11-08 09:37:08 -05:00
.woodpecker Merge branch 'develop' into audit-mix-audit-report 2026-10-21 19:24:32 +02:00
benchmarks Ensure benchee doesn't run unless we are executing benchmarks 2023-11-08 12:44:57 -05:00
changelog.d Merge pull request 'Federation: do not deliver to instances rejected by SimplePolicy' (#8021) from lambadalambda/pleroma:fix/federation-reject-instances into develop 2026-10-27 13:20:00 +00:00
ci Replace Elixir 1.17 with 1.18 for build unit-testing pipelines 2025-05-24 22:17:38 +02:00
config Merge branch 'audit-mix-audit-report' (#69) into release/2.11 2026-10-22 16:37:08 +04:00
docs fix(federation): do not deliver to instances rejected by SimplePolicy 2026-10-27 12:38:18 +04:00
installation Merge pull request 'OpenRC: Automatically run migrations before starting pleroma' (#7680) from gitlab-mr-iid-4303 into develop 2026-07-29 11:07:32 +00:00
lib Fix malformed is_active qualifiers in User.Query usages 2026-10-27 17:24:58 +04:00
priv feat(oauth): support the profile scope 2026-10-26 12:29:51 +04:00
rel Merge pull request 'OpenRC: Automatically run migrations before starting pleroma' (#7680) from gitlab-mr-iid-4303 into develop 2026-07-29 11:07:32 +00:00
restarter Bump minimum Elixir version to 1.10 2022-09-02 22:53:54 +02:00
supplemental/search/fastembed-api Fastembed Server: Add health check endpoint 2024-05-27 14:15:04 +04:00
test Fix malformed is_active qualifiers in User.Query usages 2026-10-27 17:24:58 +04:00
tools Woodpecker CI: Update check-changelog script for Woodpecker 2026-03-31 14:32:52 +00:00
.buildpacks
.credo.exs Tell newer Credo it's OK to exit 0 on single with clauses and piping into anonymous functions for now 2022-11-13 18:46:02 -05:00
.dialyzer_ignore.exs Quiet Dialyzer 2024-07-25 16:36:34 -04:00
.dockerignore
.formatter.exs
.gitattributes
.gitignore Add spoofing regression tests 2026-04-30 14:31:06 +04:00
.gitlab-ci.yml GitlabCI: Fix. 2025-12-31 11:40:27 +04:00
.mailmap
.rgignore Add .rgignore for easier grepping 2023-12-10 17:06:28 +04:00
AGPL-3
CC-BY-4.0
CC-BY-SA-4.0
CHANGELOG.md Prepare 2.11.1 release 2026-10-26 22:02:51 +04:00
COPYING Revert "Merge branch 'copyright-bump' into 'develop'" 2023-01-02 20:38:50 +00:00
coveralls.json
docker-entrypoint-e2e.sh Seed E2E admin before API readiness 2026-05-25 16:06:21 +04:00
docker-entrypoint.sh allow custom db port 2022-11-11 12:22:21 -03:00
Dockerfile Bump minimum Elixir version to 1.17. 2026-09-08 22:39:36 +02:00
Dockerfile-e2e Add custom Docker image for FE E2E tests 2026-05-05 21:34:10 +02:00
elixir_buildpack.config Bump minimum Elixir version to 1.10 2022-09-02 22:53:54 +02:00
logo-with-name.png Fix missing readme logo 2026-07-26 21:14:29 +02:00
mix.exs Prepare 2.11.1 release 2026-10-26 22:02:51 +04:00
mix.lock Sec: Update hackney to version 4.9.1 2026-10-26 21:52:03 +04:00
Procfile
README.md Fix missing readme logo 2026-07-26 21:14:29 +02:00
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

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 --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

Community Channels