Just learned about Brave for the first time. Pretty neat stuff.
Only if you're into cryptocurrencies. I wish there was an alternative without the BAT stuff.
That makes no sense. BAT is opt-in and isn't even mentioned when you install the browser.
Google’s GDPR Workaround
251–260 of 629 posts
Re: Google’s GDPR Workaround
#252Earlier quoted context omitted.
The matching is in itself a violation of privacy, at least if you interpret the right of privacy as "The right to be left alone", as former Supreme Court Justice Louis Brandeis put it.
I think that’s incorrect, relevant ads could be displayed based purely on the site content, without user info attached to ad calls. We’ve been there.
Why the downvote? Care to provide a reason?
Re: Google’s GDPR Workaround
#253Earlier quoted context omitted.
You mean how there are somehow always commenters in every topic ready to leap to the defense of China and major US tech companies?
I would guess that those are, more often than not, not paid shills but rather just people who like taking devil’s-advocate sides in arguments “for fun”, i.e. just for the challenge of seeing if they can construct a valid rebuttal to a comment. (I say this because I believe I’ve done this myself more than once, and I know my personality-type isn’t uncommon on HN.)
At least in the case of corporate defense, most of them are the "free market solves everything" types who believe that if completely left alone, business will turn the world into some utopia.
Re: Google’s GDPR Workaround
#254Earlier quoted context omitted.
"somebody looking over your shoulder" can see a lot more than you ads, like your private messages, bank info, medical info, etc.
Not if I'm just showing them a random website. The problem with targeted ads is, they show up at random websites.
I dunno man. This reminds me of the time that someone at defcon said they found a vulnerability in my last company's product because it flashes a WiFi password to an iot device instead of making a user type it in.
"What if we capture the flashes and steal the password?"
Well, if you're positioned to capture the flashes, you're definitely positioned to just watch me type it in...
Re: Google’s GDPR Workaround
#255>I was branded as a 'privacy nut' Companies do actually employ shills to go on forums and try to sway public opinion. They call them something like public advocates, doesn't change the idea though.
> Companies do actually employ shills to go on forums and try to sway public opinion I'm inclined to believe you, but sources please. Especially interested if you (or anyone) have anything on Google in this respect.
Amazon employees what it calls "FC Ambassadors". These people have openly admitted that they are paid by the hour to tweet about the company[0].
Full thread in a nicely readable format at https://www.thepoke.co.uk/2019/08/15/amazon-ambassadors-take...
[0] https://twitter.com/rulesObeyer/status/1161758672973811712
Re: Google’s GDPR Workaround
#256Do they have to prove that the RTB ID can be used to retrieve PII? Or only that the RTB ID is correlated with personally protected information? Is it enough that a RTB ID is pseudo-anonymous? (it always identifies the same person, but cannot be used to find that person's real information) - OR - is a RTB ID not even pseudo-anonymous?
GDPR definitions are slightly different.
A person is identified, if the ID references only one user in the whole dataset[1]. This also makes any information linked to the ID PII.
the ID would be pseudo-anonymous if one would need some extra data, to which they don't have access to, for linking the ID to one specific user in the whole dataset[2].
So to answer your question, RTB ID is not pseudo-anonymous as it only references a single user out of all of them.
[1] It's also important to understand the definition of PII in GDPR context. Which is any data that relates to an identified or identifiable person. Identifiable is the same as distinguishable. Knowing this helps to understand where the line is. https://www.lexico.com/en/definition/identifiable
[2] Definition of pseudonymisation, 5'th bullet-point: https://gdpr-info.eu/art-4-gdpr/ sheds some light on this.
Re: Google’s GDPR Workaround
#257Earlier quoted context omitted.
Yep. Privacy violations and leaks should be punished with fines and jail time. Period. End of sentence. Just like execs have to personally sign for and are accountable for their financial statements, they should do the same thing with privacy. GDPR sets a very common leveling of the field so it's completely fair now.
"Privacy violation" is a huge, gigantic category of all kinds of things. One kind of privacy violation is completely different from another; some privacy violations are completely harmless, and some are actually directly harmful, and some in between. Giving jail time for any of these is like giving jail time for any kind of "offensive behavior". Maybe someone just didn't like what someone said and called it offensive…
I specifically mentioned GDPR not something nebulous or not well defined. It's a level field. It appears Google has violated the GDPR, willfully even. I have no problem with execs going to jail over that.
Re: Google’s GDPR Workaround
#258Re: Google’s GDPR Workaround
#259Earlier quoted context omitted.
The most interesting thing to me about that McDonald's "hot coffee" lawsuit is how different the narrative is in popular circles vs. in legal circles. It's a little bit like in Rashomon . In popular circles, the story is framed in a way that does make the lawsuit look frivolous. But this is also a case that has made it into the legal textbooks as an example of corporate negligence that's clear-cut enough to use for d…
Are you a lawyer? Because this take is quite remarkable, especially given that the overwhelming public sentiment is that McDonalds was heinously negligent, coupled with a lot of supporting but not entirely factual claims to justify that position. I feel like the same people who were jeering at the victim just marched over to sainting her and demonizing McDonalds. The Internet extreme position machine. Everything has…
The standard temperate you brew coffee at is 200F, less if at high altitude. McDonalds coffee is served at 180-190F and brewed at something higher than 200F and lower than boiling.
Typical coffee serving temperature is 155-175F. I'm considered unusual among my friends for being able to sip 170-180F coffee. 190F is just way too hot.
Re: Google’s GDPR Workaround
#260Earlier quoted context omitted.
Only if you're into cryptocurrencies. I wish there was an alternative without the BAT stuff.
That makes no sense. BAT is opt-in and isn't even mentioned when you install the browser.
I would argue that the whole reason for Brave's existence is BAT. It's their business model and I'm surprised that HN normally hates cryptocurrencies with a passion but gives Brave a pass.