AAAAAAAAaaaaaahhhhhh

There’s personal time for sleep in the grave.

That explains it, you can’t code with both your arms broken.

The Shadow

Are the payment processors saying Visa"MC told them to not process payments for this content? Or are they just citing a section of the agreement when being asked why they’re telling retailers to take down this content?

Probably just the timing. Mbin was forked from Kbin after the majority of newcomers from Reddit settled on Lemmy over Kbin. Because Kbin was pretty much the one-man show with an unreliable flagship instance during the initial big wave of users coming over.

If you can read that, see that they’re on major version 1 with a minor version over 100, and you still think they’re using semver, then that’s on you.

I don’t think they’re using semver. That’s literally what I’m complaining about. I genuinely don’t understand why people here are taking it so hard that I wish the Immich devs were using semver.

As this project is clearly not following semver, the semver guidelines aren’t applicable and haven’t been violated.

Wonderful. Good for them. Good for you. Good for everyone who disagrees with me. Just not for me. And that’s just my opinion, man. And that should be ok with you for me to have it.

Aivis. Trai harder.

🍻

You can argue the correctness or not of the guidelines put out at semver.org, but I don’t think there’s any room to argue that announcing a 1.x with a change the developers say is a breaking change, which is what Immich have done, fits within the semver.org guidelines.

But it is a service that clients connect to via an API.

Yes, I understand they have declared that. Their declaration does not, however, negate the common semantic versioning standards, found at semver.org. These common standards are significant for admins running shared systems where they automatic upgrade processes based on common semantic versioning rules. The software will stabilize and they will adopt a more stringent policy. But they should still be releasing 0.x versions since they’ve not yet reached it.

Yes indeed. 🙂

A breaking change should have been 2.0, not a new 1.<minor> release.

It should still be 0.<minor> if they’ve not reached the stability for keeping backwards compatibly in all 1.x releases.

Breaking changes should warrant a 2.0 version, not a 1.minor version.

Edit: I am basing my comments on https://semver.org/ guidelines

I’ve been meaning to give this a try on my Synology.

But breaking changes in a point release? Not cool.

And a lot of professors write their own text book.

Well iPad and iPhone did have the same OS at first, so they knew how to do that. I would have preferred when they forked iPad OS out for them to have converged desktop and iPad instead of making a 3rd distinct OS variant. I can’t reasonably say that a docked iPad is the same as a Mac, as commercial apps I use have different versions, with different capabilities, for iPad and Mac. Things like Adobe Lightroom andIK Multimedia Amplitube. But my Surface Pro has one set of apps whether I’m docked at home, using a clamshell keyboard case, or as a tablet and pen. That’s more useful to me than having a really well polished and dedicated tablet OS.

I’m thinking this is the opposite direction, with the enhanced desktop mode in Android 16. You hook your phone up to a KVM and get Chrome desktop, complete with containerized Linux apps and your mobile apps staying on your mobile device.

Apple doesn’t exactly try to converge OS platform, even forking off iPad OS from iOS.

Microsoft’s converged desktop and tablet OS hasn’t been well regarded.

Google’s efforts to make Android well suited on tablets has been poorly maintained.

I did find ChromeOS Flex on an old Surface Pro 3 to be a pretty good tablet experience. I’m cautiously optimistic about this, though I haven’t tried the desktop mode on my Pixel 7.