Archive for March 21, 2023

Tuesday, March 21, 2023 to Close

Scott Everett (via Hacker News, Reddit):

After nearly 25 years of operation, DPReview will be closing in the near future. This difficult decision is part of the annual operating plan review that our parent company shared earlier this year.


Thank you for your support over the years, and we hope you’ll join us in the coming weeks as we celebrate this journey.


The site will be locked, with no further updates made after April 10th 2023. The site will be available in read-only mode for a limited period afterwards.

This is so sad.


The forums on this site needs to be archived ASAP. Theres so much information living within those forums that it would be a major blow if it all just disappeared, especially as a film photographer, where finding a lot of my niche information pops up on these forums.


Update (2023-03-22): ReclusiveEagle (via Hacker News):

PSA DPReview is being archived by the Archive team. Currently they are working to scrape over 4 million articles and posts within the next 3 weeks. [1] — see April 10 2023

Once archived, the entire site will be made available for anyone to browse on the internet archive. The entire .WARC will also be made available for anyone to download and view locally with a .WARC viewer such as Web Replay — this allows you to download the site and view it locally forever. You will be able to download the .WARC file from here once complete.

Jaron Schneider:

Chris Niccolls and Jordan Drake are joining PetaPixel and will lead its new YouTube Channel. The two have been a mainstay in the photography industry for more than a decade as hosts for first The Camera Store and then DPReview.

See also: Adam Chandler, Rui Carmo, Nick Heer, Om Malik, Jeff Carlson, John Gruber, TidBITS.

Update (2023-03-24): Glenn Fleishman:

Contrast Amazon’s integration of DPReview since 2007 (not at all) with the New York Times’s of Wirecutter—no offense to Wirecutter, but the NYT treats it poorly within the NYT family/framework however good the work is. IMDB is a better example for Amazon: they bought it in 1998 and it remains fairly independent in appearance, yet well integrated with Amazon’s product and video offerings.

See also: Devin Coldewey (via John Gruber) and Arun Venkatesan.

Update (2023-04-03): Kirk McElhearn:

We had an entirely different topic planned for this episode and then learned just before recording that the website DPReview is being shut down after 25 years of covering digital photography and being the best resource for camera reviews.

Update (2023-04-06): Ernie Smith:

In the roughly two weeks since Amazon announced it was shuttering the site, the community of digital photography fans that made up the DPReview website and forums haven’t focused on the what-ifs. Instead, they’ve gotten straight to action. Case in point is the creation of Digicam Finder, an archive of photography information generated by the community. The site first emerged online in a basic form that includes more than 2,500 cameras in a fully searchable database, with specific information on technical features such as weight, sensor size, optical zoom, shutter speed, and USB capabilities.


While representing a new community resource, Digicam Finder is starting with a masterful scrape job of DPReview’s archive, utilizing work conducted by the Archive Team and others to put the website onto the Internet Archive. The site actually links to the Wayback Machine versions of many vintage DPReview articles, particularly reviews of featured cameras, making it possible to access both the open-source camera information and the still-copyrighted source material. But in the long term, Green says that the goal is to take this information and improve both its resourcing and presentation—and the OPD project is already seeing support from hundreds of fans and even outside data-collection efforts.


But even in that context, the DPReview shuttering stands out because of its nature as both a data-rich resource and a publicly facing community of members, and the fact that the closure was seemingly out of left field. And that means there’s a community willing to fight to keep its spirit alive, both in the form of data and successor forums like DPRevived, which has taken in more than 2,000 DPReview forum members since last month’s announcement.

Update (2023-04-22): Scott Everett:

We’ve received a lot of questions about what's next for the site. We hear your concerns about losing the content that has been carefully curated over the years, and want to assure you that the content will remain available as an archive.

We’ve also heard that you need more time to access the site, so we’re going to keep publishing some more stories while we work on archiving.

John Gruber:

I don’t understand either of these paragraphs. I mean, I’m glad they’re still publishing new content, but I don’t understand what publishing new stories has to do with giving readers more time to access the site. And it’s completely unclear what sort of “archive” is going to be available after it closes.


Update (2023-06-23): Scott Everett (via John Gruber):

We’re thrilled to share the news that Gear Patrol has acquired DPReview.


I want to reassure you that we remain firmly committed to what makes DPReview great: the best camera reviews in the business, industry-leading photography news and features, and one of the most active photography communities anywhere on the internet.

The Growth of Mastodon


Looks like users of are starting to register for Mastodon accounts.

Welcome to all new users of Mastodon.

Registered users of Mastodon might reach 10million users tomorrow.

And, indeed, that happened (via Hacker News). Some of the accounts are surely defunct, though that’s also the case with numbers from other social networks.

Mike Masnick:

Anyway, again, no idea how accurate any of these numbers are, but potentially more interesting is’s stats suggesting that the fediverse is closing in rapidly on an average of a billion posts per month!


Recovering Cropped Parts of Google Pixel Screenshots

Simon Aarons (via Hacker News):

Introducing acropalypse: a serious privacy vulnerability in the Google Pixel’s inbuilt screenshot editing tool, Markup, enabling partial recovery of the original, unedited image data of a cropped and/or redacted screenshot.

David Buchanan (via Hacker News):

Google was passing "w" to a call to parseMode(), when they should've been passing "wt" (the t stands for truncation). This is an easy mistake, since similar APIs (like POSIX fopen) will truncate by default when you simply pass "w". Not only that, but previous Android releases had parseMode("w") truncate by default too! This change wasn't even documented until some time after the aforementioned bug report was made.

The end result is that the image file is opened without the O_TRUNC flag, so that when the cropped image is written, the original image is not truncated. If the new image file is smaller, the end of the original is left behind.

This reminds me of the old Microsoft Word issue where if you had it set to “fast save” it would leave deleted text in the file. Sometimes there even seemed to be chunks of unzeroed content from other apps’ deleted files.

I found that the data was indeed compressed using dynamic Huffman coding, but that the Huffman tree was re-specified every ~16KB or so. This was excellent news because it meant I didn’t have to solve the “Huffman coding cryptanalysis” problem, and could instead solve the much simpler-in-practice problem of “find the start of a dynamic-Huffman-coded zlib block”.


Although I’m currently an iPhone user, I used to use a Pixel 3XL. I’m also a heavy Discord user, and in the past I’d shared plenty of cropped screenshots through the Discord app.

I wrote a script to scrape my own message history to look for vulnerable images. There were lots of them, although most didn’t leak any particularly private information.


Very simple script to check which PNG files have trailing data.

I hope that people who host forums, image boards, chat applications, etc., will delete or fix potentially vulnerable images before anyone uses them maliciously.

One way to repair a vulnerable image is to use optipng -fix.


These types of issues are exactly why whenever it’s sensitive, I screenshot, crop/edit, then screenshot the crop’d/edited screenshot. There’s other possible issues than this bug (like iOS’s non-destructive edits by default), so it’s better to be safe than sorry.

Nick Heer:

There are some people in the replies to Aarons’ tweet claiming the same is true for cropped iPhone screenshots. In my testing, that is not exactly right: if you crop an iPhone screenshot and then share it with default sharing options, it does not transmit edit history or removed image data, as best as I can tell. When I AirDropped a cropped screenshot to myself, it sent a re-encoded JPG image instead of the HEIF original. In the iOS Share sheet, there is an “Options” button; if you want, you can toggle the switch to “include all photos data” which includes “edit history and metadata”, including image data removed via cropping. This option is off by default.