Admins: FYI on lemmy logs:
Example of a federation message success (HTTP Response 200):
INFO actix_web::middleware::logger: 12.34.56.78 'POST /inbox HTTP/1.1' 200 0 '-' 'Lemmy/0.17.4; +https://remote.lemmy' 0.145673
and failure (HTTP Response 400):
INFO actix_web::middleware::logger: 12.34.56.78 'POST /inbox HTTP/1.1' 400 65 '-' 'Lemmy/0.17.4; +https://remote.lemmy' 0.145673
These are usually accompanied soon with a more verbose reason like Http Signature is expired.
Lemmy is far better at logging INCOMING stuff than it is OUTGOING. You can grep for activity_queue
to get a sense if there are issues. This is not good:
Target server https://lemmy.lemmy/inbox rejected https://lemmy.local/activities/announce/9852ff01-c768-484b-a38da-da021cd1333, aborting
Also there are stats indicating "pile-ups":
Activity queue stats: pending: 1, running: 1, retries: 706, dead: 0, complete: 12
I think the exception is companies “too big to die.” They serve as the archangels of tech so ALL other goals lead to being bought by FAANG or dying.