Nick Krabbenhoeft 🆗 @[email protected] 🆒

Does Apple roll the DCF folder numbering from one iPhone to another? If you've taken 90,000 images on a phone (189APPLE), and then migrate to a new phone, will it start with 190APPLE?

DCF is one of those standards that you don't realize is still widely followed, pretty good, very difficult to replace, and keeping the 8.3 filename spec alive. To this day, Apple still maintains DCF folders (100APPLE) and almost DCF filename (IMG_0001.HEIF, shame on that F.)

Can't believe the inventor of the thing that gave us RIFF is getting bought for $50+ billion

@EmptyBowlShow nothing beats putting your spoon into a bowl of tortilla chips crumbles swimming in salsa.

@beet_keeper Gonna try this

@NKrabben Is it a correct read from this image that there are a couple of hundred (or thousand?) null bytes in the header? If you strip those to the first chunk of non-null bytes, you might get some other rersults.

I have what I think are audio files from a CD, but they don't have extensions, aren't identified by mediainfo, pronom, file, etc, won't open in VLC. But there is a txt file that looks table of CUE file info. Any ideas of what else I can throw at these files?

@angealbertini Here's one snapshot from binvis.io. Each byte binned into a 5 partition black to blue gradient from 00 to FF

@angealbertini Just online TrID. The primary results are typically very generic, TXT, Null file, etc. Often MP3 makes an appearance, which, isn't correct, but there is some regularity to the data, based on visualizations of the hex

@CHLThor Depending on the file, sometimes FFs, sometimes 00s

@NKrabben What are the first few bytes?

A passkey is exactly like a key in that I have no idea where it is.

@beet_keeper Oh, it's because \x## isn't a byte, but a representation of a unicode character. So \xEF == \u00EF == \U000000EF == ï This doesn't quite square for me though, because when Python is reading a byte sequence it sees C3AF -> ï but also EF -> \xEF -> ï?

@beet_keeper Or some kind of error, like UnicodeEncodeError: 'utf-8' codec can't encode byte 0xef in position 0

Why does Python render a UTF8 BOM as `` ? The BOM is \xEF\xBB\xBF aka U+FEFF aka ZERO WIDTH NO-BREAK SPACE. So why isn't that byte sequence rendered as a zero width no break space? \xEF isn't a valid UTF8 byte. Why does Python render it as U+00EF aka \xC3\xAF aka ï?

@historivist @CHLThor I'm still looking for a good short explainer, but I like the analogy at the end of this blog post DPI is like "8 glasses of water a day." We hear it's important because the people saying it's important heard other people say it's important. jimhphoto.com/index.php/2020…

I'm realizing that image generators are the clip-art libraries of the future. Please prepare yourselves for my upcoming slide presentations on digital preservation starring Archie the Cockroach

I love Lieferketten.

Installing a PCI SCSI card

In observance of @UNESCO World Day for Audiovisual Heritage, I recommend seeking out sources for digitized footage of the 1948 Nakba and reflect on how little has been done to prevent continued bloodshed. youtube.com/watch?v=d3v6VH… #WDAVH