5 ms·
Have you tried compressing your JSON before base64 encoding it. https://github.com/KilledByAPixel/JSONCrush https://github.com/KilledByAPixel/JSONCrush Agreed
by alberth 4y ago
Have you tried compressing your JSON before base64 encoding it.
https://github.com/KilledByAPixel/JSONCrush https://github.com/KilledByAPixel/JSONCrush
Agreed with GP, it seems like you don't even need a backend.
- CBarkleyU 4y agoEven when compressing thje JSON before encoding it, it's still way too long for a shareable link. As I've said below, I've roughly calculated the entropy and even had a quick look around if there was any cool research out there regarding compressing the type of data I have (just loads of integers) (and there is cool research out there, just no magic, unfortunately).
- 8note 4y agoJSON might be the problem though? The string representation of integers could easily take more space than storing them as ints
- CBarkleyU 4y agoFor sure, but how much impact does it actually have? Let's say I have around 2000 datapoints, all of them integers, little rhyme or reason to their sequence. I'm very open for ideas on how to squeeze that down to a link that wouldnt (a) deter you from sharing that link with family and friends and (b) deter your family and friends from clicking that link.
- woleium 4y agoWhy not use an url shortener?