4 ms·

The sidebar content should be blockable, but the inline content... they can make that indistinguishable from user content, can't they?

by Touche 10y ago

detaro 10y ago
Which will get them in trouble with FTC and local equivalents for not making it clear what's an ad/"sponsored content".
- amyjess 10y ago
  FTC, actually [0]. I have to wonder if Facebook's anti-adblocking games are going to, at some point, get the FTC to stomp them flat. [0] https://www.ftc.gov/tips-advice/business-center/guidance/ftcs-endorsement-guides-what-people-are-asking https://www.ftc.gov/tips-advice/business-center/guidance/ftc...
  - detaro 10y ago
    fixed, thanks. to many TLAs...
- Touche 10y ago
  Wasn't aware of these requirements, thanks!
CM30 10y ago
Depends. I suspect you could somehow try and parse the content to determine whether it's likely to be an ad, and then block it if so. Yeah that'd get a lot of false negatives, but there has been work into calculating the percentage that a piece of text is an advertisement or fake. Something like Fakespot for ads could be the next adblock integration. Then, the content could be literally identical on a mark up level but still be blocked by the program. At which point, it's another cat and mouse game. How much do you try and 'hide' that something's an ad before the adblocker starts blocking real content? Of course, it's questionable whether trying to hide an ad too much is even 100% legal. Remember, the Advertising Standards Authority and others like them require sponsored posts and content to be clearly marked as ads. So then Facebook ends up in an awkward situation. Do we leave the legally allowed disclaimer (which provides a great ad blocking hook), or remove it and potentially get sued?
- niftich 10y ago
  Why not parse each timeline item to determine the originator? If the originator's name (or some other attribute) matches that of someone on the user's friend list, show the content; otherwise, don't. Using the official Facebook API, doing this is very much possible in a custom client. To do in with a browser addon, you may not always have access to internal user IDs, but can still fall back to imperfect name comparisons, which should still give decent results.
  - Touche 10y ago
    You see more than immediate friend posts on Facebook.
teaneedz 10y ago
Ads, including native, require clear verbiage. Ad blockers will always be able to target that verbiage. https://www.ftc.gov/tips-advice/business-center/guidance/native-advertising-guide-businesses https://www.ftc.gov/tips-advice/business-center/guidance/nat...

The sidebar content should be blockable, but the inline content... they can make that indistinguishable from user content, can't they?

by Touche 10y ago

The sidebar content should be blockable, but the inline content... they can make that indistinguishable from user content, can't they?

detaro 10y ago

Which will get them in trouble with FTC and local equivalents for not making it clear what's an ad/"sponsored content".

amyjess 10y ago
FTC, actually [0]. I have to wonder if Facebook's anti-adblocking games are going to, at some point, get the FTC to stomp them flat. [0] https://www.ftc.gov/tips-advice/business-center/guidance/ftcs-endorsement-guides-what-people-are-asking https://www.ftc.gov/tips-advice/business-center/guidance/ftc...
- detaro 10y ago
  fixed, thanks. to many TLAs...
Touche 10y ago
Wasn't aware of these requirements, thanks!

CM30 10y ago

Depends. I suspect you could somehow try and parse the content to determine whether it's likely to be an ad, and then block it if so. Yeah that'd get a lot of false negatives, but there has been work into calculating the percentage that a piece of text is an advertisement or fake. Something like Fakespot for ads could be the next adblock integration. Then, the content could be literally identical on a mark up level but still be blocked by the program. At which point, it's another cat and mouse game. How much do you try and 'hide' that something's an ad before the adblocker starts blocking real content? Of course, it's questionable whether trying to hide an ad too much is even 100% legal. Remember, the Advertising Standards Authority and others like them require sponsored posts and content to be clearly marked as ads. So then Facebook ends up in an awkward situation. Do we leave the legally allowed disclaimer (which provides a great ad blocking hook), or remove it and potentially get sued?

niftich 10y ago
Why not parse each timeline item to determine the originator? If the originator's name (or some other attribute) matches that of someone on the user's friend list, show the content; otherwise, don't. Using the official Facebook API, doing this is very much possible in a custom client. To do in with a browser addon, you may not always have access to internal user IDs, but can still fall back to imperfect name comparisons, which should still give decent results.
- Touche 10y ago
  You see more than immediate friend posts on Facebook.

teaneedz 10y ago

Ads, including native, require clear verbiage. Ad blockers will always be able to target that verbiage. https://www.ftc.gov/tips-advice/business-center/guidance/native-advertising-guide-businesses https://www.ftc.gov/tips-advice/business-center/guidance/nat...