Seems to be the only big change - this was added to a list of 'thou shalt not's:
"use or access the Licensed Materials to create or attempt to create a substitute or similar service or product to the Twitter Applications"
Goodbye, nitter(?)
"use or access the Licensed Materials to create or attempt to create a substitute or similar service or product to the Twitter Applications"
Goodbye, nitter(?)
That would be devastating for me. Not only it's the only way of looking at anything on Twitter (I invite you to open a thread on mobile. I get 3 modals covering 95% of a screen) but it's also how I follow some accounts via RSS.
Because it's superior technology for following posting/news to opening app and praying that algorithm will show me what I wanted? My feeds flow to me at 6:00, via rss2email, and get filtered into a IMAP folder and I can read them at my leisure. Online or offline, with whatever client I have handy.
> this is a pretty good user signup strategy
Nagging only works if I really, really want to see what you hide behind a login screen. For most of the posts on Twitter it won't be worth it.
What do you propose instead?
> Reddit does it, Instagram does it
One website known for its hilariously broken performance and a Facebook subsidiary. Nothing anyone should look up to.
Better question is: why not?
Gen Z? Or just not familiar with the technology? Protocols don't die just because the newer generation doesn't understand them.
- IG it's crapware and unusable with tons of propietary JS.
At least for me - I leave. Or in the case of reddit, occasionally use old.reddit.com, which does not block without an account.
I got this article via my RSS client; it's the best way to consolidate everything I follow from YouTube videos to things that hit the front page on HN, all in one place.
Then I can browse through doing my morning coffee.
I doubt that Twitter is interesting enough for people who just want to view
Goodbye all methods of accessing Twitter outside of their apps. They took down their API and bypassing this move via internal API's or scraping output via a headless client (thinking of ways forward for Nitter) will surely be seen as intentional to violate this. So, I guess this is the end then.
What are the odds that this whole imbroglio happened because their third-party APIs broke and they can't figure out how to fix them?
The slack convo leak would have been the same either way.
It really has a strong smell of protect-my-ego.
Nitter will be fine and will gain more relevance as a result of this.