GitLab

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

in conversations.

Will work for missing users and badly migrated users.

The intention here is to allow proper subject copying when it contains
emoji, obviously this will require minor frontend changes, though.

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

because of user refetch, accounts can stop existing (get_from_ap_id() can fail), accordingly
filter the follow requests for these failures.