Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Post on privacy and security issues in advertising #344

Merged
merged 3 commits into from Feb 6, 2023

Conversation

davidfischer
Copy link
Collaborator

Keywords

Some keywords this post might rank for

  • malvertising, malware advertising, adtech malware, etc.
  • advertising vulnerability, advertising xss
  • blockchain advertising, blockchain advertising malware, cryptocurrency ad malware, etc.
  • brand safety, publisher vetting, keep you safe, keep advertisers safe, etc.
  • ad blockers related to the above things (ad blockers generally is too hard to rank for)

Screenshot

Screenshot 2023-01-30 at 16-46-33 Keeping Yourself Safe from Security and Privacy Issues in Advertising

@davidfischer davidfischer requested review from a team and ericholscher January 31, 2023 00:53
Copy link
Member

@ericholscher ericholscher left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is great content. I think it could be a bit more clear about the risks, but I don't think we need to spend a ton of time on this beyond small tweaks unless it gets a bit more traction. I think we can ship it with a couple small additions 👍

davidfischer and others added 2 commits February 2, 2023 14:43
…ising.md

Co-authored-by: Eric Holscher <25510+ericholscher@users.noreply.github.com>
@davidfischer davidfischer merged commit e787714 into main Feb 6, 2023
@davidfischer davidfischer deleted the davidfischer/privacy-issues-advertising-jpost branch February 6, 2023 23:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants