any actual callee will be dealing with a User struct to begin with, so
just check the child struct inside User.superuser?/1 with pattern matching.

auth_active?/1 can check remote users and return true directly.

user: use pattern matching to determine if user is local or remote instead of the previous hairy logic

Add logging to syslog

See merge request pleroma/pleroma!622

Actually put some onformation in the error user, make it actually properly parse in conversations.

See merge request pleroma/pleroma!638

in conversations.

Make TwAPI UserView more resilient to issues.

See merge request pleroma/pleroma!634

Scarlett/pleroma search visibility check

See merge request pleroma/pleroma!635

Will work for missing users and badly migrated users.

Add check to prevent multiple follow notifications from the same user

Closes #397

See merge request pleroma/pleroma!591

fix user search results for users with unset display name

Closes #499

See merge request pleroma/pleroma!625

fix 486: Add option --assume-yes to allow mix pleroma.user to work non-interactive

See merge request pleroma/pleroma!627

Don't crash on AP request for tombstone

See merge request pleroma/pleroma!630

Strip HTML in and allow emoji in summaries.

See merge request pleroma/pleroma!631

Because tombstone objects has no addressing the is_public?-predicate
would cause an error that propagated as a 500 error in the api

rich media: use cachex to avoid flooding remote servers

See merge request pleroma/pleroma!629

Different caches based on the module. Remove scrubber version since it is not relevant anymore

See merge request pleroma/pleroma!628

URL previews in posts

Closes #402

See merge request pleroma/pleroma!617

Activitypub c2s delete activity

See merge request pleroma/pleroma!618