#612 closed defect (fixed)
Twitter: HTML entities like < and > aren't unescaped to < and >
| Reported by: | Owned by: | geert | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Version: | 1.2.6 | |
| Keywords: | Cc: | ||
| IRC client+version: | Client-independent | Operating System: | Linux |
| OS version/distro: |
Description
Twitter's API returns < and > for <>, and maybe & for &, although I don't think so. It differ from identi.ca in this regard.
Presumably this is some measure to avoid having silly third party websites that consume the API shooting themselves in the foot.
Bitlbee should s/</</g s/>/>/g in the client before displaying it on IRC.
Attachments (0)
Change History (4)
comment:1 follow-up: 3 Changed at 2010-05-08T14:04:50Z by
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
comment:2 Changed at 2010-05-08T14:06:11Z by
I see your remark about identi.ca here now. Ugh. I hope this is not going to get messy when we add non-Twitter support to the module.
comment:3 Changed at 2010-05-08T14:08:56Z by
Replying to wilmer:
Thanks for the report. Luckily this is already taken care of: changeset:devel,564.
It seems that this is indeed somewhat related to protecting the ignorant. I noticed that when I tweet something like "& & &amp; < <" via their web interface, the result is simply "& & & < <".
BitlBee should do the right thing now, in both directions. Wait for 1.2.7 which should come at least next month (in time before the OAuth deadline).
Thanks! And sorry for the duplicate, I tried searching the bugtracker before I filed but didn't find anything.
Looking forward to 1.2.7. Thanks for the Twitter support.
Replying to wilmer:
I see your remark about identi.ca here now. Ugh. I hope this is not going to get messy when we add non-Twitter support to the module.
It shouldn't be a problem. I've written a bidirectional Twitter <-> Identi.ca syncing script and < and > were the only difference in the two APIs that I noticed. I was using Perl's Net::Twitter though, so that may have hid some nastyness.
comment:4 Changed at 2010-05-08T14:10:38Z by
No problem, it's entirely possible that there was no other bug report filed for this yet; it was a one line change as you can see so filing a bug for it myself also seemed like a waste of time. :-)
Thanks for the report. Luckily this is already taken care of: changeset:devel,564.
It seems that this is indeed somewhat related to protecting the ignorant. I noticed that when I tweet something like "& & &amp; < <" via their web interface, the result is simply "& & & < <".
BitlBee should do the right thing now, in both directions. Wait for 1.2.7 which should come at least next month (in time before the OAuth deadline).