Signal <-> XMPP attachments #3
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Refactor component and processing to have external libraries under clients.
Separate out common functions into generic library where all functions have an additional service argument.
Lower TTFB from Signal to XMPP by chaining these generic operators in two ways:
Signal [get attachment] -> XMPP [get upload slot] -> HTTP [upload attachment] -> XMPP [send attachment]
XMPP [get attachment] -> Signal [send attachment]
Meaning that in deferred, we no longer have:
as this actually blocks until all attachments are downloaded before sending the first to XMPP.
Check the reciprocal path and ensure the same is not true.
Refactor is key otherwise this is a mess.
Look into removing Redis as a one way intermediary by combining component and processing.