They constantly ask for an example project, even if it's something that is easily demonstrated, simply by running existing Apple software, and creating a project, would be a huge pain.

They also ignore reports. Very rarely, I may get a ping on one of my reports, asking me to verify that it was fixed in some release. Otherwise, there's no sign that they ever even read it.

I usually end up closing my bug reports and feature requests, after a few months, because I'm tired of looking at them.

It's clear that they consider every bug report to be a burden. That's a very strange stance, but then, they are not a typical company.

I guess you can't argue with the results, as they have a market value North of 3 trillion dollars, but that does not make it any less annoying.

Which means that if that bug has been present since the (now unsupported) Mavericks, tough luck!

I would think the diffs would be telling to the right people.

It's on the front page of HN, so that's a good start!

What's the point of it? It is well known in the industry they ignore bugreports.

Also, this bug doesn't affect the majority of users, so it won't ever be fixed.

> I stopped checking the “delete after import” button

”Glad” to see it was an actual bug.

It’s more likely that things will be reversed: the old, battle-tested framework may have bugs, but it’s is less likely to have serious ones.

They should try to hunt down bugs in the existing code. A partial rewrite of parts that historically have many bugs may be in order, but a complete replacement? Unlikely to be an improvement.

Never use the camera over USB, the experience is terrible on everything from Canon to Sony to Panasonic to Fuji.

Don't fight it, just buy that $30 USB hub and get on with your day.

For the future, Graphene OS devs have stated publicly that they're working with an unnamed hardware vendor to develop a phone that will meet their list of hardware requirements. Currently only the Pixel line does. From what I understand, a few Samsung phones come close, but don't support bootloader re-locking... When you unlock Samsung bootloaders it burns out a fuse on the board which in turn completely disables Knox, their architecture for a trusted execution environment.

I suspect banks won't ever be able to take their web portals down and go app-only, though Google is now trying to ram through technologies in the Chrome browser to "verify the computing platform" that will have a similar effect to the Google Play "integrity" checks for apps.

Enduring solutions to these vendor lock-in efforts must ultimately be legislative.

That being said, I mostly receive email, and the privacy benefits of running my own server would still be significant even without the ability to send email at all.

I had one case where I screwed up a shoot and thought file corruption might have been involved (it wasn't) Even though I had formatted the card with the camera and shot maybe 5 test shots I was able to recover most of the images with Disk Drill

https://www.cleverfiles.com/data-recovery-software.html

which has both Windows and Mac versions and looking at a sample of them confirmed it wasn't corruption, it was user error.

It doesn't strike me as different from "porn" i.e. "unix porn" "food porn" etc, which are at least somewhat widely accepted. I assumed it was self-aware/deprecating humor, as in the people there recognized they were frequently replacing which gear they used beyond what might be strictly necessary.

It was colorful, in the way a lot of music and art is colorful. It's not like it's a sysadmin forum...

It's like, we collectively prioritize efficiency over fun and then we wonder why life is not fun even though it is efficient.

C++ reference is one of these.

Ruby's community has been all sorts of whimsy and quirky over the years.

I very much enjoy Tenderlove being the community figurehead he is as is: kind, empathetic, genuine, open-minded, and generally wholesome.

> it's just awkward with interns to explain.

I've never had any trouble talking about Aaron Patterson a.k.a Tenderlove to coworkers, interns or otherwise.

I don’t even want to know what ZScaler thinks of “tender love making”.

I still use Macs because data on a physical disk seems perfectly reliable, but I've been bitten by so many of these bugs in their apps. iCloud files completely disappear, then reappear a day later. Highlight a couple chapters of a PDF in Preview, then reopen the file and they're gone because iCloud thinks the older unhighlighted version is newer or something. Madness. I don't touch any of these Apple services/apps anymore.

There's very clearly a fundamental bug in whatever sync framework they seem to share across everything. It's bad enough to have data disappear entirely or deleted data reappear, but then when data shows up in the completely wrong place, and this has been happening for years and years and still isn't fixed... I don't know what to think.

You're right. There's no other word for it but "insane". They can engineer their A-series and M-series microchips, but it's been over a decade now and their sync is still fundamentally broken.

* prompts in settings for adding an account recovery contact that never go away, even after months and months of successfully setting it up multiple times.

* OS account profile picture can barely stay associated with the most recently picked option. Happens for non-iCloud local accounts on Mac, happens when I change profile pictures on iOS for iCloud… weird.

* OS account update screens on iPad, iOS, and watchOS will forget that they are in the middle of updating if you navigate away from the settings screen. Thankfully, today they at least recover from it (it’s probably still happening in the background), but it takes several long seconds of spinning for the settings page to remember that it was doing an update two seconds ago before I navigated away from it.

* similar to your ghost pictures bug, deleting a large media file from a media player app moves it to recently deleted, but you can sometimes end up in situations where you can’t permanently delete the file, or it doesn’t show up anywhere but still takes up space. (Talking about 20GB-80GB file sizes where it makes a big difference on OS storage space)

Some of these bugs have been around for a VERY long time.

But the weird thing is I don’t see them in 3rd party apps.

Not sure when exactly that changed, but it was probably a few OS releases ago?

I then subscribed to Apple Music and relied on its matching function. After switching from an Intel Mac to an M2 and redownloading my library from remote, it now believes that each and every song in my library are rented Apple Music copies. Even those it shows as having been added in 2003.

Some songs are missing; some go missing, then inexplicably come back months later. Worse: so far I have found around a dozen which have been replaced by different versions.

It's a real mess.

The Safari reading list can't even sync properly between devices for me. Image Capture ("Keep Originals"??) or AirDrop is a little minimal for such a keystone part of the phone -> computer if you don't want to use Apple ecosystem after.. Let alone the other more complicated issues.

Used to be, these were full software engineers embedded with dev teams, with a mission to destroy, document, and harden the apps and frameworks.

During the 2010s in all the FAANG that I’m aware of (have worked at 3), QA as a high paid American profession was completely offshored to India and responsibility for quality removed from developers concern. It’s a blocking item on the Launch Checklist. Automated testing was expected to fill the gap but has mostly been ignored.

Dropbox doesn't seem to keep timestamps properly either.

I like using filesystem timestamps to sort through things in Finder, and thankfully I like A Better Finder Attributes for being able to batch copy EXIF data into timestamps.

[1] https://www.publicspace.net/ABetterFinderAttributes/index.ht...

Ensuring ZFS has at least 2 copies on physically separate disks and using scrub frequently is the way, right?

Please correct me if I am wrong HN!

https://github.com/RhetTbull/osxphotos

Also a good idea to copy to multiple locations when importing. When I do professional work and import into Lightroom from SD card I have it set to create two copies - import to my external SSD (the "working" copy) and also copies the files to my NAS (which is then backed up to the cloud).

Nowhere in that process do I ever delete anything.

Every professional/paid client I shoot for, I do on new SD cards. I have dual slot cameras, so one card just permanently lives in my camera and gets formatted between shoots, the other I treat as a one-time use card.

Doesn't eat into my margin too much, and I appreciate the extra redundancy when dealing with someone else's wedding photos, so that if somehow something went catastrophically wrong with the rest of my back up process and off sites, at the very least I still have the SD card with the RAWs on it.

https://github.com/LANDrop/LANDrop

I used it along with another called Localsend, but the later one gave me a bit of headache and crashed while transferring some large files last time I used it, but still great as an alternative too, and it’s open source as well.

Edit: Actually, you are correct, it seems they did close it! Try localsend instead.

As far as I can tell:

- 0x7800 bytes were replaced at file offset 0x00aa0000

- 0x2200 bytes were replaced at file offset 0x00aa8000

I can't tell if the replacement data came from a different part of the file, or somewhere totally different. Race condition somewhere sounds plausible.

The visible effect shown could be due to a change as small as a single bit flip. It also could be that large parts of the file got overwritten, or that it partially got zeroed. The exact kind of damage can help pinpoint the cause of the problem.

It sounds like Photos App can have issues trying to import both at the same time?

GP isn't wrong though. Most cameras embed a medium quality full-resolution JPEG along a couple different thumbnails in raw files, so saving raw+normal JPG is kinda pointless, because the raw already contains that jpeg. Raw+jpg is only easier in the sense that many/most non-vendor tools - even viewers - can't properly handle the embedded jpg so it's easier to just duplicate the storage (e.g. 50 MB for the raw + 10-20 MB for the JPG) and take the hit on storage consumption/transfer time.