Pretty sure that’s what he gave as punishment for eating of the forbidden tree.

That intro and general structure (AI loves bulleted lists but then again so do I) sure sound like a lot of the responses I’ve gotten. As always, it’s hard to say for sure.

Business continuity plan testing day.

I can confirm this is related to the 0.19.4 update. The bug goes away if I downgrade my instance.

That said, it was extra bad with the beta because I think they never got marked read but now that the final release is cut and I’ve upgraded, they’re being marked read on refresh.

I think. It’s possible I just missed that it was working on refresh on beta6 too.

I wish this wasn’t so true.

LMAO we really have Lemmy cliques?

Is there a language that anyone would say really does fare well for continued development or is it just that few people enjoy maintaining code? I’ve maintained some pretty old Go programs I wrote and didn’t mind it at all. I’ve inherited some brand new ones and wanted to rage quit immediately. I’ve also hated my own code too, so it’s not just whether or not I wrote it.

I have found maintainability is vastly more about the abstractions and architecture (modules and cohesive design etc) chosen than it is about the language.

The real primary benefit of storing your relationships in a separate place is that it becomes a point of entry for scans or alterations instead of scanning all entries of one of the larger entity types. For example, “how many users have favorited movie X” is a query on one smaller table (and likely much better optimized on modern processor architectures) vs across all favorites of all users. And “movie x2 is deleted so let’s remove all references to it” is again a single table to alter.

Another benefit regardless of language is normalization. You can keep your entities distinct, and can operate on only one of either. This matters a lot more the more relationships you have between instances of both entities. You could get away with your json array containing IDs of movies rather than storing the joins separately, but that still loses for efficiency when compared to a third relationship table.

The biggest win for design is normalization. Store entities separately and updates or scans will require significantly less rewriting. And there are degrees of it, each with benefits and trade-offs.

The other related advantage is being able to update data about a given B once, instead of everywhere it occurs as a child in A.

How do we know you’re actually here though? 🤔

Yeah, the image (not mine, but the best I found quickly) kinda shows a rebase+merge as the third image. As the other commenter mentioned, the new commit in the second image is the merge commit that would include any conflict resolutions.

Merge takes two commits and smooshes them together at their current state, and may require one commit to reconcile changes. Rebase takes a whole branch and moves it, as if you started working on it from a more recent base commit, and will ask you to reconcile changes as it replays history.

Or homeassistant. Or gitlab/github actions. So much yaml.

I’m currently playing Lego City Undercover on my steam deck, which is only as crashy as the switch version, and it’s great because my 10 year old is also playing it on the switch, as is my 4 year old. Obviously we all play it differently but it’s been a fun couple of weeks all playing the same game.

If you’re up for pgp and git, gnu password store is a killer app. There are a few guis, including Android and iOS, and if you use gopass there’s a nice plugin for browsers as well. And it’s ultimately just two tools that are both solid and generally well known.

My 3090 is a light flickering machine. Kind of annoying tbh.

Having used sync for like 10 years I think that’s been my general experience. It’s always just worked and every once in a while a bucket of new features or a bomb redesign will drop and I’m like “oh hey, I didn’t need that but I like it!”