Fediverse

27910 readers

3 users here now

A community to talk about the Fediverse and all it's related services using ActivityPub (Mastodon, Lemmy, KBin, etc).

If you wanted to get help with moderating your own community then head over to [email protected]!

Rules

Posts must be on topic.
Be respectful of others.
Cite the sources used for graphs and other statistics.
Follow the general Lemmy.world rules.

Learn more at these websites: Join The Fediverse Wiki, Fediverse.info, Wikipedia Page, The Federation Info (Stats), FediDB (Stats), Sub Rehab (Reddit Migration), Search Lemmy

founded 1 year ago

MODERATORS

[email protected]

100

Why do a lot of fediverse instances put their software (i.e. Lemmy/Mastodon) in their name somehow? (lemm.ee)

submitted 11 months ago* (last edited 11 months ago) by [email protected] to c/[email protected]

59 comments fedilink hide all child comments

It kind of makes me think of how odd it would have been if many of the old forums named themselves like bookclub.phpbulletin.com, metalheads.vbulletin.net, or something.

There's nothing wrong with doing that, obviously, but it's struck me as another interesting quirk of fediverse instances/sites. Generally as soon as you visit them you can tell by the site interface or an icon somewhere what software they're using.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 1 points 11 months ago (1 children)

That sounds a lot like an ISP,

No, that sounds exactly like Nostr, which is a lot more practical and cheap to run that a Mastodon server and actually scales quite well.

moving all your storage to the edge is usually a bad idea.

No. You just need to move the application state to the edge. Storage itself can still be in content-addressable data servers, like IPFS, magnet links or plain-old (S)FTP servers.

When someone posts a picture on Mastodon, the picture itself is not replicated, just a link to it. Now, imagine that your "smart client" version of Mastodon (or Peertube, or Lemmy) wants to post a picture. How would it work?

User posts the photo to an IPFS server. It could be a cloud server or it could be their own NAS they have it running at home.
The uploaded photo generates a hash.
Client takes the hash of the photo and puts in the message.
Client signs a message and send to the server
Server receives the message, processes it (index metadata, puts the image in its cache to help with seeding, etc)
The server has a policy of keeping the image in the cache in the outbox until it has been delivered to at least 70% of the other clients or 5 days, whichever happens first.

I think that servers are needed.

If by "servers" you mean "nodes in the network that are more stable and have stronger uptime/performance guarantees", I agree 100%. If by "servers" you mean "centralized nodes responsible for application logic" then I'd say you can be easily be proven wrong by actual examples of distributed apps.

[–] [email protected] 1 points 11 months ago

Looking at nostr, I generally like the architecture, although the it's very similar in broad strokes.

I like the simplification and separation of the responsibilities. I don't like using self signing as an identification mechanism for a social network.

But crucially it seems like it has the same problem we're discussing here, wrt different social networks based on that protocol, having different message schemas and capabilities, making them incompatible.