Repository navigation
Stop spreading misinformation #25283
Description
I have searched the existing issues, both open and closed, to make sure this is not a duplicate report.
- Yes
Misinformation 1: TOTP is hard
The TOTP reference implementation in Java is ~100 lines of code (comments stripped, code formatted). Furthermore, passkeys are also very easy to implement. MDN documentation also available. Relying on other auth providers is just another step into vendor lock-in, which is exactly what immich users want to avoid.
Misinformation 2: lack of folders in S3 is a blocker
Lack of folders by itself is not a blocker. You need to store a virtual filesystem with files mapped to S3 endpoints. This is as easy as storing an object with folder/file names as keys and S3 identifiers as values. As long as you store metadata locally, S3 is cheap.
Misinformation 3: Apple proprietary format makes rotation harder
https://www.iso.org/standard/89035.html
Misinformation 4: race conditions during rotation
Race conditions are not a problem if you're using a nonce.
Misinformation 5: Apple blocks custom chunk uploading
Their guidelines do not require you to use Resumable Uploads HTTP spec draft. Unless you post proof your app was rejected due to not implementing their solution, this is utterly bullshit.
Misinformation 6: chunking means out-of-order
As long as you're not using plain UDP, they come exactly in the same order you send them in. Validation is a separate issue and is not strictly bound to chunking. You don't need validation to implement chunking.
Why come with this?
Top comments blaming Apple for inventing their own image format.
A public apology would be in order.
Don't blame Apple for things they didn't do. You have already shown your incompetence twice: #12702 #12706 and potentially caused hundred-dollar bills.
Activity
alextran1502 commentedon Jan 15, 2026
Appreciate the feedback, please move to GitHub discussion
szmarczak commentedon Jan 15, 2026
alextran1502 commentedon Jan 15, 2026
Hello, I think there might be a misunderstanding between the information discussed and how it is being interpreted.
For example, point 2, in the video, Zack said that "S3 doesn't support moving file" not "lack of folder".
So I won't be spending more time on this, as it has honestly come in with a very hostile position. I'd rather spend time fixing bugs that you refer to in your post
szmarczak commentedon Jan 15, 2026
alextran1502 commentedon Jan 15, 2026
I think it would have turned out better if you had opened a GitHub discussion with
"Hey, I hear you guys saying X in this video. I have experience in this area, such as A/B/C, I think you can do that by reading this article X or document Y to understand better. I wonder what your thoughts are on my position and how it is different from what you are saying."
Then perhaps we can present our viewpoint and experiences based on the work we are doing day to day to reach that conclusion.
But coming in and accusing us of spreading misinformation just leaves a bad taste in everybody's mouth, and automatically makes it harder to have a proper conversation with you.
szmarczak commentedon Jan 15, 2026
bo0tzz commentedon Jan 15, 2026
Negative feedback is very welcome; what's not is the hostile tone you use when delivering it - which you've already been warned about before.
szmarczak commentedon Jan 16, 2026