Delta chat is hilariously slow. It’s less of an instant messenger and moreover next business day messenger. That’s ignoring the problems you’ll have running it on your own infrastructure.
Electric is not a discord clone and element has a customer base more similar to slack.
And to end encrypted direct messages have been the default for years now in Matrix.
Delta chat is hilariously slow. It's less of an instant messenger and moreover next business day messenger. That's ignoring the problems you'll have running it on your own infrastructure.
To go on top of the reverse DNS/mail comments, it can also be useful for running a service like codeburg pages, or some other program that handles its own virtual hosting and TLS, without interfering with your more traditional services.
The problem (as matrix people found out the hard way) is some media & content is very illegal. Most individuals really don't want even the chance of being exposed to CSAM or gore, and neither do server operators want the chance of that being shared from their server or written to their disk when that can result in police at the door. You need default-on moderation that is very powerful, and end users should never be distributing media they don't want to. This pushes towards centralisation of nodes run by experts, and heavily punishes true P2P models.
I use https://fedoraproject.org/coreos/ for my server/website. My host doesn't offer it as an image so I have to upload it myself, but I use an ISO I made with the CLI to automatically set up everything anyway. It works pretty well, I configured auto updates and I can just forget about it.
Regarding your first paragraph, this results limit is per page. To get the next page, you take your timestamp of the last item and use it in from_time, or whatever you've called it. It's still a pagination technique.
Regarding custom sorting, some of the techniques in the article can do this, some of them can't. Obviously timestamp based pagination can't, however the ID-based pagination that I mentioned can.
This whole article was sprung from a discussion of exactly that case, because users often simply don't delete notifications. It's very common for users to have years of undismissed notifications stacked up under the notification bell, and it's not a good experience to load them all at once.
Yep, that's the point described in the linked paper - traffic goes via the same domains used for their app, and the messenger is embedded in their app