No way… ‘boring’ is their takeaway oneliner? i can only imagine that such headline is meant to steer the lazy reader away from actual thinking.

I’d expect the actual interview (which now happened) would be posted already, to be disected etc.

Do you have any idea why that isn’t happening?

Here’s a howto https://lemmy.ml/comment/459391

Nowadays doesn’t even make any sense to use servers. … Why not create something better?

i think you might underestimate the problem.

Jami.net (a decentralized messaging app) works p2p. it uses a torrent-like distributed-hashmap to locate the peers at any moment. (The main usability issue for nontechnical users, is that devices on an internal ip address aren’t addressable from outside. This requires (a single point of failure and privacy concern), a turn-server)

They started to incorporate Git for merging chats for the reason that any of set of peers (of a group chat) can be out of reach of another set of peers, i.e. the chat continues on different branches and needs to be merged again later.(this happens in the clients-app, because there is no central server). Jami is aiming at double-digit group sizes… That’s not nearly the size of what Lemmy is handling.

Documentation etc can be found from their github page

https://github.com/LemmyNet/lemmy

Maybe a developer is better suited to answer that question. @[email protected] i’d assume there’s a difference in load in the backend and load on the frontend.

if you’re a registered user on a server, when you click [Communities], there you can see

• [local] communities - Those created on your server
• [all] communities - Those local and also those already federated to your server

You can subscribe to a community of any server which your server can federate with. The list of connected servers you can find via the /instances link at the bottom of the page.

There’s an easy to use community search tool here https://browse.feddit.de/

If you’ve found a community you like to follow, translate the original URL to a federated URL You do this by putting the community URL of the original server in the search bar; e.g.

(This search functionality is available in the web interface, but not yet available in the Jerboa app)

The result will list the federated URL. A federated URL has the form:
https://<your server>/c/<community-id>@<other server>

Visiting the federated link, and clicking [Subscribe] will make that community be federated to your server from now on. Your subscribed community will now also be listed under the [all] communities listing on your server.