Well that's interesting. I just found out after working on a post here that if I actually used up all the available characters, it just fails outright and says my post exceeded the allowed length.
That was with the little character counter at 0. Not negative, just 0. I also noticed that hitting shift - return to do a paragraph is 3 characters instead of 1. Oh well, learning the little oddnesses of a new, (at least to me,) thing. LOL!
1 year ago 路 馃憤 astroseneca
@mozz I do sometimes use special characters, like 谩, 茅, or 艔. But I didn't in that post. Your explination does make sense as to why a CR = 3 characters though. But when I did that it showed 3 characters being counted, so it seems like if the counter was working spot on it would still say 0 at 0. Not something life threatening I suppose, but I'll make a point now to do a quick copy of anything that gets close to the limit before I post it from now on. Just so if it happens again I don't lose it or have to type it over. LOL! 路 1 year ago
As for why it failed when you posted with 0 left, it looks like a bug in the gemini server running station where it counts the ending <CR><LF> as part of the total request length. This means you only get 1022 bytes to play with for the <URL> instead of the 1024 that Lagrange is (correctly) displaying in the UI. 路 1 year ago
A newline (\n) is encoded as "%0A" in the URL which is 3-bytes long . Any non-english or special characters are going to take up multiple bytes and blow through your 1024 quota faster. Definitely annoying, but now you know why :) 路 1 year ago
@jsreed5 I'm using Lagrange. And I did notice that a carriage return counted as 3 characters. 路 1 year ago
What client are you using? It may be possible the input dialog in your client doesn't account for carriage return or something like that. 路 1 year ago