1. 24 Jan, 2022 6 commits
  2. 19 Jan, 2022 3 commits
  3. 09 Jan, 2022 5 commits
  4. 28 Dec, 2021 1 commit
  5. 12 Dec, 2021 1 commit
    • Ilja's avatar
      Allow canceling a follow request · 4587f37d
      Ilja authored
      When a follow request is sent, but not (yet) accepted, the behaviour is now to cancel the request instead of re sending.
      
      The reason is double
      * You couldn't cancel a follow request if you change your mind and the request wasn't answered yet
      * Instances don't always correctly process a new follow request when the following is already happening. If something went wrong (e;g. the target server thinks you're following, but your instance thinks you're not yet), it's better to first sent an unfollow. This is the behaviour that Mastodon and most probably most other clients have. Therefore this flow is more tested and expected by other instances.
      4587f37d
  6. 03 Dec, 2021 2 commits
  7. 16 Nov, 2021 2 commits
    • HJ's avatar
      Merge branch 'fix/escape-display-name' into 'develop' · ea0887a1
      HJ authored
      entity_normalizer: Escape name when parsing user
      
      See merge request !1415
      ea0887a1
    • rinpatch's avatar
      entity_normalizer: Escape name when parsing user · d36b45ad
      rinpatch authored
      In January 2020 Pleroma backend stopped escaping HTML in display names
      and passed that responsibility on frontends, compliant with Mastodon's
      version of Mastodon API [1]. Pleroma-FE was subsequently modified to
      escape the display name [2], however only in the "name_html" field. This
      was fine however, since that's what the code rendering display names used.
      
      However, 2 months ago an MR [3] refactoring the way the frontend does emoji
      and mention rendering was merged. One of the things it did was moving away
      from doing emoji rendering in the entity normalizer and use the unescaped
      'user.name' in the rendering code, resulting in HTML injection being
      possible again.
      
      This patch escapes 'user.name' as well, as far as I can tell there is no
      actual use for an unescaped display name in frontend code, especially
      when it comes from MastoAPI, where it is not supposed to be HTML.
      
      [1]: !1052
      [2]: https://git....
      d36b45ad
  8. 21 Oct, 2021 1 commit
  9. 29 Sep, 2021 1 commit
  10. 19 Sep, 2021 2 commits
  11. 16 Sep, 2021 1 commit
  12. 14 Sep, 2021 1 commit
  13. 09 Sep, 2021 8 commits
  14. 07 Sep, 2021 3 commits
  15. 05 Sep, 2021 3 commits