I've attempted to get researchers to use lossless H.264 to encode CT scans. They typically use directories full of tiffs. Even with intra-slice compression (i.e. tiff compression) they are pretty huge. But H.264 will let you recover the original images to the individual bit, and save a huge amount of space thanks to inter-slice similarities.

They are still using directories of tiff, though.

I’d imagine the main drawback of using H.264 here is that you’d still have to decode to get the frames back. This is similar to how even though many consumer grade cameras will output natively to h.264, if you want to edit the videos from it you’d usually have to convert it to prores or something first (the editor would usually do this automatically behind the scenes)

I’m not sure if lossless h.264 is I only or not, but if it uses inter-frame compression then it’s difficult to randomly access arbitrary frames. For any arbitrary frame you’d have to find the nearest key frame, then interpolate from there based on the inter-frame compression metadata.

It's acceptable to use the nearest key frame when randomly accessing arbitrary frames.

The real problem is that you'd have to rewrite the entire app stack to use H.264 or AV1 for storing the image stack generated by CT.

CT images are 16-bit monochrome, and the pixel values have real physical meaning (Hounsfield Units). So you'd have to prove that your compression tool can reproduce the original images 1:1. The H.264 encoder would also need to be modified to support 16-bit pixels.

And you'd need to modify the post-processing tools to accept your new file format. Otherwise users will still have to convert it back to DICOM or some other commonly accepted format before they can use their post-processing software.

So unless you're a CT vendor, you'll have a hard time pushing this into a hospital.

> The German acronym (DDR) is much better known among Eastern Europeans.

And in the UK. Presumably because it was used in athletic meetings and on cars. Never seen 'GDR', we'd just use 'East Germany'.

I have seen GDR used in the UK. But then again not many people refer to North Korea by its official name here.

The river Taff flows through Cardiff, and 'taffy' was used as a derogatory term for Welsh people from this origin.

I can't pretend I've heard anyone use it since the 80s.

I'm in my late twenties, grew up in the south west. This is my first time hearing about this term

'Anonymisation' schemes are a little like encryption, in that they just get monotonically weaker over time as people work out attacks. But the attacks tend to be much worse. I work in academic open data publishing, and the netflix prize (https://arxiv.org/abs/cs/0610105) hangs over our heads.

But what this illustrates to me is that researchers are just really careless, despite everything we make them agree to in data transfer agreements. It seems absurd to have little cubicles like this https://safepodnetwork.ac.uk/ (think Mission Impossible 1) but I do despair.

--DRESS means your clothes with fall off.

No, troll, it's actually your skin falls off dead and your organs are injured. It's similar to SJS/TEN.

I think this has just been fixed. A bit of dark mode was leaking into light in the css.

I still saw the same bug just now (Firefox on macOS).

It’s still broken for me at this point. White link text on nearly white background. Impossible to read. Safari on my iPad.

Then somebody needs to let the government know, because the relevant 1981 act is "[a]n Act to make fresh provision about citizenship and nationality". In that 'British subjects' are a quite limited subset of citizens. Most British people are citizens, not subjects.

https://www.legislation.gov.uk/ukpga/1981/61/contents

What’s the difference? I’m not knowledgeable enough about English law to parse this

My (really limited) understanding is that 'British subject' was the status of people in the British empire. It's now reduced to just some people born pre-1949 in Ireland and India. They have many of the rights of citizens, and can become citizens via a simpler route than other non-nationals.

No, Braun invented the cathode ray tube.

It's in the article. Not sure it had his name, but certainly his family name since he looked for records concerning his relatives.

The queries appear to have been looking for me specifically, filtering by date of birth. That wouldn't be a good way to find my relatives.

Damn, some other group trying to cause trouble for you?

I doubt it. I think it's just cops doing shitty work under pressure and then trying to cover it up.

Automating the upload of a home folder to the darkweb in the middle of an extortion attempt would be pretty weak for a "legendary" hacker.

whoopsie :D

The big problem with this video is that it's basically entirely based on google translated tabloid articles.

The results are what you might expect if you decided to just use dailymail.co.uk as a source, similar to the creator of malicious trojan virus Python being arrested https://www.dailymail.co.uk/news/article-2124114/Computer-ha...

>Pearson coded trojan viruses, called Zeus, SpyEye and Python, to automatically scour the internet in search of personal details.

It’s really not a good idea to be posting about your case when it hasn’t even been resolved yet.

I do have access to excellent legal advice, strive to live by it.

> I do have access to excellent legal advice, strive to live by it.

Says the guy that went on a news broadcast (unmasked) to brag about hacking Sony.

https://www.youtube.com/watch?v=fPX8yCBdIZ8

I was 17 at the time :) And FWIW, the whole joke there was that neither me nor the other guy being interviewed had anything at all to do with the attacks on PSN and XBL.

Just wanted to say hi, I was pretty young at the time but I remember the whole thing with the PSN shit and the Keemstar interviews :DDdddd

good times man.

But the thing about not having any devices seized, is that real?

Some people I know have had run-ins with the NBI, and the first thing they do is seize your computers for like a year+?

If that's true then that's really weird...

>But the thing about not having any devices seized, is that real?

It's real and just as bizarre as it sounds. You'd think that'd be the #1 thing you'd want in any serious investigation.

Well, judging by this thread, it doesn’t seem like it.

Yes, I'm sure my comments here are just full of terribly damaging stuff.

Not sure what the theory here is. Am I supposed to worry about the judges stalking me online and reading my HN comments professing innocence?

The prosecutors couldn't, and wouldn't even want to use anything I've written here, especially considering the trial is over and they can't just file new evidence.

Not exactly true, but they deprecated absolutely everything that made it a date. It expresses deep regret in the medium of annotations:

https://javaalmanac.io/jdk/1.2/api/java/util/Date.html

(I can't find the 1.1 docs, but they were the same)

It's one of my favourite examples of how languages pretty much always get date and time hopelessly wrong initially. Java now has one of the best temporal APIs.

Yeah, it effectively became a typed wrapper of a long epoch millis value. Generally treated as immutable by convention in my experience, although of course it technically wasn't as the setters were never removed.

It was hopelessly wrong initially, and got even worse when they added the horrible sql Date/Timestamp/etc classes.

With java.time though, it is the gold standard as far as I've seen.

Java's time and duration representations, heavily based on Joda, should be the standard that every language works towards.

It's just about perfect in every way. It makes it easy to do the right thing and it's very pleasant to read.

Curses, I was close. Also: yikes to the design.