Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
Features/glitch soc frontend
See merge request pleroma/pleroma!192
|
|
|
|
|
|
|
|
# Conflicts:
# lib/pleroma/activity.ex
|
|
|
|
missing `info.deactivated`. Adjusted test.
|
|
I1t/pleroma 477 user search improvements
See merge request pleroma/pleroma!685
|
|
|
|
Indices in postgresql rely on operators, so they won't be used if you use only functions.
|
|
[#491] Made user bio preserve full nicknames (nick@host)
Closes #491
See merge request pleroma/pleroma!676
|
|
|
|
|
|
requests).
|
|
|
|
users.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
& followers boosting.
|
|
|
|
|
|
Twapi follower pagination
See merge request pleroma/pleroma!648
|
|
|
|
|
|
|
|
user: fix local vs remote determination in remote_or_auth_active?/1
See merge request pleroma/pleroma!640
|
|
|
|
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.
|
|
|
|
of the previous hairy logic
|
|
|
|
Will work for missing users and badly migrated users.
|
|
|
|
associated with it
because of user refetch, accounts can stop existing (get_from_ap_id() can fail), accordingly
filter the follow requests for these failures.
|
|
|
|
|