1. 01 Jul, 2022 3 commits
    • Ilja's avatar
      Rename the Exiftool module · 8303af84
      Ilja authored
      No migrations or checks yet
      8303af84
    • Ilja's avatar
      Rename the new module · 551721e4
      Ilja authored
      551721e4
    • Ilja's avatar
      Use EXIF data of image to prefill image description · cd316d72
      Ilja authored
      During attachment upload Pleroma returns a "description" field. Pleroma-fe has an MR to use that to pre-fill the image description field, <pleroma-fe!1399>
      
      * This MR allows Pleroma to read the EXIF data during upload and return the description to the FE
          * If a description is already present (e.g. because a previous module added it), it will use that
          * Otherwise it will read from the EXIF data. First it will check -ImageDescription, if that's empty, it will check -iptc:Caption-Abstract
          * If no description is found, it will simply return nil, just like before
      * When people set up a new instance, they will be asked if they want to read metadata and this module will be activated if so
      
      This was taken from an MR i did on Pleroma and isn't finished yet.
      cd316d72
  2. 08 May, 2022 1 commit
  3. 19 Jan, 2022 1 commit
    • rinpatch's avatar
      Add ForceMentionsInContentPolicy · a02cfd7f
      rinpatch authored
      Even though latest PleromaFE supports displaying these properly, mobile
      apps still exist, so I think we should offer a workaround to those who
      want it.
      a02cfd7f
  4. 15 Jan, 2022 1 commit
  5. 06 Aug, 2021 1 commit
    • Ilja's avatar
      Change docs · 506bf163
      Ilja authored and Haelwenn's avatar Haelwenn committed
      * ./configuration/mrf.md
        * Change example
      * ./configuration/cheatsheet.md
        * Change descriptions to include that a reason is given
      * CHANGELOG.md
        * Add as breaking change
      506bf163
  6. 02 Jun, 2021 1 commit
  7. 01 Jun, 2021 1 commit
  8. 16 Apr, 2021 1 commit
  9. 30 Mar, 2021 3 commits
  10. 27 Feb, 2021 1 commit
  11. 23 Feb, 2021 1 commit
  12. 22 Feb, 2021 1 commit
  13. 18 Feb, 2021 1 commit
  14. 13 Feb, 2021 1 commit
  15. 29 Jan, 2021 1 commit
  16. 21 Jan, 2021 4 commits
  17. 12 Jan, 2021 1 commit
  18. 20 Nov, 2020 1 commit
  19. 19 Nov, 2020 2 commits
  20. 17 Nov, 2020 1 commit
    • rinpatch's avatar
      Remove FedSockets · 2c55f7d7
      rinpatch authored
      Current FedSocket implementation has a bunch of problems. It doesn't
      have proper error handling (in case of an error the server just doesn't
      respond until the connection is closed, while the client doesn't match
      any error messages and just assumes there has been an error after 15s)
      and the code is full of bad descisions (see: fetch registry which uses
      uuids for no reason and waits for a response by recursively querying a
       ets table until the value changes, or double JSON encoding).
      
      Sometime ago I almost completed rewriting fedsockets from scrach to
      adress these issues. However, while doing so, I realized that fedsockets
       are just too overkill for what they were trying to accomplish, which is
       reduce the overhead of federation by not signing every message.
      This could be done without reimplementing failure states and endpoint
       logic we already have with HTTP by, for example, using TLS cert auth,
      or switching to a more performant signature algorithm. I opened
      #2262 for further
      discussion on alternatives to fedsockets.
      
      From discussions I had with other Pleroma developers it seems like they
       would approve the descision to remove them as well,
      therefore I am submitting this patch.
      2c55f7d7
  21. 04 Nov, 2020 1 commit
  22. 21 Oct, 2020 1 commit
  23. 20 Oct, 2020 1 commit
  24. 16 Oct, 2020 1 commit
  25. 13 Oct, 2020 2 commits
  26. 07 Oct, 2020 3 commits
  27. 06 Oct, 2020 3 commits