jhealy

This is neat.

I'd love an NTP sync'd wall clock but my time for hardware hacking is pretty limited. Are there any off the shelf wall clocks that do NTP? Bonus points for POE and no WiFi.

A similar anecdote from my family.

My uncle (a sheep farmer) and I discovered that:

1. I was afraid to touch anything in a car engine, but happy to muddle through unfamiliar computer issues

2. He was afraid to click unknown buttons on a computer screen, but comfortable pulling apart and rebuilding an unfamiliar car engine.

In both cases, we were confident because we knew whatever mistake we made we'd be able to reverse it. And in both cases, we were afraid of making a mistake that we couldn't reverse.

It connects to your computer via USB 3.1 and a USB type-a port. Unfortunately type-a can't power the computer and can't carry video signals.

> Just adding a banner to docs pages is plain lazy and is not customer friendly

We will be affected by the change (our prices will drop) and we received a proactive email about them this morning.

Sounds like it might've been this article?

https://jpetazzo.github.io/2017/02/24/from-dotcloud-to-docke...?

I'm interested in why COS is unaffected - is it due to the read-only root filesystem?

This is only the tip of the iceberg, but I found this introduction to naive bayes classification assumed little prior knowledge and successfully helped me build a basic classifier: https://monkeylearn.com/blog/practical-explanation-naive-bay...

The delegates.xml file looks interesting, and `convert -list delegate` lists a large number of formats that we don't need to support.

I'm not clear on the difference between a "coder" and a "delegate". Do I need to add a policy.xml entry to for each delegate?

For our use case, the only input formats we need to support are GIF, JPG and PNG.

Using policy.xml to disable EPHEMERAL, URL, HTTPS, MVG and MSL is a nice start, but is it also possible to disable PDF, open office, FTP and others? Where would I find a list of all the supported coders?

pglogical (http://2ndquadrant.com/en-us/resources/pglogical/) claims to allow cross version upgrades from 9.4 to 9.5 with minimal downtime, but the documentation seems fairly light-on.

Has anyone come across a guide to using it for upgrades?

Here's a discussion of these results by an Australian lecturer in Pharmacology: https://theconversation.com/a-fishy-story-zebra-fish-bisphen...

He covers a few points, but here's a key one:

> The concentrations of BPA in this study, while low, are still much higher than humans would be exposed to. It is a bit difficult to relate the exposures of the fish to those of humans, as humans typically do not swim immersed in solutions of BPA day in and day out, but let us look at it from a variety of perspectives.

It seems like inbound and outbound zone transfers aren't offered by a number of providers (like AWS). Do you know of a list of DNS providers that support either option?

Yup, in Ubuntu 12.04 LTS version 1.0.1-4ubuntu5.12 is what you need.

Here's the changelog: http://changelogs.ubuntu.com/changelogs/pool/main/o/openssl/...

Interesting question.

I'm a developer for the linked site - if you're interested in posting the question in the comments I'll ping the author to see if he can answer.

I'm not much of a gamer, but I thought I'd give this a go on my Debian amd64 system. However the package is i386 only, so it won't install.

Are they planning to support amd64 too?

That's a shame. I was opting to use fallback mode so I could continue using gnome without gnome-shell.

When 3.8 hits debian unstable I guess I'll move to a different window manager.

You've just described KDE, Gnome and a suite of other graphics toolkits. Do we really need another one in the mix?

The cached page contains content suitable for everyone, so it looks the the user is logged out.

An extra AJAX request grabs the users logged in status, CSRF token and similar data as JSON and then modifies the page so the user sees what they expect (a logout button, a comment form, etc).

We're using ShareJS in production for the authoring side of http://theconversation.edu.au - it's brilliant and solved most of our collaborative editing pain.

If only it wasn't written in node....

Sure, but it's better than the 15 seconds on ruby 1.9.2 and rails 3. Things are getting better!

We see ~20% improvement with the same upgrade (on 1.9.3p0).

8.5s to 6.6s on my laptop (with SSD). Nice!

As an Australian sitting 210ms+ from most web servers I use regularly, this is great news. Muxing all assets for a each page load into a single TCP stream will make page loads oodles faster.

As others have said, this won't help much until common servers (nginx, varnish, etc) also support SPDY, but it's a move in the right direction.

This perfect circle gig is a good sample:

http://switchcam.com/event/a-perfect-circle-lollapalooza-201...

Some of these concerts may have bootleg audio available, often recorded by audiophiles with decent equipment. It'd be amazing if supported syncing that up so you'd get great audio with multi-camera video

absolutely agree. It's incredibly disingenuous of the author to lay all the blame at the feet of his female job applicants.

The problem is his companies aggressive hiring practices and his willingness to follow them, not his applicants.

The prices seem a bargain to me.

I'm not a reader of Linux Journal, but $2.45 an issue is absolute peanuts. Hell, I'm considering buying the next few editions on the off chance the content is interesting.

Creating quality content creation still takes money, even if the print and distribution costs are minimised via digital distribution.

I understand Lucas' decision, however it leaves some worrying questions about the state of ruby on Debian systems.

Despite the rumours, the ruby1.8, ruby1.9 and rubygems packages are are excellent shape thanks to the hard work by Lucas, Diago and Akira.

There were consistent fundamental workflow clashes between upstream and the Debian packagers that have made their job exceedingly difficult. These clashes aren't malicious or antagonistic, they're just the meeting of two very different communities with very different priorities.

To name a few of the clashes: API changes in minor releases, effective forking of rubygems by copying it into the 1.9 tree, opaque decision making (mostly due to the language barrier), allowing installed programs (ie rubygems) to update themselves and expectations on what is allowed in /usr/bin.

I'm not saying either community is necessarily correct on these issues, just that they add up to some pretty big differences for debian-ruby to navigate.

I use the Debian packages for ruby1.8, 1.9.2, jruby and rubygems in both my development and production environments. I've found them stable, rapidly updated in response to security issues and predictable. Lucas - thanks for your efforts, they will be missed.