By @edent · android AOSP bugs DarkMode LineageOS · 4 comments · 300 words · read ~127 times.
I don't know if this is a bug, or just the way the world works now. Several of the people who live in my phone use artistic black and white headshots. They look very cool. But my Android phone shows their image with inverted colours - so they look like pure shite. Here's what my […]
Continue reading →By @edent · books bugs google · 3 comments · 300 words · read ~113 times.
Google Books is one of many projects that Google has forgotten about. There's no support available and, of course, it's impossible to send them a bug report. The best anyone can do is write a ranty blog post and hope it gets noticed. When I search for my name in Google Books, it returns books […]
Continue reading →By @edent · bugs Text Encoding unicode · 1 comment · 200 words · read ~123 times.
I received this weird bit of mojibake in an email. Here's the raw text view: ------=_NextPart_001_009E_01D4D8BF.D0737E10 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable =E6=8C=A8=E2=8E=92tml xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"= urn:schemas-microsoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-c= om:office:word" xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml= " xmlns=3D"http://www.w3.org/TR/REC-html40"> What's going on? 挨 is a Chinese, Japanese, Korean (cjk) unified ideograph (U+6328) ⎒ is the passive-pull-up-output symbol (U+2392) That's somehow replaced: < - less-than […]
Continue reading →By @edent · bugs facebook security unicode url · 350 words · read ~737 times.
Facebook rewrite URLs with Unicode in the path - this is not best practice and could be dangerous. It is possible to create a URL like http://bit.ly/😀 - the Unicode characters are valid in the path. The URL Encoded representation is : bit.ly/%F0%9F%98%80 Facebook mangles these URLs in such a way that it might be […]
Continue reading →By @edent · bugs chrome chromium firefox unicode · 350 words · read ~1,312 times.
Take a look at the following text, looks normal enough doesn't it? "Harry ".draziw a si Potter Now, try to select the text and see what happens. WHAT WITCHCRAFT IS THIS?! If you examine the source code for this page, you'll see that I'm using the Unicode Bi-Directional characters. "Harry ‮".draziw a si ‭Potter These […]
Continue reading →By @edent · bugs gmail google privacy · 8 comments · 700 words · read ~32,922 times.
My wife likes to set reminders for herself in Google Calendar. Recently, she added a note to her personal Google Calendar reading "Email alice@example.com to discuss pay rise" and set the date for a few months from now. She'd had a discussion with her boss, Alice, and they'd agreed to talk about salary later in […]
Continue reading →By @edent · bugs security twitter usability · 7 comments · 300 words · read ~5,241 times.
Did you know that you can to link to a specific Tweet on Twitter? The URL looks like this: https://twitter.com/#!/edent/status/197967209459499008 Pretty obviously, that's the user's name and the ID of their tweet. Simple, right? Not really, click on that link and you'll see this: That's my name in the URL bar - but the Number […]
Continue reading →By @edent · bugs dabr parse regex twitter urls · 5 comments · 400 words · read ~186 times.
The Twitter Engineering Team have a set of text processing classes which are meant to simplify and standardise the recognition of URLs, screen names, and hashtags. Dabr makes use of them to keep in conformance with Twitter's style. One of the advantages of the text processing is that it will recognise that www.example.com is a […]
Continue reading →