devraza

Wouldn’t just using a temporary phone number service work? From what I remember, you just need to recieve a text message and put it into Signal during registration. From skimming through the post, there’s no mention of this option.

I would agree somewhat, except I think Bitwarden verifiably doesn’t store unencrypted password data. Of course, I think that a self-hosted solution is pretty much always more secure than one that isn’t, but the convenience Bitwarden provides is real.

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.

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’d just like to add that you can use a temporary phone number service to sign up to Signal as you only need a phone number to register, not to actually use Signal.

I don’t get i-

…

Or you can use a doas implementation like OpenDoas, or maybe sudo-rs…