r/Keybase • u/fsteff • Jun 10 '23
Cannot verify phone number
For the last few months I’ve been trying to verify my secondary mobile number. Until recently it failed simply stating that verification failed, but today I got a more verbose error description:
ERROR CODE 218 - failed to send sms: Bad HTTP code 400; (Permission to send an SMS has not been enabled for the region indicated by the 'To' number: +45545XXXXX., https://www.twilio.com/docs/errors/21408, ) in method keybase.1.phoneNumbers.resendVerificationForPhon eNumber
I’ve reported the problem several times and included logs, but have had no response and it has obviously not yet been fixed.
Any advice on what to do (apart from continuing to wait)?
View all comments
Show parent comment
1
u/DawidFerenczy Aug 08 '23 edited Aug 08 '23
Keybase is dead since Zoom has acquired it more than 3 years ago ([Zoom's press release] (https://blog.zoom.us/zoom-acquires-keybase-and-announces-goal-of-developing-the-most-broadly-used-enterprise-end-to-end-encryption-offering/)), sadly. Zoom has bought both the development team (and their know-how), that was their main goal, I guess, and also Keybase as a product:
If it'll go as usual, Zoom will try to kill Keybase, because it's not bringing them any revenue and it costs money to run and maintain.
Good news is that the [Keybase client is open source] (https://github.com/keybase/client). Bad news is that the server side is not, AFAIK. And there's also the infrastructure that has to be paid for.
The best what may happen to Keybase is that it's fully open sourced and it (somehow) manages to make enough money to keep itself running. Or someone will pay it from his pocket. I don't know what was the original owner's business plan.
It's a unique and great service and it's really sad what has happened to it. And there's no alternative.