pleroma/config
rinpatch 2c55f7d7cb Remove FedSockets
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
https://git.pleroma.social/pleroma/pleroma/-/issues/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.
2020-11-17 17:28:30 +03:00
..
benchmark.exs web push http_client fix 2020-10-01 13:32:11 +03:00
config.exs Remove FedSockets 2020-11-17 17:28:30 +03:00
description.exs Remove FedSockets 2020-11-17 17:28:30 +03:00
dev.exs Enable strict validation mode in dev and test environments 2020-05-04 22:35:28 +04:00
docker.exs Remove dynamic config as default, add healthcheck 2019-09-03 09:31:52 -04:00
dokku.exs
emoji.txt
prod.exs Set Logger level to :info in prod 2019-12-09 19:11:54 +07:00
releases.exs some refactor and tests 2020-01-21 18:42:00 +03:00
test.exs RemoteIp module name 2020-10-13 16:43:50 +03:00