Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
|
|
Move is emitted from the old account
EmojiReact is ~ Like
Announced TBD
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
incoming activity or object
|
|
|
|
|
|
|
|
Clean up Elixir 1.13 TODOs
See merge request pleroma/pleroma!4233
|
|
|
|
Pleroma.HTTP: support streaming response bodies
See merge request pleroma/pleroma!4239
|
|
malicious URLs
|
|
|
|
|
|
|
|
ReceiverWorker: tests, improvements
See merge request pleroma/pleroma!4241
|
|
|
|
Correct response in AdminAPI docs
See merge request pleroma/pleroma!4240
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
By removing the inReplyTo, tags, and cc we can simplify the test and it still passes signature validation
|
|
|
|
|
|
An instance block with authenticated fetch being required can cause this as we couldn't get the user to find their public key to verify the signature. Commonly observed if someone boosts/Announces a post from an instance that blocked you.
|
|
Signed-off-by: marcin mikołajczak <git@mkljczk.pl>
|
|
Upstream has a bug filed for this as they aren't handling this error internally, so it was raising
|
|
|
|
These are executed by Oban now and Oban can enforce the timeout if the regular HTTP timeout is not sufficient.
|
|
|
|
the response body
|
|
current adapter supports returning a Stream body
|
|
adapter
|
|
Translations update from Pleroma Weblate
See merge request pleroma/pleroma!4200
|