Hacker News new | past | comments | ask | show | jobs | submit login

If your stack is so deep that you're worried about serving malware to users for them to execute, you might want to put a warning on your site so users understand the risk before executing scripts.

The fact that the above sentence sounds unrealistic nowadays is extremely depressing. If malware distribution through web browsers wasn't already the norm, it'd look like common sense.




Aside from the stack, I also mentioned a marketing department doing something the tech department wasn't aware of. It happens.


If the tech department needs to protect users from the marketing department and can't approve or advise changes the marketing department does, then this is a good short-term solution. Fixing the organizational issues would be a good long-term solution.

I do admit that "a visible vote against FLoC" is a good reason to put this header; I've updated the article.

Diff: https://git.sr.ht/~seirdy/seirdy.one/commit/155d4f7b915f9f04...

I don't think these votes will sway Google but I do think they'll spread awareness. I still think that a better use of our time is getting users off Chrome.




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: