Google is a for-profit company whose interest is in making money.
953 karma · joined October 3, 2019
Google is a for-profit company whose interest is in making money.
The idea that "This can't be a bug! They must have spent huge amounts of effort making deliberately ridiculous outputs that no one would value!" comes close to clinical paranoia.
That there are bugs in AI training? That when they tried to retrain their model to remove one type of bias, they accidentally went too far the other way?
What's his theory? That Google deliberately "by hand" forced their programs to make ridiculous images so that they would be mocked by absolutely everyone? Does the writer think that people who care about racial diversity are going to be somehow pleased by pictures of Black Nazis?
It's paranoia, but it's also clickbait. We shouldn't give these losers a platform.
The boring truth is that this is not a monetizable query, so Google doesn't really care: and that no one except a few white supremacists captions their family snapshots "White woman with white man".
I might add that this has showed up every few years on social media, always with this same, "Look at how the woke are destroying our search engines!", spin on it.
What if you are writing primarily paragraphs?
What if you want extra blank lines at the end of a block? Or no carriage return at all?
In my reading, unscientifically I feel I see the `>` text formatter most often, then almost as often `|`, then `>-` occasionally, then `>+` just one time.
I can imagine this would have been baffling if I hadn't read about it before. There wasn't actually an elegant solution, but replacing `\n on:` with `\n "on":` was an acceptable hack that took two minutes.
Just one quibble: the reporter was anonymous, so they aren't doing it for prestige. Perhaps it's griefing?
The database isn't really much use unless it's pretty accurate, as few of us have the ability to evaluate correctness.
In this case, where there's an anonymous report, and a clear, near-elementary level explanation of how the code in question cannot be a security violation and has since been removed, the CVE should just be deleted, to save bandwidth for everyone.
I'm glad the `curl` organization is a CMA now, though, maybe that will mitigate the issue.
This is particularly hard now when many sites use images of program code in order to get syntactic highlighting, because your page rewriting extensions do nothing.
(A majority of adults in Europe and Asia also have it.)
One of the side-effects is that light on dark text is harder to read. And now a lot of people seem to use light grey on dark grey, which I can barely read at all, and more, use images of their program instead of text, so tools that rewrite webpages for better contrast can't help.
But mentioning this in a comment thread often gets a wave of abuse. I avoid the temptation to say, "If you're lucky, one day you'll be old like me."
If you want people over 40 to read your writing, please figure out a way to give us a "light mode"! "Today you, tomorrow me."
Interest rates are lower than they have been for most of my life, and close to the average interest rate over the last 700 years.
https://bankunderground.co.uk/2017/11/06/guest-post-global-r...
People have simply gotten used to governments in the last twenty years trying to juice their economies by dropping interest rates more and more.
Reviewing a 50-line code change in 60% of the time it takes to review a 250-line code change means the shorter code review takes _four times_ as long to review per line.
A cynical person might believe that this was deliberate, and wonder why these various "corrections" and law organizations get to police themselves.
> Please don't post shallow dismissals, especially of other people's work. A good critical comment teaches us something.
Do you have some specific refutation to the arguments made in this article? Otherwise, it's unclear what the value of your comment is - you could literally make it about any claim of any side effect of any technology!
The article presents a serious argument as to why this is a possible danger. You don't try to engage with the article, or present a counter-argument.
Given the terrible consequences of weakening the Earth's magnetic field, "We don't know for sure it will happen so we simply shouldn't worry about it," seems unwise.
In some jobs, I always have multiple tmux terminals running. I was about to claim that I have none running right now, but shamefully I have a Mastodon bot that I never productionized running in a tmux on my server.
If you're exclusively a front-end JS developer, it's hard to see how you'd use tmux at all.