News for hackers. Stuff that matters.
Re:Tweetbot. April 2011 – January 2023 by nomel on Friday January 20, 2023 @03:06PM (#34459033)
> filled with ads and irrelevant clutter.

I always assumed the third party clients just provided a better interface. I didn't realize they circumvented the income stream.

If the third party clients were removing the means of monetization, for a company who struggles to profit, then it seems obvious that requiring paid access on its way, regardless of the owner. Twitter can't go forever at a loss.

The "surprise" is surprising.

Re:Tweetbot. April 2011 – January 2023 by notwhereyouare on Friday January 20, 2023 @03:13PM (#34459146)
I think it's more that the API didn't return the ads to the client. If they required 3rd party clients to include the ad's in the feed and grounds for termination of the API key if they weren't that would be a different story
Re:Tweetbot. April 2011 – January 2023 by MrOwnPut on Friday January 20, 2023 @03:53PM (#34459787)
What service does this? There are very strict rules in showing ads.

Making sure you're not showing them by nsfw content, etc. or your advertisers will pull out.

I can't think of a single service that provides ads for 3rd party clients to use.

Most are hostile to 3rd party clients due to threatened ad revenue, that's why there's invidious, nitter, etc. whackamole.

Re:Tweetbot. April 2011 – January 2023 by Nextgrid on Friday January 20, 2023 @04:39PM (#34460333)
> Making sure you're not showing them by nsfw content, etc. or your advertisers will pull out.

Which you can control by just returning the ads as part of the API response for the feed, which I'm sure how the official client does it. Making the client classify NSFW content and hide ads based on that seems like a stupid idea.

Re:Tweetbot. April 2011 – January 2023 by MrOwnPut on Friday January 20, 2023 @05:26PM (#34460948)
Certainly, but the second you get a rouge actor, your advertiser is going to be pissed.

At the very best the rouge app won't display ads.

At the worse, they'll ignore a nsfw tag and won't show the spoiler overlay, angering your advertiser.

Audits can catch it, but only after the damage is done.

I don't think there's any service that lets their ad supported plan be in the hands of a 3rd party client.

Re:Tweetbot. April 2011 – January 2023 by robryan on Friday January 20, 2023 @05:06PM (#34460701)
Enforce it on clients over a certain number of users where they are big enough to manage following a bunch of rules around the ads. Then they can be audited to make sure they get doing it correctly.
Re:Tweetbot. April 2011 – January 2023 by MrOwnPut on Friday January 20, 2023 @05:22PM (#34460910)
Yeah it can be done with X amount of risk and auditing ($)...

I was mainly asking has it been done by any service?

Risking your advertisers is not wise and audits will be expensive and reactive not proactive.

Re:Tweetbot. April 2011 – January 2023 by croes on Friday January 20, 2023 @04:25PM (#34460134)
Without the debt Musk put on Twitter they could at least go longer
Re:Tweetbot. April 2011 – January 2023 by dragonwriter on Friday January 20, 2023 @04:28PM (#34460198)
> Twitter can’t go forever at a loss.

But for nonrecurring expenses, Twitter was profitable before Musk’s buyout both torpedoed ad revenue (when it was announced, before it was even completed) and saddled it with massive expenses to finance the buyout.

The acquisition is literally the only reason it is any concern how long Twitter can operate at a loss.

Re:Tweetbot. April 2011 – January 2023 by nomel on Friday January 20, 2023 @09:41PM (#34463294)
> Twitter was profitable before Musk’s buyout

My mistake. Last I looked was 2020, when they were down about $1B.