Quick! Get this person a series A, B and C funding!

Sorry to be a pendantic ass. But. Jellyfin, in and on itself, has absolutely nothing to do with docker.

About the same here, though I have to say… Reading the “3 hours per day” part out loud still seems… Insane somehow.

In a similar vein, I’m currently staying at my mom’s house, and the internet is too shit to use my Jellyfin. As a result, I haven’t been watching any shows, and my day seems to be infinitely longer, like a million more activities fit in the sake 24 hours.

Because a commit should be an “indivisible” unit, in the sense that “should this be a separate commit?” equates to “would I ever want to revert just these changes?”.

IDK about your commit histories, but if I’d leave everything in there, there’d be a ton of fixup commits just fixing spelling, satisfying the linter,…

Also, changes requested by reviewers: those fixups almost always belong to the same commit, it makes no sense for them to be separate.

And finally, I guess you do technically give up some granularity, but you gain an immense amount of readability of your commit history.

Same. And even if you were to fuck up, have people never heard of the reflog…?

Every job I’ve worked at it’s been the expectation to regularly rebase your feature branch on main, to squash your commits (and then force push, obv), and for most projects to do rebase-merges of PRs rather than creating merge commits. Even the, uh, less gifted developers never had an issue with this.

I think people just hear the meme about git being hard somewhere and then use that as an excuse to never learn.

Yes, in supported apps / protocols. Koreader, for example, should have 2-way sync for eBooks, and Mihon has 2-way sync for Manga.

+1 for kavita. It also has a nice webreader ui.

… are entirely possible, even if rarely the right choice.

Or a CLI with clap.

Curious what you are talking about. Multi-threaded sharing of memory for example is also easy with rust, it just doesn’t let you wrote and read at the same time, and so on.

Yeah. Once you get used to the (verbose, but by no means unergonomic!) syntax, you’ll probably never be happy with another language again. Job-wise, I am currently mostly using Go, and while also a nice language, I miss the confidence and security I took for granted with rust.

Not to mention just how goddamn expressive rust can be. Let bindings like if ok/err, else return? Assign from a match on Some(Ok(x))? Filter, map, and friends on any iterator? Oh my GOD the error handling with the question mark iterator? 100% confidence that if it compiles, no error, possible null value, or case is unhandled.

And all this WHILE giving you the amazing security benefits!

Ah, damn, caught me proselytizing again.

• if your skill is so great that you would never cause the kinds of bugs the rust compiler is designed to prevent, then it will never keep you from compiling, and therefore your complaint is unnecessary and you can happily use rust
• if you do encounter these error messages, then you are apparently not skilled enough to not use rust, and should use rust

In summary: use rust.

Nice, that’s great to hear!

Ah, nice. In that case just beware to move /var/lib/private/conduwuit to /var/lib/private/continuwuity, not /var/lib/conduwuit to its counterpart

Ah crap, forgot to ping you! Sorry!!

Yep, easy decision now. Migration went smoothly, just had to move the state dir and chown it to continuwuity:continuwuity. Might be different on docker though, no idea, sorry 😄

Update: seems to me tuwunel is drama waiting to happen. See updated post for details.

Yes, completely agree. It seems that the matrix foundation could easily take a different path to allow the community to flourish and third-party servers to have a much easier time. Since I’m not federated, I wouldn’t even mind if whatever fork I’ll end up on eventually says “fuck this, we’re not following synapse specs any more”.

But yeah, I am sure selling premium accounts on matrix.org is what will save the matrix ecosystem… 🤦🏼‍♀️

Understandable.

Hm, fair enough, I actually have very little experience with XMPP. (Only through prosody, which I personally am on a war footing with.) From a cursory glance, I also couldn’t find an Android lient I’d really want to use, but of course that is subjective.

In any case: I have a matrix server up and running, and it has been a pain to get friends and family on there; I do not want to do all of that again with a new protocol/clients. As long as it’s sustainable, I want to stay with the same server installation, and that means choosing a conduwuit for me.

There’s nothing technically wrong with it, it’s just a glacial development speed. I tried contributing there myself when I wanted a specific feature (which had been requested years prior by someone else and was deemed a good idea), it took months before I even got a single comment back.

In the meantime, I had switched to conduwuit because it was a much, MUCH more active project. However, conduwuit has diverged substantially from conduit, including irreconcilable database changes, so it is not possible to migrate back, that would require starting from a fresh slate and loosing all user data.

Understandable. Funny thing is, I’m not even federated; I think that keeps me away from a lot of drama.

But yeah. The drama sucks, and so does the Matrix Foundation. So many dumb decisions, so many years old issues that could easily boost acceptance and usability, but… Nah. No better alternatives around though if you want to own your data, have proper multi-client support, and at least the option to federate.