This obsession with making every single website a hugbox these days is moronic. The word retard/retarded is seldom associated with actual retardation instead it's just a synonym for moron.
Even if you dissagree with that you should still be able to see that even if we did s/retard/moron/ or replaced it with git, idiot etc it would still violate the TOS.
No, they aren't. Git means "bastard", which I find awfully discriminatory towards people brought up by single parents. How will they ever feel comfortable in contributing to open source if all open source development happens on Github?
You're a bastard - in the strict sense - which is uncommonly used nowadays, other than mischievously - if born out of wedlock. Being brought up by a single parent is a separate matter.
I misspoke when I implied that all children brought up by single parents are bastards. In any case, my point stands. Github makes children born out of wedlock feel unwelcome and they should change their name.
Git may be a synonym (sort of) for "bastard", but not for all of its meanings. I doubt anybody would link "git" to birth out of wedlock.
(Judging by this particular hoohah though it may be true though that Github might eventually turn out unwelcoming to those fitting definitions #2 or #3 from the above link.)
It's not about meaning, it's about usage and impact. Slurs like "r@t$rd" are used against people with mental health issues and make it hard for them to participate in such spaces.
Offence is meaningless. White people are occasionally offended by 'cracker', rich people by other terms, but they don't cause material harm to them. But people of colour are hurt by words like 'n$@!%r".
Words themselves have no meaning. The meaning is derived by the intention and context. It is perfectly correct to use nigger in some context. Just look at Louis CK or George Carlin. Actually George Carlin made a bit about the word nigger and he made pretty good arguments against the American obsession with "bad" words. The Americans have a very childish attitude towards this, I haven't seen any country were adults refer to words by their first letter.
As if somehow euphemism make everything ok, even though you say 'n$@!%r", you are still saying nigger.
Linguist here: you haven't seen much, this "obsession" is inherent to language itself and has a name of its own: connotation. Connotation is everything associated with a word, denotation is what the word actually means. But denotation doesn't override connotation, they coexist. If anything, connotation can change denotation, while connotation changes independently from denotation.
So what's the difference between saying nigger and meaning nigger? When you're saying nigger, you give away the option of not meaning nigger, because you cannot use the word free of its connotation: it's there, no matter how you use it. Dogwhistle terms used instead of nigger do not have that universal connotation to them, which is precisely why they are used: they can slip under the radar.
So what to do? Honestly, this is extremely simple: don't say nigger if you don't want people to equate what you're saying with the connotation your words carry. And the same goes for retard: if you don't want people to equate your words with the hate directed at people with mental health issues, don't use words whose connotation is limited to that hate. The denotation of "Sieg Heil" is completely harmless, but you have no problem with understanding its connotation and you don't go around saying it when the denotation fits because you know that only Nazis say "Sieg Heil".
Well, only assholes say retarded or retard. That's the connotation you're associating yourself with and no matter how much you complain about being misunderstood and people being too PC, you just messed up by not paying attention to the connotation of the word.
Oh, so when someone calls me a totally racist and offensive slur against white people it causes no harm, but when white people call blacks what they call each other all the time it hurts them... definitely makes sense.
They use cameras for counting free spaces as they mention in the video. Nothing is said about security. Having cameras does not mean you have actual recording and surveillance.
(I'm the CTO of LumiGuide who developed this system).
We're currently not using the system for video surveillance. Images from the cameras are only stored in memory for a short period of time while being processed by our CV algorithm.
However, since bicycle theft is a common theme in the Netherlands, there's strong interest from municipalities for using our system for video surveillance. So we're now researching how to extend our system for doing that.
Actually, from the article, the opposite is expressly mentioned: ..."The sensors look like cameras, but the images are not captured or saved, so the cyclist’s privacy is not violated.”
Great to see that Python3 support for frameworks such as Flask and Django are catching on. I personally feel that the big frameworks should push more when it comes to the adaption of Python3. The only reason I ever still use Python2 is because of frameworks such as Twisted[1] not supporting Python3 yet.
This looks pretty cool. Although I do not understand why I would have to sign up on the website. The demo makes it look like it's a minimal-config command line tool. Instead the website makes it look like it's a service and there is no clear indication who stores my creditcard info etc. on the front page. This is explained in the FAQ though. A quick notice about stripe processing payments on the front page would be nice.
True, the demo doesn't show the sign up process, but you only have to sign up once and after that, buying certs is as simple as in the demo. (And the sign up process is itself very quick.)
Thanks for the feedback about the credit card processing information. I'll think about how to make that information more prominent.
This special syntax should be discouraged for any strings that shall be translated in the future. Different languages have different syntax, so the order can change, with this kind of syntax, you will be in big trouble very soon!
For anything translated, you'd use the (admittedly gross, fixed in Python3) "Welcome %(who)s to %(place)s" % { 'who': who, 'place': place }. The Python3 version is "Welcome {who} to {place}".format(place=place, who=who), or if you want to be un-idiomatic and unsafe, "Welcome {who} to {place}".format(locals())
It's easier to see the point with more variables being interpolated where it becomes cumbersome to keep track of the order and you end up recounting everything multiple times when something's out of place.
You wouldn't take Google seriously? I'm sure they didn't fork out just for today, they will be using it for their products at some point.
In a few years, it will probably the standard domain for big corps. iphone.apple, macbook.apple, etc. It looks weird now (or an intranet address at best), but once people get used to it, it will be recognisable as a domain just as any.com is now.
Not to mention, an explosion of TLDs for reselling (.futbol .enterprise etc) means people will just equate . on billboards etc with a domain.
The fact that a company needs their own gTLD is silly. Sites like google have a perfectly good domain. Why use iphone.apple if apple can already do iphone.apple.com or apple.com/iphone? At the end of the day the consumer will not start guessing what domain he/she has to use to get what they want. The average consumer uses a search engine and types in "apple iphone". They don't care about iphone.apple they just want to go to the product page.
Well, it's not about need. It's about a story that goes like this:
ICANN: Hey, has anyone noticed that our wallets aren't
very heavy?
Google: We have a bucketload of money just laying around
that will fill your wallets, and wouldn't mind
our own gTLD. It'd be cute.
ICANN: You had us at 'bucketload of money'
We needed more gTLDs anyway. So what if a few mega-companies get their own versions?
> Google isn't going to abandon their perfectly good domains.
Good thing icann just increased the available domain-space from "limited" to "unlimited" then. That sounds good for almost everyone, or at least icann.
The TLD system is arguably broken, because it never turned out as hierarchical as it was supposed to. All the new TLDs do is force people to shell out more money to squat on pointless domains to avoid them being used for fraud (or, worse, by the competition).
Not happening in my experience. As long as everyone in the industry is earning their share from this madness they'll happily "suggest optimizations to the domain portfolio" of their vict^Wcustomers.
This battle was lost the second people started using .net and .org for things that wheren't related network technologies and non-profit orgranizations respectively. The nail was driven into the coffin when people started using country tld's for sites that had nothing to do with that country.
If anything this might be step back in the right direction. Whereas I cannot tell anything about the nature or origin of a site based on the fact that it has a .net or .ly tld, I will be able to tell something about nature and origin of a site if it has a .google or .apple tld.
More generally, as part of ICANN's gTLD approval process, if the gTLD being applied for is a trademark, then it can't go to anyone else besides the trademark holder. So there's actually a lot more assurances that you are dealing with who you expect to be dealing with with gTLDs versus random domain names on .com.
Honest question, trademarked according to who? The Internet is a global thing now, so who wins if there's two entities that happen to both have valid claims to a trademark?
What kind of lunatic would pay that kind of money for a dev for a single week