Closed ianpaul closed 6 years ago
bumping this for @commandline I haven't been able to fix the unescaped HTML problem, but at least this version of the plugin doesn't throw an error when tweets contain certain characters like the current version does. If you have any suggestions for how I might fix the unescaped HTML issue I'm all ears.
I ran into an edge case with the Twitter plugin where if a tweet had a special character--in this case an ellipsis--it threw an error. This edit fixes that, but now some special characters are printing as unescaped HTML (ampersand, angle brackets, etc.). I've tried to fix that but so far no luck. It could also be a quirk of my terminal as other tools I use--like Jlund's Streisand--have the same problem on my computer.