←back to thread

669 points danso | 3 comments | | HN request time: 0.588s | source
Show context
coffeefirst ◴[] No.23261776[source]
"Our system broke, you're screwed now, sorry" is never an acceptable answer. Do they really not have anyone who knows how to get stuff done?

1. Take the files and figure out what to do with them so they can be read. This isn't a hard problem.

2. Ask everyone affected to email you the photo or a new photo of the documents. We'll just take it on trust that you do so honestly because there's no way you would've seen this coming.

replies(9): >>23262323 #>>23262343 #>>23262428 #>>23262479 #>>23262627 #>>23262802 #>>23263229 #>>23263339 #>>23263882 #
xienyc ◴[] No.23262428[source]
>"Our system broke, you're screwed now, sorry" is never an acceptable answer.

That's not what happened at all. The college board admitted their fault and are letting students take the test again. Even without that, they mentioned in their FAQ that JPEGs and PNGs are the only file types acceptable and even sent out a tweet (which should have been an email) a week before especially for iPhone users to let them know how to take pictures as JPEGs.

I agree with the people blaming the board for not having a standard image input field that lets the OS know when to convert images to JPEG but that is their only fault and I wouldn't have thought of that as a bug deal if not for this issue. While I'm all for open source media formats replacing what we have, HEIC certainly isn't big enough to be considered as among standard input options. Also, isn't Apple themselves infamous for not supporting certain formats throughout their devices?

replies(13): >>23262512 #>>23262557 #>>23262647 #>>23262683 #>>23262686 #>>23262913 #>>23263022 #>>23263295 #>>23264032 #>>23267061 #>>23267152 #>>23267311 #>>23268141 #
pwthornton ◴[] No.23262512[source]
If they had enough time to warn people ahead of time, they had plenty of time to push a fix to their system for this. We are literally talking about adding support for one more image format.

Emails, tweets, texts are no excuse for broken products. The iPhone is the best selling model in the United States. It is on College Board to support its default image format.

Good product design is owning your users' success. It is not sending people workaround emails.

The bare minimum would have to be to do a warning before every single AP test about this and giving students a few minutes to change their default image format. Sending a tweet (!!!) out does not count as doing any work.

This is a failure. An abysmal failure.

replies(14): >>23262634 #>>23262713 #>>23262885 #>>23262935 #>>23263736 #>>23263796 #>>23263816 #>>23263831 #>>23263848 #>>23263933 #>>23264038 #>>23264438 #>>23265745 #>>23265965 #
Alupis ◴[] No.23262885[source]
HEIC isn't supported in a lot of places. It's mainly (only?) Apple that uses it with iOS devices.

Perhaps Apple should make it easier or automatic to convert into a format that's universally usable.

Bet the same thing would have happened with webp images too.

JPG and PNG are like the FAT32 format of images. Always accepted, everywhere.

replies(2): >>23263019 #>>23263720 #
1. cozzyd ◴[] No.23263720[source]
You know, I thought that about FAT32. But apparently neither Windows nor Mac OS X can see a FAT32 partition on an SD card if it's not the primary partition (at, least, not in an obvious way).
replies(2): >>23264040 #>>23264121 #
2. nucleardog ◴[] No.23264040[source]
Don't think that's exclusive to FAT32. For quite a while Windows just straight up ignored anything but the first partition on removeable media.
3. derefr ◴[] No.23264121[source]
Windows and macOS do that in order to hide EFI system partitions, I believe. (Not that they should have to; MBR and GPT both define a specific tag to mark a partition as being an EFI partition. But so many partitioning tools don't bother to use that tag—or to adhere to any other standard that could be used to identify an EFI partition—that OSes are stuck with a very bad/loose heuristic.)

They may also get some other benefits from this bad/loose heuristic, e.g. hiding Linux's common FAT32 /boot partition; OEMs' "backup" and "BIOS update" partitions; OS Recovery partitions from unknown (and therefore unpredictable-in-approach) OSes; etc.

What the consumer OSes really need is a bit in each MBR/GPT partition's bitflags, that has a meaning equivalent to one of those "no user-serviceable parts inside" stickers. I think it's too late to fit that bit into either standard, sadly.