Age | Commit message (Collapse) | Author | |
---|---|---|---|
2019-08-07 | ActivityPub tests: remove assertions of embedded object being updated, | rinpatch | |
because the objects are no longer supposed to be embedded | |||
2019-08-06 | [#1150] fixed parser TwitterCard | Maksim | |
2019-08-05 | tests for CommonApi/Utils | Maksim | |
2019-08-05 | Linting. | lain | |
2019-08-05 | CommonAPI: Replies to conversations also get the correct context id. | lain | |
2019-08-05 | Pleroma Conversations API: Add a way to set recipients. | lain | |
2019-08-04 | Do not add the "next" key to likes.json if there is no more items | Sergey Suprunenko | |
2019-08-03 | Admin fixes | Alexander Strizhakov | |
2019-08-03 | Remove spaces from the domain search | Sergey Suprunenko | |
2019-08-03 | Handle MRF rejections of incoming AP activities | Sergey Suprunenko | |
2019-08-02 | Pleroma API: Add endpoint to get conversation statuses. | lain | |
2019-08-02 | Fix/mediaproxy whitelist base url | feld | |
2019-08-02 | CommonAPI: Extend api with conversation replies. | lain | |
2019-08-02 | Merge branch 'feature/hide-follows-remote' into 'develop' | lain | |
Refactor Follows/Followers counter syncronization and set hide_followers/hide_follows for remote users See merge request pleroma/pleroma!1411 | |||
2019-08-01 | Clean up tests output | Egor Kislitsyn | |
2019-07-31 | Merge branch 'fix/disallow-ostatus-follows-locked' into 'develop' | kaniini | |
Disallow following locked accounts over OStatus See merge request pleroma/pleroma!1512 | |||
2019-07-31 | Disallow following locked accounts over OStatus | rinpatch | |
2019-07-31 | test for Pleroma.Web.CommonAPI.Utils.get_by_id_or_ap_id | Maksim | |
2019-07-31 | ostatus: explicitly disallow protocol downgrade from activitypub | Ariadne Conill | |
This closes embargoed bug #1135. | |||
2019-07-31 | Add tests for counters being updated on follow | rinpatch | |
2019-07-31 | tests for TwitterApi/UtilController | Maksim | |
2019-07-31 | StatusView: Return direct conversation id. | lain | |
2019-07-31 | Merge branch 'develop' into feature/hide-follows-remote | rinpatch | |
2019-07-30 | Admin changes | Alexander Strizhakov | |
2019-07-29 | Revert "Merge branch 'bugfix/clean-up-markdown-rendering' into 'develop'" | kaniini | |
This reverts merge request !1504 | |||
2019-07-29 | markdown: clean up html generated by earmark | Ariadne Conill | |
2019-07-29 | Merge branch 'refactor/use-constants' into 'develop' | lain | |
refactoring: begin to use constants See merge request pleroma/pleroma!1500 | |||
2019-07-29 | Redirect not logged-in users to the MastoFE login page on private instances | Sergey Suprunenko | |
2019-07-29 | added tests for OstatusController | Maksim | |
2019-07-29 | constants: add as_public constant and use it everywhere | Ariadne Conill | |
2019-07-28 | add account confirmation email resend in mastodon api | Sachin Joshi | |
2019-07-26 | [#1097] added redirect: /pleroma/admin -> /pleroma/admin/ | Maksim | |
2019-07-25 | Merge branch 'develop' into feature/hide-follows-remote | rinpatch | |
2019-07-24 | Merge branch 'fix-remote-follow-from-ostatus-subscribe' into 'develop' | kaniini | |
Fix remote follow from /ostatus_subscribe Closes #1103 See merge request pleroma/pleroma!1472 | |||
2019-07-24 | Show the url advertised in the Activity in the Status JSON response | Sergey Suprunenko | |
2019-07-25 | Add WebFinger test for AP-only account | kPherox | |
2019-07-24 | WIP | Mike Verdone | |
2019-07-24 | tests WebFinger | Maksim | |
2019-07-24 | Add `domain_blocking` to the relationship API (GET ↵ | Eugenij | |
/api/v1/accounts/relationships) | |||
2019-07-24 | Revert "squash! Expose expires_at datetime in mastoAPI only for the activity ↵ | Mike Verdone | |
actor" This reverts commit 2981821db834448bf9b2ba26590314e36201664c. | |||
2019-07-24 | squash! Expose expires_at datetime in mastoAPI only for the activity actor | Mike Verdone | |
NOTE: rewrite the commit msg | |||
2019-07-24 | Expose expires_at datetime in mastoAPI only for the activity actor | Mike Verdone | |
In the "pleroma" section of the MastoAPI for status activities you can see an expires_at item that states when the activity will expire, or nothing if the activity will not expire. The expires_at date is only visible to the person who posted the activity. This is the conservative approach in case some attacker decides to write a logger for expiring posts. However, in the future of OCAP, signed requests, and all that stuff, this attack might not be that likely. Some other pleroma dev should remove the restriction in the code at that time, if they're satisfied with the security implications of doing so. | |||
2019-07-24 | Add support for activity expiration to common and Masto API | Mike Verdone | |
The "expires_at" parameter accepts an ISO8601-formatted date which defines when the activity will expire. At this point the API will not give you any feedback about if your post will expire or not. | |||
2019-07-24 | Cleanup: fix a comment | Mike Verdone | |
2019-07-24 | check both item and parent domain blocks | sadposter | |
2019-07-24 | honour domain blocks on streaming notifications | Sadposter | |
2019-07-23 | Merge branch 'feature/admin-api-user-statuses' into 'develop' | kaniini | |
Admin API: Endpoint for fetching latest user's statuses See merge request pleroma/pleroma!1413 | |||
2019-07-23 | rich media: parser: splice the given URL into the result | Ariadne Conill | |
2019-07-24 | Merge branch 'develop' into feature/admin-api-user-statuses | Maxim Filippov | |
2019-07-24 | AdminAPI: Add "godmode" while fetching user statuses (i.e. admin can see ↵ | Maxim Filippov | |
private statuses) |