1. 30 Mar, 2021 3 commits
  2. 27 Feb, 2021 1 commit
  3. 23 Feb, 2021 1 commit
  4. 22 Feb, 2021 1 commit
  5. 18 Feb, 2021 1 commit
  6. 13 Feb, 2021 1 commit
  7. 29 Jan, 2021 1 commit
  8. 21 Jan, 2021 4 commits
  9. 12 Jan, 2021 1 commit
  10. 20 Nov, 2020 1 commit
  11. 19 Nov, 2020 2 commits
  12. 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
  13. 21 Oct, 2020 1 commit
  14. 20 Oct, 2020 1 commit
  15. 16 Oct, 2020 1 commit
  16. 13 Oct, 2020 2 commits
  17. 07 Oct, 2020 3 commits
  18. 06 Oct, 2020 4 commits
  19. 18 Sep, 2020 1 commit
  20. 17 Sep, 2020 1 commit
  21. 14 Sep, 2020 1 commit
    • rinpatch's avatar
      Remove `:managed_config` option. · 0b5e72ec
      rinpatch authored
      In practice, it was already removed half a year ago, but the description
       and cheatsheet entries were still there.
      
      The migration intentionally does not use ConfigDB.get_by_params, since
      this will break migration code as soon as we add a new field is added
       to ConfigDB.
      
      Closes #2086
      0b5e72ec
  22. 11 Sep, 2020 1 commit
    • feld's avatar
      Spelling · 40c847dc
      feld authored
      Reported by:	trevoke
      40c847dc
  23. 10 Sep, 2020 3 commits
  24. 08 Sep, 2020 3 commits