>
> Sure, we may use a different "protocol" but i think the "//" is not 
> required.
>
just suppose it's a bit easier to parse (and by eye too).

That's actually part of the base64 string. every 3 bytes encodes to 4, but 
> we have 8. then it adds "=" as padding.
>
 why is it need to add it by hand? can twisterd add it by itself?

You know you don't have to, right? Just pass into twisterd's decodeshorturl 
> RPC and we're done.
>
oh, silly me. 

I don't know exactly how to get a reference into the formatted post that 
> can be later changed by a callback or something.
>
when we match shortened twister URL and perform "msg = msgAddHtmlEntity()" 
we may add some *id* to so called *templateShortenedTwisterURL* which we 
put in newHtmlEntityLink() and then search element with that id from 
callback function to manage it. it's not so good but I don't see clearly 
your need.

>

-- 
You received this message because you are subscribed to the Google Groups 
"twister-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to