Slashdot videos: Now with more Slashdot!

The typical compromise (see what I did there?) when a customer or Federal Government auditor wants to run scans of any sort on your private network is to agree on tools (to be provided by the auditing group if you don't already have them) running an agreed configuration/profile/whatever against an agreed limited scope target list (typically a VLAN or set of VLANs unless that entire network is devoted to just that one customer, which is sometimes the case, though less so these days with public/private/hybrid clouds being all the rage). When it comes to web application and database testing, you'll typically agree on a non-production target list that's a mirror of the production system (with appropriate verification of the two being a mirror outside the automated testing) so as to avoid impacting the production systems. When it comes time to run the tests, over-the-admins'-shoulder monitoring ensures the proper tools with the proper configurations hitting the proper targets is being done and that the output is being handed over unaltered.

Seen this done in plenty of places and 99% of the time, the auditing group is fine with it because at the end of the day, it's getting them exactly what they want; just in a slightly more red-tape riddled way. Meanwhile, the group being audited has the assurance that nothing is running wild all over their network unsupervised. If you don't have anything to hide, you're typically fine with this approach. If you aren't fine with this approach, something else is going on behind the scenes and most of the time that'll be something you're trying to hide.

Two hours for a one-way commute? That doesn't sound like a very good life balance. I think if that was our teams that we'd end up doing a mixed online/f2f meeting as if some of the team were remote.

Yep, you can improve acoustics a little with soft furnishings and plants for instance. Bonus is a better environment.

Polycom isn't necessary. I work with two remote scrum teams who both try standing around a shared desktop in their rooms for their stand-ups via Lync. One of them has great audio, the other doesn't. Both are in large echoey rooms. The only difference in systems is their mic and room decoration.

The team in the room we can't hear clearly have resolved the issue by doing all meetings from their desks using headsets. They also now have long drawn out stand-ups. Hmmm, proves the point about standing up.

Never tried SmallTalk?

Most BD players do have storage. BD-Live depends upon it for instance.

Any BD-J apps will need to be signed with a private key that matches the public key in the cert pressed to the disc, won't they?

This is neurotic navel gazing. Take responsibility for your own actions, which includes getting drunk in the first place because you know before the first drink that this will lead to suspension of judgement. If you choose to use a tool like a robot to get you a drink, that's your decision, even if it kills you. What next - a controlling nanny state that raises the drinking age to 21 or it makes it illegal to jaywalk?

I switched to Chrome a few years ago because I was fed-up with Firefox's monolithic single process architecture. With a single process I have no way to tell which tab is draining my battery, which is a bigger issue than the constant memory leaking. The devs at Mozilla and Netscape before it have never really understood the benefits of multi-processing.

My laptop failed a few days ago so I'm on an old machine I haven't used for three years, but seeing as Firefox is the default I thought I'd update it and give it a shot. Mistake. One tab having trouble loading a web page blocks the whole UI leaving me wondering whether the app has hung up and needs to be killed via Task Manager. What a load of utter shit. Internet Explorer is better these days.

When did they promise that Electrolysis would be done this Feb? How many years have they been promising it full-stop? Now it seems it'll be later this year. No commitment, and apparently incapable of either running a decent engineering operation that can deliver anything sensible in a predictable and reasonable time frame.

Back to Chrome.

Actually rapid charge isn't that bad; you normally only rapid charge to 80%. It's rapid charging to 100% that's the most problematic.

Not only cost though.

People just like having great cars. Electric cars are quiet, zippy, reliable and easy to use. When you go back to a fossil fuel car afterwards, it's like going back in time.

> So electric cars have electric heaters; I had not thought about that aspect before. That would be a considerable inefficiency;

To some extent. The main problem is that it flattens the battery more quickly and impacts range in winter time, the actual cost of the heater for an hour or two is generally relatively trivial compared to the other costs of running the car.

The newer electric cars have much less of an issue though. Instead of using electric heaters they run the air conditioner in reverse (it's an 'air source heat pump' in fact) and most of the heat energy then comes from the external environment rather than resistive heating. The heat pump uses about 1/3 of the power.

Nope, even the worst case is not a deal breaker for most people.

The thing is, most people don't empty the battery most days. A lot of people do like 20 miles a day, so in practice, even with a conventional socket, the car is full again each morning; even on 110 volts.

If you have a 240 volt socket, which are very, very widely available, it's even less of an issue.

And the extra cost to install a higher current charging point is very low. Where I live most premises have a 30 amp, 240 volt circuit already for their electric cookers. That's about 6kW, and the Nissan Leaf has a 24kWh battery; it can do an 80% charge in about 4 hours.

I'm surprised you expect to hear about it here. Most people here seem to care about the codecs and whether they're free. DASH doesn't really care about codecs and really just defines how you create and use adaptive streams and is based on existing codecs/formats. It only standardised relatively recently and it's going to be big (but hopefully transparent), for example: http://www.dash-player.com/blo.... Expect to see it as a vendor neutral alternative to things like MS SmoothStreaming and even Apple's HLS, although the later requires you to have a player with your own decoders if you're sending more than a certain size to iOS devices.

That said, most implementors are doing AVC or HEVC with AAC in a fragmented MP4 container. VOD content is probably one file per stream and live is multiple files fragments) per stream.

In most cases crypto is like having the worlds best lock on your door; the people that want to get in just jimmy the window instead.

The phone thing could certainly happen in theory, but in practice the NSA may have already installed a backdoor or found an accidental backdoor that was due to a bug. And they would probably copy the flashdrive in the phone and analyse it later, possibly on a supercomputer if they're really keen; a lot of commercial crypto is deliberately weak so they can crack it that way if they really have to.

How well does that work on OS X? Oh, no TortoiseSVN?!

Seriously, only a programmer could possibly think SVN is the the right tool in a general office environment.