Omnimaga
Omnimaga => Discontinued => Our Projects => OmnomIRC Development => Topic started by: calcdude84se on April 30, 2011, 12:57:59 am
-
Yeah. :P
Edit: it appears inconsistent. For example, "te~st" never displays, while "k~k" does.
-
Odd. It works half of the time, found out that if the
3rd character is a position of the tilde is a multiple of 3 it doesn't work.
-
Also, don't count spaces and index from 1.
-
wut
How do you guys find these? :|
The only thing I can think of is some sort of flaw in the base64 lib I'm using, I'll read over it..
-
I typed a message that had a tilde in the bad position, and it didn't display. I tried it a couple more times and it still didn't work, at which point I made this topic. Juju and I then proceeded to test it ;D
Edit: Oh, and good luck fixing it, of course :)
-
I love these hidden tricks :D
The only thing I can think of is some sort of flaw in the base64 lib I'm using, I'll read over it..
Every third? Sounds like it.
EDIT: Always works for me ???/me ~test
/me t~est
/me te~st
/me tes~t
/me test~
EDIT2: Oh, non-/me. Never mind.
EDIT3: Still works ???
~test
t~est
te~st
tes~t
test~
EDIT4: Oh, OmnomIRC. Never mind.
-
I tested this and here are my resuts
te~st works if not sent through omnomIRC(I used XChat) and it will display on omnomirc
-
Stop confusing us, Deep :P
I'll be interested to know just what went wrong.
By the way, Deep Thought, what does the number three have to do with a base64 lib?
Edit: Ruler, yep, from a normal client OmnomIRC receives the lines just fine :) It can't send them, though.
-
By the way, Deep Thought, what does the number three have to do with a base64 lib?
In base64, each group (triplet) of three ASCII characters is represented as four B64 digits.
http://en.wikipedia.org/wiki/Base64#Examples
-
Oh, I see. Silly me :P (* calcdude needs to think for himself a bit more...)
I wonder if any other characters are affected...
-
Er, it happens in /me lines too :-
-
So it does. I just didn't realize it. Fixing the topic title, here I go!
Edit: Done.
-
Guess it's just tilde... What does $7E have to do with anything? O.o
-
~ is the last displayable char in the (standard) ascii set. Maybe somewhere there is an error in conversion code that makes it go out of 'bounds'.
-
I can type รกรกรก with no problem though...
-
Ok, other theory: maybe durring the process, 1 is added to the char (to be subtracted later). If this is so, 126 becomes 127, which is the control character DEL. Maybe this has something to do with it?
Anyway, its a weird bug.
-
Here's what was happening:
Base64 has + as a valid character.
+ is not valid for URLs.
~ just happens to have a + in it, if it's in a specific spot.
Solution:
Find/replace + for - on send, as - is a valid URL char and not used in Base64.
Find/replace - for + on receive, then base64 decode.
Problem solved.