h3ndrik

Port forwards in the router + DynDns.

Though those leaks showed they actually did it on a large scale. I don't think they stopped for some arbitrary reason. Why would they? And technology developed further, surveillance is only getting easier. I'd say even without a tin-foil hat on, it's more likely they do it than not.

Well, centralization and giving up your freedoms, letting someone else control you, is always kinda easy. Same applies to all the other big tech companies and their platforms. I'd say it applies to other aspects of life, too.

And I'd say it's not far off from the usual setup. If you had a port forward and DynDns like lots of people have, the Dns would automatically update, you'd need to make sure the port forward is activated if you got a new router, but that's pretty much it.

But sure. if it's too inconvenient to put in the 5 minutes of effort it requires to set up port forwarding everytime you move, I also don't see an alternative to tunneling. Or you'd need to pay for a VPS.

Ah, nice. Alright. Thanks again. I'll see how I can do it. Unfortunately I've already set everything up, joined Rooms and connected a few bridges. I hope it doesn't break. I'll do a backup first. Seems reasonable and not that hard to upgrade.

Oh well, seems both reasonable. Maybe I should switch before the projects diverge too much. Conduwuit seems pretty active. Hope it stays that way.

Do you happen to have a link where I can read the backstory myself? Thanks for the info anyways. Seems to be a good call.

I found that. Seems it mainly addresses caching and database performance, adds some admin and moderation commands. I'm not sure if it addresses any of the shortcomings I have.

My main question is: Which one is going to be maintained in the years to come and have the latest features implemented? And secondly: Why a fork? Why don't they contribute their fixes upstream to Conduit?

Ah, well I only read the official documentation on https://docs.conduit.rs/

I'm gonna take a look at this later.

Depends a bit on how much images and videos get shared. If its mainly used for chat by a bunch of people and a few gifs and stickers in-between, it shouldn't consume that much storage. But sure if you frequently share all your vacation photos, the cache is going to grow fast.

Definitely the whole server name. Other servers and clients can't guess that information. I think it's properly documented how to do it.

I installed it like 2 weeks ago. As of now it's still running and has a really low memory footprint compared to Synapse. But a lot of things aren't implemented. Chatting works fine. I get a lot of warning messages about not implemented things, though. Like my client (FluffyChat) trying to query some profile status ... I'd say try it. I've done so. But I can really only give some good advise after a few more weeks of using it. Maybe there is a dealbreaker.

Nice, didn't know about HomeBox. Are there other good inventory systems for home use?

How is divorce a matter of consent?