• 6 Posts
  • 494 Comments
Joined 2 years ago
cake
Cake day: July 1st, 2023

help-circle






  • Development time and user support?

    These are two pretty obvious reasons. It takes time and time is a limited resource. Therefore, time should be spent on solving impactful problems. Lemmy account login is extremely low impact, it’s not a bad thing, it’s just not something that improves immich for a large portion of its user base.

    Another thing is user support. Since the many instances are self-hosted for the most part, and they will go offline, and they will go away forever in some instances. Users asking for support for this login type and asking for additional features to make up for this baked in instability.

    Essentially. Low impact work that may drive a higher volume of support efforts.

    It’s the same reason some niche projects stop supporting Linux. Low user volume and disproportionately high “neediness” of those users.













  • This is a good reason to start investing in multi region architecture at some point.

    Not trying to be smug here or anything, but we updated a single config value, made a PR, and committed the change and we were switched over to a different region in a few minutes. Smooth sailing after that.

    (This is still dependent to some degree on AWS in order to actually execute the failover, something we’re mulling over how to solve)

    Now, our work demands we invest in such things, we’re even investing in multi-cloud (an actual nightmare). Not everyone can do this, and some systems are just not built to be able to, but if it’s within reach it’s probably worth it.