275 karma · joined December 2, 2014
For me, this was a full stop dealbreaker. A work around was to create a separate GitHub org just to use with the dockerhub build service, but frankly that’s a terrible hack that just masks the larger problem.
I’ve had the experience searching google maps for bagels, and it returns donut shops. Yes, they are both bakeries, but I wanted bagels, not donuts. In this case I don’t want google to ‘guess’ what I’m searching for; I gave it a pretty specific search term (bagels) in context (google maps), yet the results were imho too smart for their own good.
(I work at Microsoft but have no inside knowledge on this; just speculating.)
If you could control this permission at the app level, many of the privacy issues brought out in the article would be mitigated.
Yes, it would have been be logical to simply redesignate the NJ Turnpike as i95 for its duration, and relabel the highway that goes through Philly with another number, but instead we got the craziness that exists till today.
I still don't follow you; why is this an issue with markdown? Why do you see this as different than any other markup language (e.g, HTML)? Unless we're talking about something like Word documents, you'll have to host the image somewhere, which could be in your github repo. I still don't see why this is an issue.
We talked to the APNIC team about how we wanted to create a privacy-first, extremely fast DNS system. They thought it was a laudable goal. We offered Cloudflare's network to receive and study the garbage traffic in exchange for being able to offer a DNS resolver on the memorable IPs. And, with that, 1.1.1.1 was born."
Disclosure: I work at Microsoft; opinions are mine.
Take lightning cables: I can buy the Apple lightning cable for $25, or I can buy a perfectly good Monoprice, MFi-certified lightning cable for $7, or I can buy a no name, non-certified cable (that will likely have issues) for a buck or two on ebay.