We’ve been forced to pull Twitterrific from the app stores

Nitter + an RSS app like Vienna is a neat solution for replacing Twitterrific on desktop.

The UX isn't as good, particularly with quote tweets just showing up as links instead of embedded in context.

Also I had to write a quick browser hack so if I open a tweet from the RSS reader to Nitter it will make it so there is a link to the original Tweet from Nitter so I can actually interact with the tweet (like, reply, etc).

But it works, it lets me see things chronologically, and it tracks which are read and unread. Thanks!

Works great, but the time to add each RSS was the only downside. Was easier to write a loop script to feed it a list and have it grab rss feeds for each user.

Podcasts are just rss feeds too.

[0] https://github.com/nuclearfog/Shitter/releases/tag/3.0.1

For example, most ad-funded websites post content to Twitter, even though Twitter sells ads too. Why? Because tweeting drives additional traffic, which creates a net gain in ad dollars for the site. Despite the seeming direct competition for ad dollars, both Twitter and websites have made more money by working together.

The argument for Twitter client apps is that Twitter needs free content to sell ads against, and many of their most prolific tweeters loved the client apps. Now Twitter will get to see if killing apps reduces tweet content quality or quantity enough to notice.

Counterpoint would be that Twitter grew (partially) due to it's easy to use API. And one could argue that Twitter has a monopoly on short message social media because of this growth. Thus being anti-competitive by suddenly disabling its API.

It's not "[twitter's] own data". Full fucking stop.

It's the data of the users on the platform. In the same way that the texts I send are NOT my carrier's data, and the emails I send are NOT my email provider's data, and mail I send is not the postal service's data. It's mine. They are simply holding it.

The alternative to pulling this data from the api is to simply scrape it from the site. And there are many (very legal) ways to do this. Although they come with some notable downsides (everything from forcing a user to download a browser extension, to having to ask the user for their credentials).

They also carry downsides for twitter - scraping may not be efficient for them.

So the API is the compromise: I can get access the data I could anyways using the automations I'd prefer, but in a manner that allows Twitter to moderate possible downsides for themselves.

Broadly speaking - this is the legal structure twitter (and google, and all sorts of other sites based on user content) operate under. They are not the legal publisher of the information. They may be granted a right to copy and reproduce the information to facilitate the operation of the service, but it's not their info. Period. if it were... they could be in a fuck load of hot water for anything they allow to be posted to the site.

So - while they're under no obligation to build an API... it's a compelling way to improve the user experience, moderate the consequences of scraping, and increase engagement and activity. Because at the end of the day - that information is already available to users.