Imagine if OP asked: “I want to repair/maintain my own car, but I don’t want to open the hood or get under the car. What are my options?”

Obviously there would be some options, but those options would be very limited and not ideal. This is very similar. Self-hosting, like self-repair of a vehicle, requires some foundational knowledge and understanding of your specific hardware, usecase, and needs, as well as the knowledge and ability to bring those things to fruition. There is no single universal answer that applies to everyone, but those skills can be acquired by anyone.

I don’t think self-hosting is any more doomed than self-repair of a vehicle. It’s certainly not for everyone, but it can be satisfying, rewarding, enjoyable, and generally optimized for those who choose to participate.

For those, like me, who wondered how much data was written in 400 picoseconds, the answer is a single bit.

If I’m doing the math correctly, that’s write speeds in the 10s-100s GBps range.

The article highlights on device AI processing. Could be game changing in a lot of ways.

Interesting and good to know, thank you for the info! I haven’t run into that issue with synapse yet, but I’m also running it in a docker container on an enterprise server. I also don’t currently have any chat rooms with more than 5 or so users, and I imagine that is also a factor.

How does this differ from something like synapse?