awesome-falsehood VS libphonenumber

Billing. It always has to be the billing. For a list of all other edge cases, you have: https://github.com/kdeldycke/awesome-falsehood#readme

Falsehoods Programmers Believe in: https://github.com/kdeldycke/awesome-falsehood

Also, a list of other falsehood-programmers-believe collections: awesome-falsehood.

> I feel like there's a "Fallacies programmers believe about text" that should exist somewhere

I got you covered.

https://github.com/kdeldycke/awesome-falsehood#international...

http://garbled.benhamill.com/2017/04/18/falsehoods-programme...

https://jeremyhussell.blogspot.com/2017/11/falsehoods-progra...

https://wiesmann.codiferes.net/wordpress/archives/30296

There's an excellent GitHub repo that lists a lot of common falsehoods regarding names. I'm not sure how useful it'll be to OP, but the repo in general should probably have way more attention than it already does.

https://github.com/kdeldycke/awesome-falsehood#human-identit...

A decent list for this about prices and currency https://gist.github.com/rgs/6509585 and the full list of other falsehoods https://github.com/kdeldycke/awesome-falsehood

If you're interested in this sort of thing there's a whole bunch more: https://github.com/kdeldycke/awesome-falsehood

It's saddening to see the number of people who critique the idea of storing time as an unsigned integer by immediately responding that that means that times before 1970 cannot exist. This bespeaks of a continuing poor knowledge of the subject, despite all of the "falsehoods that programmers believe about" documentation that has grown up.

* https://github.com/kdeldycke/awesome-falsehood#dates-and-tim...

Microsoft, for one example, has been modelling times as a 64-bit unsigned 100-nanosecond count since 1601 (proleptic-Gregorian proleptic-UTC) for about 30 years, now.

* https://learn.microsoft.com/en-us/windows/win32/api/minwinba...

Daniel J. Bernstein in the late 1990s chose a 0 point for an unsigned count so far back that it pre-dates most estimates of the point of the Big Bang.

* http://cr.yp.to/libtai/tai64.html

1970 is not the mandatory origin for every timescale. (Indeed, in the early years of Unix itself there wasn't even a stable origin for time.) It is not a valid reason for dismissing the idea of storing time as an unsigned integer.

It's also sad to note that the headlined page's first sentence has one of the very falsehoods that programmers believe about time in it.

libphonenumber can format in many ways, you can find the national patterns in the metadata files https://github.com/google/libphonenumber/blob/master/resources/PhoneNumberMetadata.xml

For instance, the XML file https://github.com/google/libphonenumber/blob/master/resources/PhoneNumberMetadata.xml contains Phone number metadata with possible lengths, broken down by countries.

From falsehoods developers believe about phone numbers :

This makes the assumption that Twitter blocked it due to SMS fraud. While that's a plausible theory an equally plausible theory is that they were worried about account hijacking and security (and allowed twitter blue subscribers to continue to use it on a you can pay me to be stupid context) which seems equally plausible.

I take issue with a lot of the assumptions in the article but this is funny:

> Identify and block premium rate phone numbers, using libphonenumber. Whilst this seems promising, I don’t know how reliable the data and how effective this approach is.

here's this purpose-built and well maintained* library from google which does exactly what I want but i'm not even going to consider it.

* the actual number database has been updated 5x so far this year: https://github.com/google/libphonenumber/commits/master/meta...

Yeah, but you can probably use https://github.com/google/libphonenumber for that.

You can find the Github repo and documentation for the library here.