It’s best to stay away from broadly controversial topics that attract masses of non-experts. These people have no idea what reasoned debate is all about, so there’s no point in subjecting oneself to such an assault.
> I am actually a bit worried that I’m already starting to see search engine traffic coming in...
We can discuss hypothetical systems that could maliciously flood us with generated content. The creator of this particular service which is being discussed here and now could also begin taking steps to ensure that his creation does not inadvertently create a problem for some hapless Google user.
Well, no. You have to read further up the thread to see the issue I was referring to.
>I wonder if our current discussion boards on the interwebs can survive the coming influx of content like this and the next generations of it that follow.
Yes the robots.txt is a good and trivial step he could take to ensure well behaved robots do not pick up his content. So your comment suggesting robots.txt is a good comment in its narrow frame, but one that missed the larger picture. That minor problem is solved. The interesting problem is of a different nature.
In a capitalist society, I will see in a negative light any statement or action that negatively impacts my livelihood. I don’t care if the most vocal activists think that it’s “right” in an absolute sense to enact a policy of reverse discrimination. Anything that detracts from my ability to provide for my family is bullshit.
Just to clarify, you're saying that being on a team that isn't diverse and consequently makes provably worse decisions means you're likely to earn less than the amount you'd earn on a diverse team making better decisions, so you're absolutely in favor of maximizing your earnings by enforcing diversity through positive discrimination, right?
The studied that found diverse teams are more effective often some fishy methodology. In particular, one of the more widely circulated studies reaches their conclusion by making diverse and non-diverse teams plan a wedding using dances, rituals, and food from two or more culturs. A lot of these studies start with a conclusion determined a priori and the design an experiment to support it.
Capitalism has nothing to do with it. Whether it's social security recipients or public school teachers, people whose income is determined by the government are as defensive of their livelihoods as people whose pay is set by market forces, perhaps even more so.
Capitalism has everything to do with it: a commercial entity fires people on a whim, whereas public school teachers basically cannot be fired. The NYC public school system is full of underperforming teachers who shouldn't be employed to begin with. Their pay and conditions of employment are determined via collective bargaining, so they're protected from any conceivable equivalent of a PIP or other "adverse action" by the employer.
Likewise, hiring practices in the private sector change like the weather.
Anyone building out a setup based on cgroups and namespaces will eventually arrive at a poorly specified, bug ridden mini Docker. Might as well get with the program early.
Anyone calling bc from bash script will eventually arrive at a poorly specified, bug ridden mini Mathematica?
Wrt "bug ridden"
> if I were having trouble with something Docker-related I would honestly feel like there was a 50/50 chance between it being my fault or a Docker bug/limitation
I don't look inside my personal e-mail inbox unless I'm expecting to receive a message at a particular time: "click on the verification link we sent you" and variations on the theme. If other mail appears on the screen at the same time, I may take a look at it assuming I'm not in a hurry to do something else. Otherwise I never look there. No one e-mails me anyway. Everyone who's anyone has my wife's phone number; that's an exceedingly short list of people.
Slack and GitHub together are adequate for day-to-day work things. Everything else just isn't sufficiently important to justify a channel into my brain.
I also have a burner gmail for account sign ups, but it's not hard to regain control of your inbox and direct people to use a email you regularly check. I bet you have an email listed on your resume, after all. A good rule is to look for "unsubscribe" in the body of the email, and throw those emails into a containment folder. If you ever wanted to scroll through those and unsubscribe one by one, it will be easier to do so, or you can just ignore those emails since they will now be isolated from your inbox.
Plastic is a great material for some uses, but it’s also a very durable material. I’d love to purchase shampoo in the form of a refill of the plastic shampoo bottle I’ve already purchased some months ago. Why buy a new bottle every time? That’s the part which doesn’t make sense.
A large vat at the store, with a spigot to refill the bottle you brought with you. I've seen this for cooking oils and honey, not sure it exists for cosmetic products.
The story of Docker, Inc should be read as a cautionary tale to those who think that every random bit of open source should be “monetized” by seeking rent for its continued use and support.
Exactly, when will Silicon valley investors understand that Open Source:
1. Doesn't grow revenue at the speeds they want returns
2. Isn't "free marketing" (dear God I have seen this one too many times, CTOs even write it out in blogs sometimes)
3. Only really makes sense when you get out more than you put in, aka is community drive . Community driven open source is really the only profitable open source.
I'm not sure, but I don't think iOS lets apps auto-start and run in the background forever. This would be needed for any alternative push notification app, else it would be too easy to miss notifications.
This is definitely a real concern, and we're actually exploring the Chrome permissions to see if it's possible to redirect your traffic, without requiring the "Read all data" permission, because you're right, that shouldn't be the norm.
The permission would need to ask for "your data on go" rather than "your data on golinks.io". I'm not certain that the "your data on golinks.io" would cover it but I think it would.
IMO this permission is something that Chrome should explore, along with other fine-grained permissions. It might be worth making a bug report to Chromium so you can link it when people ask why you ask for such broad permissions. I think the bug report should probably mention that Google uses go links :)
I don't think this is correct. The extension identifies GoLinks embedded in other websites (like internal knowledge bases or emails, I presume) and converts them to a link to the destination.
Ah, so plain text go/test would be linked? That would need full permissions I guess. What wouldn't is for the markdown [jobs](//go/jobs) - that would only need the ability to intercept links on the `go` host - but that wouldn't be nearly as convenient (I didn't realize it would need double slashes before it until now, that makes it a lot less appealing.)
It would still be possible to create a permission that makes it so the code that edits a page can't make any network requests (the output would need to be HTML sanitized, including links), and I'd like to see that, but it would be more difficult to design, implement, and communicate to users.
If it's found to be grabbing more data than it should, people can report them and the extension can be banned from the Chrome Web Store.
It's not ideal but in order to make utilities that work on every page, these permissions are needed.
The code inside the extension bundle (.crx) would need to contain the potential for abuse, and if it gets popular enough, security researchers will look at it. Even if it's not popular, incentives will be at work, because it would be a foolish risk for a company to ship code that could expose a user's entire browser history into the extension, because at any point someone could take a look at the bundle and find the flaw.
It's all about building trust with the company. We don't store or read any information on the sites you visit, we just redirect URLs that contain "go" as the domain, and provide a link for any "go/" links in your browser. We would never risk compromising that trust.
If you take a look at a company like Grammarly, they've built trust with their users, which is why they can have the "Read and modify all data on all sites" and still have 10 million customers. We plan to build the same trust with our customers.
