Does Podman work well when you have multiple rootless containers that you want to communicate securely in a least-privilege configuration (each container only has access to what it needs)? That is the one thing I couldn’t figure out how to do well with Podman.

deleted by creator

I think what you mean is abandoning self hosting right? Because self hosting Bitwarden would have similar issues if you don’t take the initiative to update.

This also suggests the Electoral College no longer favors Republicans, and is somewhere between neutral and actually favoring Democrats again.

I don’t agree with this. Republican majority States are still over represented. They just happened to also win the popular vote this time. The scenario of Democrats winning popular vote but not electoral is still more likely than it happening to Republicans

Is there a lemmy community similar to this one that allows discussion posts? This community only allows link sharing.

I don’t need the client computers to be alive, only the central server (which could be github.com for example, so not even a server I manage).

That would require my machines to be git servers, right? And hence they should also be on, right? Or am I missing something? Most of the time, my laptop is shut off.

That doesn’t solve the problem of forgetting :(

I could train myself to get in the habit, but maybe auto saving is easier, no?

Sorry, but I’m not really following here. Do you mean like git add remote and have another remote? What would the source be?

Two issues with manual pushing that I have:

• you have to remember to push
• you either get more commits than you need, or you have to do extra work to either clean up or put them in separate branches

When I looked into solutions, I thought of syncthing, but read comments from people saying they had issues with this approach, especially regarding the .git directory

I mean… That’s kinda what git does, in a way… Right?

I have considered this approach, but there are several things I had issues with.

• there is still a degree of latency. It’s not a deal breaker, but it is annoying
• clipboard programs don’t work. They copy to the remote host’s clipboard. I bet there’s a solution to this, but I couldn’t find it from spending a limited time looking into it.
• in the rare case the host is unreachable, I am kinda screwed. Not a deal breaker since its rare, but the host has to be always on, whether the git solution only requires it to be on when it syncs

To address the issues you brought up:

• less commits: this would be resolved by squashing every time I make a commit. The auto save commits will be wiped. If I really hated commits, I could just amend instead of commit, but I rather have the history.
• forgetting to git pull: the hooks I talked about will take care of that. I won’t have to ever worry about forgetting anymore.

Can you please demonstrate how async workflows and monads resolve this issue?

Wouldn’t effect systems still be considered exceptions, but handled differently?

To each their own I guess, databases are ridiculously expensive when managed and I always self host.

A team? For what OP described, all you need is one person

My issue with it arises when data is not interpreted as I expected, like because of weird white space issues for example.

Xmpp definitely wins in privacy. What is there to privacy more than message content and metadata? Matrix definitely fails the second one, and is E2E still an issue for public groups? I don’t remember if they fixed that.

XMPP being a protocol built for extensibility means it will be hard for it not to keep up with times.

On your point of picking one or the other, I’d say pick the one you like and bridges will help you connect to the other. But XMPP came way before matrix, and I believe they fractured the community instead of building it.

There’s a good reason all the big techs built on top of xmpp (meta, Google, etc). It’s a very good protocol and satisfies modern demands very well.

Haha appreciate the honesty :)

It worked more like true messaging app less than messages store ( unlike matrix ).

Can you please elaborate this point? I don’t understand what you mean by “true messaging app” and why that would be a bad thing?

Requirement of permanent tcp ip connection

Are you sure this is the case? Maybe back in the day, but my understanding is this isn’t true anymore

useful feature in xmpp ( like message history ) is optional

Why is user choice a bad thing? There’s a wealth of clients that implement the features you want

If something doesn’t work in xmpp most people would blame xmpp

This may not be an important point, but from my experience, people always blame the client and not the underlying protocol. If I face an issue with my browser, I’d likely blame the browser before I blame http.