Note: USA-specific Not even 20 years ago, before any number could be ported to mobiles, landlines in some (all?) Baby Bell regions had their prefix determined by geography. In other words, you could know what "zone" a given phone number was in by its prefix. Take Silicon Valley. A (650) 960-xxxx number meant Mountain View. (408) 733-xxxx meant Sunnyvale. Etc. Zones roughly respected cities, but boundary conditions ab…
Falsehoods Programmers Believe About Phone Numbers (2016)
191–200 of 209 posts
Re: Falsehoods Programmers Believe About Phone Numbers (2016)
#192Earlier quoted context omitted.
Geography and dialling codes aren’t necessarily aligned. So none of those countries share a border - it doesn’t mean there was never a weird issue with international dialling codes at some point (and, after I did a bit of searching, it seems that there was)
> none of those countries share a border Precisely. That should give the reader pause to think that there's something wrong. You're missing that the author mixed up Monaco with Montenegro (Kosovo's neighbour) because they sound similar. That's the perennial Austria/Australia confusion writ small.
Re: Falsehoods Programmers Believe About Phone Numbers (2016)
#193And not long before that, it was common for several homes to share one fixed-line telephone number.
Re: Falsehoods Programmers Believe About Phone Numbers (2016)
#194Earlier quoted context omitted.
Yup. I mean, every programmer I know considers stuff like this to be very interesting trivia to learn and apply. But even if you know this stuff, putting the knowledge to use often involves a series of battles against your PMs and managers and maybe even customers, who either don't know it, have their own vision, or just follow what everyone else does. (Getting a product to work correctly is as much an exercise of di…
I remember a discussion on the Linux kernel list years ago - and I believe Linus himself at one point insisted that names with less than three characters shouldn't be accepted, as they must surely be invalid. I pointed out that when I was a student there was another student with a full name consisting of just a single letter. No first name, no last name, just that letter. And the best thing - the student loans bank's…
Re: Falsehoods Programmers Believe About Phone Numbers (2016)
#195Earlier quoted context omitted.
> Signal As I understand it, Signal is always intended to be the "StartTLS" of telephone communication, so naturally it explicitly targets mobile phone users. I only use Signal to call or text someone I would otherwise call directly. But I agree with your general opinion. For most services I found it's ridiculous to be hardlinked to my phone number. Why on Earth you have to expose your phone number to some random peo…
> Signal is always intended to be the "StartTLS" of telephone communication, so naturally it explicitly targets mobile phone users. This doesn't make sense to me. If I have telephone service and the person I want to talk to also has telephone service, why do I want to use Signal to communicate from my telephone device to their telephone device? Aha! Because I want to communicate privately and the telephone service do…
That’s precisely what bugs me about these platforms. They all want to create the “social graph” based on phone numbers without giving the option to the user on how they want to expose themselves and how they want to construct their social graph.
Re: Falsehoods Programmers Believe About Phone Numbers (2016)
#196Interesting how nobody here is complaining about Apple forcing all developers to switch to 2FA this month. They sell it as "more secure" and I read it as "higher chance to get locked out".
Dont use SMS 2fa, use TOTP.
Re: Falsehoods Programmers Believe About Phone Numbers (2016)
#197The biggest widely believed programmer falsehood I run into in practice: that they are ten digits and always start with +1. It’s right up there with “all users have a US ZIP code”.
Well I'm in the UK so my zip is 90210. :0p
:p
Re: Falsehoods Programmers Believe About Phone Numbers (2016)
#198I have/had a Facebook account with a phone number. The account was left unused for a few years. Recently, I used my E-mail to reset its password, unfortunately, since the account was abandoned for a long time, the system flagged my activity as "suspicious" automatically, and asks me for confirmation using my phone number. But I no longer own that number. And from the customer Q&A forum, I realized I was not the only…
Storytime: I bounce between Japan and Korea for work. I was in Seoul for about a year and a half and naturally had a Korean phone number. I used this number to sign up for Line (a popular chat service in the two countries), and I also linked my email address to the account. So when it was time to move back to Japan, I naturally canceled my Korean phone service. Fast forward 6 months, and my Line account suddenly disa…
Re: Falsehoods Programmers Believe About Phone Numbers (2016)
#199Some people want to put phone numbers in their address books but never ever want to call that person. An example would be to get a name from a number only caller ID so you know not to answer that call.
A flag beside the number to indicate no outbound calls would be helpful. (separate flag for no inbound calls)
Re: Falsehoods Programmers Believe About Phone Numbers (2016)
#200Earlier quoted context omitted.
Not sure why this is getting downvoted. It's a valid point. There is a gap between "technically valid email addresses" and "email addresses that reasonable people use".
Why is this downvoted? Because it violates Postel's law, one of the cornerstones of the technology running the internet: "Be conservative in what you do, be liberal in what you accept from others"
This is a recipe for disaster and code bloat. I met in the past a vulnerability that some irc clients had due to that principle.