[-] toastal@lemmy.ml 3 points 3 months ago* (last edited 3 months ago)

Codeberg/Forgejo only supports Git for VCS which is a major downside. There’re good alternatives to Git, but their code forges are all pretty lackluster—and I continue to use them looking for tool/place to host.

[-] toastal@lemmy.ml 3 points 3 months ago

If it can’t run in a terminal, what is the point?

[-] toastal@lemmy.ml 3 points 3 months ago

Snikket is meant to be super simple to self-host. Ejabberd has a web GUI that can make configuration easier.

[-] toastal@lemmy.ml 3 points 3 months ago

Sony Xperia 5 III (has headphone jack) with LineageOS for microG. Shanling Q1 DAP/DAC. My everyday IEMs I take out of the house are Truthear Nova. I have a 10-year-old Ridge wallet & a mound of coins in the other pocket. Motorbike keys have nothing special other than an OnlyKey for TOTP/FIDO2.

[-] toastal@lemmy.ml 3 points 3 months ago

History / sync is known as message archive management (MAM) & every normal modern client & server supports it. OMEMO uses same double-ratchet encryption & multiple clients as Matrix (with the same old client key dropping issues sadly). By default it does not support groups you are correct, however, FOSS Jitsi (& Zoom for that matter) is powered by XMPP under the hood & can be stood up by yourself.

Personally three of my circles have opted for separate Mumble servers for voice coms (I run one of them from my living room) as video is only ever rarely needed & the system resources is minimal. Having web cams on is seen as a chore & distraction sometimes. The only time video is helpful in my experience is screen share which is different—but screensharing is the worst tool for trying to do code pairing / debugging a terminal using upterm provides a crisper view experience, lower data/system requirements, & observers can optionally drive the remote session.

[-] toastal@lemmy.ml 3 points 3 months ago

You could switch some of the problems with perf in switching away from the Python implementation server as well as Element clients but these support the most up-to-date features & the majority of users are now relying on these features that often don’t degrade graacefully.

The bigger issue is eventual consistency. Eventual consistency will not scale for small self-hosting. Every message & every attachment for every user in every chatroom they have joined must be duplicated to your server. This is why joining rooms sometmies takes 10 minutes. Even if you make this async from the client side instead of the current long wait, your server & storage are still taking the hit. A lot of small collectives had to drop their servers for performance & cost (read about yet another one today on the Techlore thread at c/privacy where now only Discord is used for realtime coms). This model is required to copycat the ability to search the entire history like the big, proprietary chat apps such as Slack/Telegram/Discord, but they are centralized so it is easier to manage—but its overuse for all announcement & trying to replace forums turns it into a black hole for information. Your small community probably does not need persistent chat like this—persistent info is lighter & easier to crawl as feeds & forums. With medium-sized servers shutting down, only the biggest & smallest hosts are still kicking with most metadata is largely centralized around Matrix.org who also hosts some of the other larger instances.

If you agree that chat can be chatter as well as ephemeral there is lightweight centralized chat in IRCv3 with TLS has most of the features you need with a longer legacy & massive choice for clients & XMPP for lightweight decentralized chat with a long legacy, client options too, & can be self-hosted in a bedroom on a toaster in comparison which increases the chances of self-hosters & decentralization. These were built in a time when we didn’t have such wasteful taste in tech since they needed to be efficient & only sip power/data in comparison both for clients & servers & storage. The bigger question IMO is what are fundamentally wrong with these two mature options that we need a new option built on unextensible JSON & Israeli Intelligence money?

[-] toastal@lemmy.ml 3 points 3 months ago

Exactly. Our words matter & the sooner we stop using Google to mean search or MS GitHub to mean code, the sooner we can start shifting the narritive towards entities that better respect our privacy or even gasp self-hosting. Word choice for social change is just as important for spreading the message.

[-] toastal@lemmy.ml 3 points 5 months ago

This is not so much as an edorsement or recommendation, but you might check out the DAPs by Shanling or Hidiz if you have coin to spare. They use Linux & don’t publish kernel mods, but they do have inexpensive, very small, lightweight options that may fit your needs. I have one & it has a place to have a dedicate device to not chew thru my phone’s battery as well as function as a high-quality USB DAC in scenarios where you don’t have a jack (like my old laptop) or the DAC is horrible (like in my dock for my laptop).

[-] toastal@lemmy.ml 3 points 9 months ago

Wut. It’s just as reproducible, flakes are mostly just a common unifying API with some extra CLI sugar for usability.

[-] toastal@lemmy.ml 3 points 9 months ago

You can use something like Nix + home-manager & take your environment with you.

[-] toastal@lemmy.ml 3 points 9 months ago

Obsidian’s fork of Markdown. Don’t expect compatibility.

[-] toastal@lemmy.ml 3 points 11 months ago

Linux is for all dresses. Configure your apparel like you do your distro.

view more: ‹ prev next ›

toastal

joined 4 years ago