• 19 Posts
  • 158 Comments
Joined 1 year ago
cake
Cake day: July 9th, 2023

help-circle







  • 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.













  • 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.