11 points | by FailMore a day ago ago
8 comments
Nice, I've also built something like this we use internally. Will it reduce token consumption as well?
Thanks. Re tokens reduction: not that I’m aware of. Would you mind explaining how it might? That could be a cool feature to add
I had not heard of url fragments before. Is there a size cap?
Hadn’t heard of it either - very smart, could open lots of other privacy-friendliness-improved „client-based web“ apps
TYVM. Yeah, I am curious to explore moving into other file formats like CSVs.
Ish, but the cap is the length of url that the browser can handle. For desktop chrome it's 2MB, but for mobile Safari its 80KB.
The compression algo SDocs uses reduces the size of your markdown file by ~10x, so 80KB is still ~800KB of markdown, so fairly beefy.
Markdown style editing looks very easy and convenient
Thanks! One potential use case I have for it is being able to make "branded" markdown if you need to share something with a client/public facing.
Nice, I've also built something like this we use internally. Will it reduce token consumption as well?
Thanks. Re tokens reduction: not that I’m aware of. Would you mind explaining how it might? That could be a cool feature to add
I had not heard of url fragments before. Is there a size cap?
Hadn’t heard of it either - very smart, could open lots of other privacy-friendliness-improved „client-based web“ apps
TYVM. Yeah, I am curious to explore moving into other file formats like CSVs.
Ish, but the cap is the length of url that the browser can handle. For desktop chrome it's 2MB, but for mobile Safari its 80KB.
The compression algo SDocs uses reduces the size of your markdown file by ~10x, so 80KB is still ~800KB of markdown, so fairly beefy.
Markdown style editing looks very easy and convenient
Thanks! One potential use case I have for it is being able to make "branded" markdown if you need to share something with a client/public facing.