I think I met him once at one of my first linuxfests.

I have had this problem in several different projects with different teams.

I generally think of it as the "code hostage" or "cherry-picking" problem. You have the work of 15 issues reviewed and merged and loaded up and running on a test environment. For 14 of those issues, a "user" ( or whatever you call the non-developer issue-owner in this case ) checks in and says it is good. Time is passing and the 15th person is a no-show. It's worse than if they said it still wasn't fixed -- then you would immediately go to work reverting that code change and re-testing everything -- but instead everything is held up in limbo.

One way to address the majority of these issues, is to set up a separate testing environment or server per ticket, and put the pull request or branch on it, before it is merged to the main branch. Force users to test BEFORE it gets on the path that will end up in a deployment. This means that slow moving people won't block others.

This might seem expensive, but with APIs to cloud hosting and/or container technology, it can be automated, and is a lot cheaper than it would have been a few years ago.

You can still end up with a problem on the now integrated code, and still have to cherry-pick / revert some commits, and since the result has not yet been tested all together, you still have to re-test. However this happens much less often, because it is only happening in the cases where interaction between different work is causing the problem.

According to a series of tweets from the Surge twitter account, the NRA sent a legal complaint to Cloudflare, which then forwarded it to Digitalocean. Surge responded âoewithin 22 minutes.â Digitalocean asked Surge to provide counterclaim documents. Some minutes later, Digitalocean shut down Surge.sh. According to Surge, 38,000 sites became unavailable.

That at least seems more plausible. I wonder if Surge will spread their services accross several hosting providers after this incident.

Exactly, all politics and humor and whatever aside, how did one notice bring down an entire hosting system ? And if they had 38,000 websites, surely they had received notices before, and why didn't it bring Surge down then ?

It seems there's more to the technical side of this story.

Instead of vinyl tape with silicone adhesive, try this:

http://www.uline.com/BL_6420/G...

It is PET, the same plastic as a 2L soda bottle, and the adhesive is silicone based. I have found it impossible to tear, easy to cut, and it has much better adhesive strength than kapton tape.

If you are interested in the power consumption of the Pi, you should probably check out this: http://www.midwesternmac.com/b...

I did a brief trademark search, and only found this:

http://tmsearch.uspto.gov/bin/...

Which seems to be a coworking space: http://www.themakersspace.com/...

I'd stick to calling it "maker" space, singular, and go for it. Make sure there is no way someone might confuse your efforts with theirs.

"local landfill for recycling"

Recyled as . . . an artifical hill ?

Keep your text config files in git, and use gitlab or something similar to be able to browse and comment on, and link to from wiki documentation, all the changes.

Amazon doesn't normally do that -- they just rent the (virtual) servers, the dashboard and other software including the OS would have been installed by the customer, at most they might reboot or shutdown and restart a machine . . . but they provide a self-serve API to do that, so probably not even that.

Unless the access involved the attackers getting the AWS account credentials, I don't think there's much Amazon could do.

We, the open source and freedom-loving community, may need an organized task force to keep track of these programmers, track their incomes, and store their communications -- just for future reference in case something comes up and a mole is suspected, not an actual search as the Constitution defines it, of course. Similar to the Apache Foundation and other Foundations for Open Source causes, but tasked with keeping our communications secure, and breaking the other side's communications where feasiable. We'll have to keep the existence of the Association secret as much as possible of course, and thus also hide it's budget in small items spread accross the other Foundations. They'll archive all the repos and mailing lists and IRC channels and any other communication medium, but advances in technology make the storage on that scale cheaper. We might have to rent a large building out somewhere that has cheap land and few pesky curious tresspassers, Utah or something. We'll just refer to it as No Such Association for now. A small and expedient measure given the threats of our times.

This is similar to vole:

http://vole.cc/

https://ancillary-proxy.atarimworker.io?url=https%3A%2F%2Fgithub.com%2Fvole%2Fvole

https://ancillary-proxy.atarimworker.io?url=https%3A%2F%2Fwww.writelatex.com%2F and https://ancillary-proxy.atarimworker.io?url=https%3A%2F%2Fwww.sharelatex.com%2F and several desktop latex editors seems to work OK despite your logic.

The main appleal of LaTeX is precisely that you aren't supposed to continuously re-render it, you are supposed to write things. Then you twiddle how it looks a bit at the end.

Optimizing web pages for speed of rendering the output seems reasonable, but I'm not sure that should be a big consideration in a document format.

Or that could be done with a plugin . . . it would also deprive google of the data of what links were clicked in searches.

Will they make it so that if you arrive on a web page via a google search, the operator of that web page cannot see the search terms that lead you there ? I think that would be an improvement.