Re:Let's Decode a VST
by monkpit on Friday June 12, 2020 @10:26PM
(#23506192)
Pretty unusable on mobile - my phone keeps trying to either start a phone call to the “number” of the byte sequence I clicked on, or it tells me (repeatedly) that the site has been blocked from making calls, after I have canceled out a few times.
[ Parent
| on HN ]
Re:Let's Decode a VST
by NikolaNovak on Saturday June 13, 2020 @09:17AM
(#23509156)
Interesting. On Firefox on PC I only have one page; Cracking the Code lets me hover over bytes but I expected something more of HN link. What VSTs are? How they reverse engineered? Other uses of either technique?
This is literally a translation for specific obscure file format ¯\_(ツ)_/¯
Must be an iPhone thing. No problem on Pixel 3XL
Yeah, iOS will try to automatically detect phone numbers in web views. It can be annoying sometimes if the web page author doesn’t take that into consideration.
<meta name="format-detection" content="telephone=no">
Re:Let's Decode a VST
by BuildTheRobots on Saturday June 13, 2020 @08:12AM
(#23508857)
And yet in some crazy parallel universe, content authors choose to tag telephone numbers as such to make them clickable, rather than having to tell a browser not to incorrectly interpret text.
A crazy parallel universe where iPhone came before the web and could shape it from its inception, surely.
Re:Let's Decode a VST
by BuildTheRobots on Saturday June 13, 2020 @08:30PM
(#23514080)
RFC-5341 defines "the tel URI for telephone numbers" and is dated December 2004. The first iPhone was released June 2007, so there was already a way of marking phone numbers well before day one.
Surely apple is to blame for it though.
thanks for letting me know. weird about the phone calls. I'll check this out on mobile
ok fixed