Hacker News new | ask | show | jobs
by notwhereyouare 1243 days ago
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
1 comments
MrOwnPut 1243 days ago
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.

link
Nextgrid 1243 days ago
> 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.

link
MrOwnPut 1243 days ago
Certainly, but the second you get a rouge actor, your advertisers are 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.

link
robryan 1243 days ago
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.
link
MrOwnPut 1243 days ago
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.

link