Age | Commit message (Collapse) | Author |
|
|
|
Closes #1382
|
|
Force password reset for multiple users
Closes admin-fe#46
See merge request pleroma/pleroma!1928
|
|
Probably fixes the issue hj had, where polls would have different
counters between endpoints.
|
|
|
|
User Search: Remove superfluous setweight and random test.
See merge request pleroma/pleroma!1935
|
|
The test tested for a behavior that isn't actually enforced anymore.
|
|
`conversation` stream event payload.
|
|
capture test log where errors are expected
See merge request pleroma/pleroma!1915
|
|
|
|
Store status data inside flag activity
See merge request pleroma/pleroma!1849
|
|
streamer: use direct object for filter checks when there is no valid child object in an activity
Closes #1291
See merge request pleroma/pleroma!1931
|
|
AdminAPI: Omit relay user from users list
Closes #1349
See merge request pleroma/pleroma!1924
|
|
Switching to FastSanitize
See merge request pleroma/pleroma!1916
|
|
object in an activity
We call Object.normalize/1 to get the child object for situations like Announce.
However, the check is flawed and immediately fails if Object.normalize/1 fails.
Instead, we should use the activity itself in those cases to allow activities which
never have a child object to pass through the filter.
Closes #1291
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Move following relationships to a separate table
Closes #1233
See merge request pleroma/pleroma!1814
|
|
|
|
|
|
|
|
user's `unread_conversation_count`.
Since the conversations with the blocked user are invisible, they are excluded
from the blocking user's `unread_conversation_count`.
|
|
|
|
refactor/following-relationships
|
|
|
|
1304-user-info-deprecation
# Conflicts:
# lib/pleroma/notification.ex
|
|
|
|
single-element array deserialization
There appears to be confusion on whether or not Pleroma can handle this particular
sin of JSON-LD. It can, and we will add regression tests to prove that it can handle
this particular sin. Which, by the way, this is actually not a "feature" of JSON-LD,
but whatever.
|
|
Direct messages should provide a distinct push notification subject
See merge request pleroma/pleroma!1864
|
|
|
|
|
|
Do not include notifications from blocked users when with_muted is set
See merge request pleroma/pleroma!1869
|
|
This is not what with_muted is for per documentation and it was agreed
on irc that this behavior doesn't make sense.
|
|
|
|
|
|
1304-user-info-deprecation
# Conflicts:
# lib/pleroma/user/info.ex
# lib/pleroma/web/activity_pub/activity_pub.ex
# lib/pleroma/web/activity_pub/transmogrifier.ex
|
|
|
|
|
|
git.pleroma.social:pleroma/pleroma into 1304-user-info-deprecation
# Conflicts:
# CHANGELOG.md
# lib/pleroma/notification.ex
# lib/pleroma/user.ex
# lib/pleroma/user/info.ex
# lib/pleroma/web/admin_api/admin_api_controller.ex
# lib/pleroma/web/ostatus/handlers/follow_handler.ex
# lib/pleroma/web/ostatus/ostatus.ex
# lib/pleroma/web/salmon/salmon.ex
# lib/pleroma/web/websub/websub.ex
# test/web/admin_api/admin_api_controller_test.exs
# test/web/federator_test.exs
# test/web/mastodon_api/controllers/conversation_controller_test.exs
# test/web/ostatus/ostatus_controller_test.exs
# test/web/ostatus/ostatus_test.exs
# test/web/salmon/salmon_test.exs
# test/web/websub/websub_test.exs
|
|
1304-user-info-deprecation
# Conflicts:
# CHANGELOG.md
# lib/pleroma/notification.ex
# lib/pleroma/user.ex
# lib/pleroma/user/info.ex
# lib/pleroma/web/activity_pub/activity_pub.ex
# lib/pleroma/web/admin_api/admin_api_controller.ex
# lib/pleroma/web/ostatus/handlers/follow_handler.ex
# lib/pleroma/web/ostatus/ostatus.ex
# lib/pleroma/web/salmon/salmon.ex
# lib/pleroma/web/websub/websub.ex
# test/web/admin_api/admin_api_controller_test.exs
# test/web/federator_test.exs
# test/web/mastodon_api/controllers/conversation_controller_test.exs
# test/web/ostatus/ostatus_controller_test.exs
# test/web/ostatus/ostatus_test.exs
# test/web/salmon/salmon_test.exs
# test/web/websub/websub_test.exs
|
|
Misc. fixes / improvements.
|
|
|
|
hint set to true
|