Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Twitter kills off SMS notifications and posting in most countries

dansdeals.com

Post reply on HN
Print view View original

121–130 of 158 posts

Re: Twitter kills off SMS notifications and posting in most countries

#121

Post by closeparen »

tsimionescu wrote: post #111
hombre_fatal wrote: post #69

Earlier quoted context omitted.

Only if 2FA doesn't open up customer support channels that defeat the point of 2FA, like the common "oops I lost my phone lol" channel attack that gives you access to an account if you can provide the other factor. (Still) works against Amazon btw: https://medium.com/@espringe/amazon-s-customer-service-backd... I'd say 2FA is often worse than 1FA because customer support systems are rarely prepared to say "sorry, can…

That has nothing to do with 2FA, has it? Having a recovery procedure that escalates up tp direct phone contact is the norm with or without 2FA. This system is probably older than the Internet, with banks operating on similar principles (of course, it escalates up to physical presence there).

If the recovery procedure requires only one factor, then “2FA” is a lie.

Re: Twitter kills off SMS notifications and posting in most countries

#122

Post by Avamander »

mlindner wrote: post #113
yepguy wrote: post #37

Earlier quoted context omitted.

That infuriated me last year when I finally tried to create a Twitter account. During registration I was given a choice between providing an email address or a phone number. I provided an email address, only to immediately have my account locked until I provided a phone number. Well, I wouldn't have given my email address if I knew a phone number was required anyway! It wouldn't even let me visit my account settings…

That's pretty interesting. I've had a twitter account that has no phone number and no email for a very long time. It's never been blocked.

If you've had the account for very long it's probably grandfathered.

Re: Twitter kills off SMS notifications and posting in most countries

#123

Post by MaybeNetwork »

jedberg wrote: post #102
munificent wrote: post #88

Earlier quoted context omitted.

It will be a very sad day (for me, at least) when that happens.

I want to say that my reddit usage will go way down, but I know that's probably not the case. On the other hand, I know a few of the old-timers at reddit still use old.reddit, so that might help keep it alive. In theory reddit can rebuild as an alternate front end, or someone else could do it. A good chuck of it is open source. You'd have to do a lot of work integrating the new APIs though.

Reddit's new GQL API uses different oauth tokens than the old API uses, and Reddit doesn't issue those tokens to third party apps. Until that changes, you can't build an alternate front end that has feature (or should I say misfeature) parity with the new site.

It's a shame that the most important chunk of Reddit isn't open source any more. I recently found bugs in both the old API (introduced in 2011, detailed at [1]) and in PRAW regarding bulk flair updates. Since PRAW is open source, I submitted a pull request [1], and their bug was promptly fixed. On the other hand, Reddit is no longer open source, so instead of submitting a pull request like in the old days, I'll have to make a submission to /r/bugs or message the current admins and pray that an engineer sees.

[1] https://github.com/praw-dev/praw/pull/1388

Re: Twitter kills off SMS notifications and posting in most countries

#124

Post by Pxtl »

thirtyseven wrote: post #80
w1 wrote: post #79

Earlier quoted context omitted.

Lol I may or may not currently be using a Twitter account and cron to broadcast any changes to my (non-static) home ip address, encrypted, so I can ssh into my workstation when I'm on vacation.

Are dynamic DNS services no longer a thing?

The big one is gone, but I have good integration between my Asus router and Google domains.

Re: Twitter kills off SMS notifications and posting in most countries

#127

Post by prawn »

arkitaip wrote: post #32
3fe9a03ccd14ca5 wrote: post #13

Earlier quoted context omitted.

On the flip side, the experience is remarkably similar now to what it was a decade ago. It’s materially the same, which is rare for unicorns of this time.

Twitter is getting worse on a monthly basis. Just the fact that they have begun adding random tweets and accounts to follow while you're trying to read an existing conversation makes everything more confusing and toxic.

On desktop, I use https://tweetdeck.twitter.com/ which handles multiple accounts, doesn't have ads and keeps everything in the order I expect. Only thing I wish it had but doesn't is the ability to paste in an image screenshot rather than save and upload from a folder.

Re: Twitter kills off SMS notifications and posting in most countries

#128

Post by dannyw »

pests wrote: post #35
Dunedan wrote: post #24

Earlier quoted context omitted.

For me, an occasional reader without a Twitter account, the experience became much worse in the past decade. That's because Twitter switched of RSS feeds and when opening links to individual tweets nowadays there is this ubiquitous "Something Went Wrong, Try Again" on first page load.

If I'm not mistaken that "Something Went Wrong" is their web API keys being throttled...

It's absolutely absurd that this happens for a site as big as Twitter.

Re: Twitter kills off SMS notifications and posting in most countries

#129

Post by jen20 »

heleninboodler wrote: post #101
icedchai wrote: post #76

Earlier quoted context omitted.

If you try it on wifi, is it still slow?

Yes, as mentioned, it's regardless of what kind of connection I'm on.

I find exactly the same thing with my iPhone too, and often on desktop via the web app. The SPA "loading" page will just spin indefinitely.

Re: Twitter kills off SMS notifications and posting in most countries

#130

Post by ikt »

heleninboodler wrote: post #49
pests wrote: post #35

Earlier quoted context omitted.

If I'm not mistaken that "Something Went Wrong" is their web API keys being throttled...

If this happens to a client attempting to load a single page in isolation (which it does, a lot), you are a failed web site. They may be a very successful mobile app , but as a website, they've failed miserably.

I get this a lot and just assumed it was because I'm using a VPN.
Post reply on HN