Res Publica Non Dominatur!

I’m just this guy, y’know?

In your interwebs, janitorializing things up and keeping the porns online.

  • 1 Post
  • 11 Comments
Joined 3 months ago
cake
Cake day: August 18th, 2025

help-circle
  • Seeing most of the negative comments here noting bare metal etc.

    Moving to the AIO build solved literally every issue I had with the single exception being the colabora office stuff.

    For the image stuff, basic file, download etc… been great.

    The Android app gives me grief, but I suspect that’s my janky Samsung phone killing it’s permissions.

    Considering they only officially support the AIO, it’s worth trying that out before passing full judgement. It has flaws, for sure, but it’s immensely complex and the AIO nullifies many of the variables that they can’t otherwise account for easily.



  • I would suggest instead looking into the deployment via the very thorough system here:

    https://github.com/spantaleev/matrix-docker-ansible-deploy

    It may seem a little overwhelming at first due to the large list of options, but underneath it boils down to some simple variables in a file. Once complete, you can then add/remove components merely with a small edit and redeploy.

    I’ve been using this for about a year, after manually doing the systems for Element and Synapse for a few years before that and HATING how kludgy things seemed.

    Once on the Ansible deploy from above, features just work. It’s been a night vs day difference without trying to convince you to pay money any time you go into an interface.

    My few users (about 2 dozen) regularly do group calls via the newer Element Call stuff (RTC) and even with a high-latency connection from one of the users using satellite internet, things work smoothly.

    XMPP / Snikket might be a better fit for your needs, but I wanted to make sure you had a chance to try out the better solution for implementing Synapse (or other Matrix servers!) before just judging by the problematic corporate deployment.


  • Nice!

    Watch out for CPU and RAM gobbling… Jitsi’s GC process can make your video streams go sideways fast if you bottleneck it too much.

    And even if things seem smooth, make sure you have SWAP space enabled somewhere! the JVM will murder your system before you know anything is wrong, and SWAP allows the kernel to compensate long enough to at least cry for help.










  • Fun fact! The Laser in the burner didn’t actually burn from thermal effects, and instead caused a chemical reaction using specific wavelengths of light to activate a substrate called pthalocyanine.

    This is part of why you could burn “faster”, although typically you had a higher quality burn at slower speeds as the change from one color to another via the chemical effects was more complete. This allowed weaker reading lenses to better perceive the new colors easier, and greatly increased compatibility.

    I am very, very old.