I did some research on what limit would be suitable. I found out that we have quite a lot of legitimate blobs over three megabytes, some even over 5 megabytes. One of them was a huge table. It is not possible to just set a hard limit that would not cause false positives while still being useful. Doing this would require changes in the UI as well (to disallow translation of huge sections) or some logic to compare source and target blob size. Latter would be complicated since we don't necessarily have the source and target blobs around to compare them, so I would lean on dropping this task.