I hope this changes (even if a little bit) once Forgejo (FLOSS Gitea fork) adds forge federation.
Programming, cybersecurity, privacy, self-hosting, and some other stuff.
I hope this changes (even if a little bit) once Forgejo (FLOSS Gitea fork) adds forge federation.
I’m not sure - conduwuit does seem to have more active development but it’s not as though conduit is dead either…I also can’t find any other reasons to use conduwuit mentioned on its repository, so I’m just going to stick to conduit.
I’ve been using Conduit within a docker container for a while now, and it’s worked pretty well aside from the mautrix-signal bridge (this was fixed in version v7.0.0, I think). Other than conduit, I tried out dendrite, but the latency in sending messages was unbearable.
I’ve previously had issues with Matrix being incredibly slow and unreliable with federation (I’m self-hosting). However, that’s pretty much in the past now and I seem to have somehow resolved that issue.
I don’t get i-
…
Or you can use a doas
implementation like OpenDoas, or maybe sudo-rs
…
when you copy/paste a file on your computer it’s much faster than copying the file
I think you meant ‘when you cut/paste a file’?
This is a pretty good option, though I also think something like what aseprite has done is pretty good too (compile it yourself for free, or pay for a precompiled binary available through e.g. Steam) - from what I can tell this setup is fairly profitable.
KVM runs VMs pretty much like they are native
Well, it is a type 1 hypervisor…
Well, I’m not sure how many lines of C rm is written in but I think that rm being only around 4kb (iirc) is something to consider.
But still, storage probably matters least in this day and age. Oh, and…
something I used to completely nuke my home server
If I’m reading this right, then I hope you had backups ready :)
Nah, no way. :)
This probably isn’t the answer you’re looking for, but vpr
being memory-safe isn’t a benefit that it has over rm
, since rm
apparently doesn’t allocate any memory (as @radiant_bloom@lemm.ee wrote).
the first thing you mentioned as a benefit was memory safety.
Looks like I worded my project description poorly. As I wrote in another comment, I meant that this alternative is memory-safe (being written in safe Rust), but not that rm
isn’t.
edit: I’ve updated the post’s title to clear things up
I guess vpr -x
would be memory-safe that way then. ;)
I don’t know whether rm
is memory-safe or not, but vpr
is. By ‘memory-safe alternative’ I meant that this alternative is memory-safe, but not that rm
isn’t.
Gitea supports migrating from a variety of sources, but I’m not sure about a bot that does everything in one click or so. You could probably make a simple script for that, though.
Nope - it’s my own.
Right now, you’d need to install Neovim packages through home-manager to get anything working, though.
But it’s still possible to give an estimate knowing a little bit about the hardware, right?
Happy to hear that you like it :)
You could host on Gitea and mirror to GitHub. Obviously, users may be less inclined to sign up to your Gitea instance, but I hope people being unwilling to register becomes less of an issue once Forgejo (Gitea fork) implements forge federation.