1,067 karma · joined August 15, 2012
If this is a sarcastic post, well done!
Curious though how your house cleaner is making more than a software engineer?
1. All other browsers' private/incognito modes behave the same. Then why do they expect Chrome to behave differently? Is the complaint about Google Analytics collecting data, or about Chrome making false promises?
2. It never explains how the information sent to Google Analytics can be tied to your person. A public IP address is generally not good enough. Forensically maybe, when combined with ISP logs, but not routinely at scale.
3. It asserts that Google is using this information "nefariously", without going into detail: "This does not mean that Google does not utilize and/or monetize this data in any way. Google does. It merely changes the form of storage after the data has served Google’s nefarious uses."
4. It points out that this kind of information is so valuable to Google that they run a program where they pay people to observe their behavior. But, the whole complaint is about how Google collects that information already. Why have a separate program where they pay users?
5. Classifying visiting a website in incognito mode as "confidential communication" is a bit of a stretch, but that's the centerpiece of their complaint.
[1] https://www.classaction.org/media/brown-et-al-v-google-llc-e...
Disclosure: I work for Google, but not in Chrome or GA. The opinions expressed in this post are mine.
It is part of Google's culture to not blindly agree with leadership on every issue and you're encouraged to voice differing opinions, but I guess some take this too far in the other direction and assume that every kind of negative feedback is appreciated and "protected".
1. Germany doesn't have TLDs like ".edu", and it became a de-facto standard to construct higher education domains by abbreviation of type of school and location: www.[uni|fh|...]-[location].de
2. Dashes in a URL emulate spaces, and in German, without spaces a phrase is often ambiguous. Example: "Gehweg" = sidewalk, "Geh weg" = get lost! Even in English, I often think a domain name would be easier to parse with dashes, e.g. "calstatela.edu" vs "cal-state-la.edu".
3. There's a strong compulsion ingrained in almost every German to be orthographically correct, and delimiting words correctly is a big part of that.
The contract[1] states that these are tax credits pursuant to Wisconsin State statute 71.28(3wm)[2], which states "If the allowable amount of the claim under this subsection exceeds the taxes otherwise due on the claimant's income under s. 71.23, the amount of the claim that is not used to offset those taxes shall be certified by the department of revenue to the department of administration for payment by check, share draft, or other draft[...]"
So if Foxconn meets the investment and job creation requirements and doesn't have significant state tax burdens, the Wisconsin tax payers will have to write big fat checks to Foxconn, hoping that the indirect economic impact of Foxconn's activity is enough to offset these payments. In that case, these subsidies are a direct cost.
[1] https://wisconnvalley.wi.gov/Documents/WEDCcontract-state.pd... [2] https://docs.legis.wisconsin.gov/statutes/statutes/71/IV/28
"Travel-related activities of e-bikers who switched from cycling decreased by around 200 MET min/wk., while those switching from private motorized vehicle and public transport gained around 550 and 800 MET min/wk. respectively."
If that still doesn't work, check other related autoplay settings, like `media.autoplay.ask-permission`.
With AMP though, any content (even ads) is funneled through a proxy CDN (the AMP cache), so ads are indistinguishable from regular content with this method.
The problem is not that they wouldn't be able to parse the cookie, it's that Akamai edge node web server (Nginx or Apache, don't remember) rejects any request with a header that's above a certain size. Your origin server doesn't even get to know that there ever was such a request.
See https://maxchadwick.xyz/blog/http-request-header-size-limits for example.
So that clause means that the plaintiffs will get up to $5,000 on top of what they will receive as claimants, and there is no such limit on claims (but the total payments will not exceed 11 million, including attorney and class representative compensation).
EDIT: see below for correction
> "This is just not true", "I don't believe you"
Those sentences stood out to me as well. Maybe I'm too conflict-averse, but in a professional setting I would rarely use sentences like this. Something like "Are you sure about that? I've read differently. Let's verify/look into that." gets the same message across and everyone saves face.And I'm coming from a cultural background that's known to be very direct and blunt...