There is no indication whether or not Litterbox uploads are successful or fail in the buffer, witnessed a delayed processing of over 2-3minutes post submission from Discord before it rendered in the Sneedchat, meanwhile messages submitted from after the upload from Discord were received before it finally submitted to Sneedchat.
Solution perhaps is having the Bot post status updates of the upload in process, HTTP status codes from Litterbox perhaps as an inline message that is later deleted on a timer after it completes the upload and message to Sneedchat. Also needs failure condition if it doesn't see an echo of the message in Sneedchat.
There is no indication whether or not Litterbox uploads are successful or fail in the buffer, witnessed a delayed processing of over 2-3minutes post submission from Discord before it rendered in the Sneedchat, meanwhile messages submitted from after the upload from Discord were received before it finally submitted to Sneedchat.
Solution perhaps is having the Bot post status updates of the upload in process, HTTP status codes from Litterbox perhaps as an inline message that is later deleted on a timer after it completes the upload and message to Sneedchat. Also needs failure condition if it doesn't see an echo of the message in Sneedchat.
f954771c0c Completed, now modular with potential for different services and embeds to alert you what stage its in as it processes.
https://git.salastil.com/Salastil/Sneedchat-Discord-Bridge-Go/commit/f954771c0cad99c7a0829f1c2d8fdc6713127a8a Completed, now modular with potential for different services and embeds to alert you what stage its in as it processes.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
There is no indication whether or not Litterbox uploads are successful or fail in the buffer, witnessed a delayed processing of over 2-3minutes post submission from Discord before it rendered in the Sneedchat, meanwhile messages submitted from after the upload from Discord were received before it finally submitted to Sneedchat.
Solution perhaps is having the Bot post status updates of the upload in process, HTTP status codes from Litterbox perhaps as an inline message that is later deleted on a timer after it completes the upload and message to Sneedchat. Also needs failure condition if it doesn't see an echo of the message in Sneedchat.
f954771c0cCompleted, now modular with potential for different services and embeds to alert you what stage its in as it processes.