Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Washington Post's Privacy Tip: Stop Using Chrome, Delete Meta Apps (and Yandex)

tech.slashdot.org

Post reply on HN
Print view View original

141–150 of 346 posts

Re: Washington Post's Privacy Tip: Stop Using Chrome, Delete Meta Apps (and Yandex)

#141

Post by labster »

timewizard wrote: post #19
ninth_ant wrote: post #9

Earlier quoted context omitted.

A media outlet which depends on ad revenue as a primary income source is unlikely to suggest this. Ditching these deeply invasive products remains a good idea, independent on any decision to use ad blockers or not. The Meta/Yandex incident in particular is straight-up malware and everyone should remove their apps.

> which depends on ad revenue They're more tightly bound than that. They're dependent on Google Display Ads. Which really makes their whole diatribe that much more pathetic. Any media company that decided to traffic the ads themselves, from their own servers, and inline with their own content, would effectively be immune from ad blocking. > Ditching these deeply invasive products remains a good idea While still allow…

Hosting the ads on the same server as the content is done in some cases, but doesn’t result in any immunity. If the ads are sufficiently annoying, it only leads to a merry little game with the adblocker annoyance list community, where they figure out new regexen to block the content, deploying daily. Bypass the blocks too effectively, and the adblocker will accidentally start blocking website content. Users will assume the website itself is broken, and visit less.

Self-hosting ads is not really a winning game unless your ads are non-animated, non-modal static text and images.

Re: Washington Post's Privacy Tip: Stop Using Chrome, Delete Meta Apps (and Yandex)

#142

Post by paulryanrogers »

arealaccount wrote: post #101
t-writescode wrote: post #92

Earlier quoted context omitted.

I'm a relatively new web dev and I've been quite happy with Firefox's Web Dev tools. What does Chrome's dev tools give someone that Firefox's doesn't? I can edit css on the fly, see where a css rule is being overwritten, debug javascript, etc.

FF dev tools just don’t work sometimes, notably with iframes, sometimes with source maps, and other edge case types things. I use FF for 99% of dev, open Chrome maybe once a quarter. It’s a better browser.

Funny, I find Chrome Dev tools doesn't save some response bodies, while Firefox consistently does.

Re: Washington Post's Privacy Tip: Stop Using Chrome, Delete Meta Apps (and Yandex)

#143

Post by 1vuio0pswjnm7 »

alkonaut wrote: post #119
ninth_ant wrote: post #9

Earlier quoted context omitted.

A media outlet which depends on ad revenue as a primary income source is unlikely to suggest this. Ditching these deeply invasive products remains a good idea, independent on any decision to use ad blockers or not. The Meta/Yandex incident in particular is straight-up malware and everyone should remove their apps.

Getting privacy advice from an adtech funded outlet sounds like reading democracy advice from the Chinese ruling party or vegetarianism advice from lions to be honest. It might be correct-and-incomplete but they just have no credibility on the topic.

Many HN commenters work for "adtech funded outlets". Do they have any credibility on the issue of privacy.

Re: Washington Post's Privacy Tip: Stop Using Chrome, Delete Meta Apps (and Yandex)

#144

Post by sertsa »

someNameIG wrote: post #109
kstrauser wrote: post #62

Earlier quoted context omitted.

Wikipedia says Safari’s their #2 browser, with 17% traffic share: https://en.wikipedia.org/wiki/Usage_share_of_web_browsers Web devs ignore Safari at their own risk, lest 100% of iPhone users be unable to use their site.

If Apple wanted more web devs to support Safari they should port it to Linux and Windows. The web is supposed to be an open standard, you shouldn't need a devices and software from a specific manufacturer to develop for it (I say that posting from a Mac).

At some point there was a Safari for Windows.

Re: Washington Post's Privacy Tip: Stop Using Chrome, Delete Meta Apps (and Yandex)

#145

Post by hungmung »

1vuio0pswjnm7 wrote: post #143
alkonaut wrote: post #119

Earlier quoted context omitted.

Getting privacy advice from an adtech funded outlet sounds like reading democracy advice from the Chinese ruling party or vegetarianism advice from lions to be honest. It might be correct-and-incomplete but they just have no credibility on the topic.

Many HN commenters work for "adtech funded outlets". Do they have any credibility on the issue of privacy.

Individually they might, but I wouldn't take advice from their employers.

Re: Washington Post's Privacy Tip: Stop Using Chrome, Delete Meta Apps (and Yandex)

#146

Post by soraminazuki »

thadk wrote: post #93

Anyone have tips on how to avoid having the WhatsApp app on your phone?

Remove lock-ins that forces people to use a specific chat app. Move private communication away from "platforms" to interoperable protocols. That is the only way for us to regain control over our own private communications.

Re: Washington Post's Privacy Tip: Stop Using Chrome, Delete Meta Apps (and Yandex)

#148

Post by elendee »

t-writescode wrote: post #92
m-localhost wrote: post #84

Zen Browser (FF) on Win and Firefox on iOS (for sync) works well for me. Edge for all M365 related stuff. Still use Chrome for web dev. Not sure what to move on in that regard...

I'm a relatively new web dev and I've been quite happy with Firefox's Web Dev tools. What does Chrome's dev tools give someone that Firefox's doesn't? I can edit css on the fly, see where a css rule is being overwritten, debug javascript, etc.

firefox doesnt have Workspaces. I do 100% of my CSS in Chrome Workspaces

Re: Washington Post's Privacy Tip: Stop Using Chrome, Delete Meta Apps (and Yandex)

#149

Post by duxup »

turtletontine wrote: post #65
duxup wrote: post #35

Earlier quoted context omitted.

I feel like that's like saying "it's fine, except for the bad part that you can't avoid" ;)

The future of Google as Chrome’s owner is genuinely in question now due to Google’s antitrust losses, in case you weren’t aware. There’s a few different cases, one recent one Google has lost and is now in the “remedy” phase. Meaning the court has officially decided Google did bad, and is now considering what to make Google do about it. And splitting up Google into separate Chrome, search, etc companies is completely…

I'm aware, but it doesn't change day to day choices for now.

I'm also completely at a loss to imagine how chrome becomes someone else's play thing and is somehow less prone to serving advertisers.

Re: Washington Post's Privacy Tip: Stop Using Chrome, Delete Meta Apps (and Yandex)

#150

Post by paradox460 »

jonhohle wrote: post #122
timewizard wrote: post #19

Earlier quoted context omitted.

> which depends on ad revenue They're more tightly bound than that. They're dependent on Google Display Ads. Which really makes their whole diatribe that much more pathetic. Any media company that decided to traffic the ads themselves, from their own servers, and inline with their own content, would effectively be immune from ad blocking. > Ditching these deeply invasive products remains a good idea While still allow…

It’s odd that orgs like NYT don’t run their own ad services. I’m sure they have a dedicated department for ad sales for physical copies. They’re large enough that companies would work directly with them. And they would have at least some editorial control on what is displayed on their site.

I've worked for a few companies that had ad placements. I wasn't too deep into that side of things, and it was a long time ago, but as I recall, at reddit there was an in house ad auction platform. If there wasn't any ads sold for the period, we'd either show in house ads (think the old reddit merch store, pics of animals, a pic of one of the reddit staff with a paper tube on his forehead to resemble a narwhal, etc) or ads from a network like AdSense. Once upon a time this actually caused issues because there was malware being served from one of those and networks
Post reply on HN