Admin: lemux

Issues and Updates: !server_news

Find me:

mastodon: @minnix@upallnight.minnix.dev

matrix: @minnix:minnix.dev

peertube: @minnix@nightshift.minnix.dev

funkwhale: @minnix@allnightlong.minnix.dev

writefreely: @minnix@tech.minnix.dev

  • 3 Posts
  • 30 Comments
Joined 1 year ago
cake
Cake day: June 22nd, 2023

help-circle








  • minnix@lemux.minnix.devtoLinux@lemmy.mlSilverblue vs uBlue
    link
    fedilink
    English
    arrow-up
    3
    arrow-down
    5
    ·
    3 months ago

    So, the points in favor of Kinoite is sticking closer to upstream, however it seems like I would need to layer quite a few packages. My understanding is that this is discouraged in an rpm-ostree setup, particularly due to update time and possible mismatches with RPMFusion

    It’s not only discouraged but often times it’s system breaking. I used Kinoite for a year before I just became too frustrated and gave up. The first thing I learned though was to stay away from package layering because it tended to break things more often than not. Basically if you can’t find or build a flatpak and you don’t want to use toolbox all the time, just stick with workstation. Immutable is great when deploying to multiple servers or locked-down corporate workstations, but it makes no sense for your personal setup especially if you’re already familiar with Linux.


  • Not every room or space will be hosted by someone self-hosting their server. I find it kind of appalling that this would be the solution. It’s certainly not what I’ve heard from people working on projects around moderation.

    This is somewhat the goal, but without the hyperbole. Homeservers will be hosted by individuals or orgs, but will contain many rooms and spaces each. In 2020 there were over 20,000 homeservers. That number has without a doubt grown exponentially. The concept is the same with Mastodon. If you are worried about moderation on the matrix.org homeserver there are many lists of public homeservers across the web. Many people research homeservers to see if they are a good fit for them just as they do Mastodon instances.

    This blog post gives a good idea of where matrix is heading. Notice their mission of decentralization.

    Since agglomeration around a single instance is against the goals of Matrix and its Foundation, users need to have a way out and incentives to move.

    We are committed both to making Matrix more accessible, and to doing the work to decenter the Matrix.org homeserver.

    Matrix.org is meant to be an entry point, not a stopping point. As to your concern regarding built-in tools, matrix is just a spec, an open source federated communication protocol based on HTTP. The community builds tools. Matrix is not discord. In fact it is in opposition to the discord philosophy of centralization, data mining, advertising, and AI training.











  • I learned quickly that installing apps the traditional way causes pretty major instability. You’re basically rebasing the entire OS via ostree to install one application. After my second nuke and pave due to updates no longer working from me rebasing I took the time to learn toolbox so if a flatpak is not available I can still use an application (containerized) without altering the OS. Toolbox by default pulls in another Fedora install as the app base. I recommend using Alpine instead, much smaller and lighter.

    I guess the moral of the story is learn to install applications the correct way, or just don’t use an immutable OS