this post was submitted on 04 Aug 2023
112 points (98.3% liked)

Asklemmy

43907 readers
1131 users here now

A loosely moderated place to ask open-ended questions

Search asklemmy 🔍

If your post meets the following criteria, it's welcome here!

  1. Open-ended question
  2. Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
  3. Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
  4. Not ad nauseam inducing: please make sure it is a question that would be new to most members
  5. An actual topic of discussion

Looking for support?

Looking for a community?

~Icon~ ~by~ ~@Double_A@discuss.tchncs.de~

founded 5 years ago
MODERATORS
 

After reading a bit about Usenet, it seems to me as if the whole Fediverse seems to be just a reinvention of Usenet.

What's the big difference?

you are viewing a single comment's thread
view the rest of the comments
[–] ryan@the.coolest.zone 15 points 1 year ago (1 children)

Actual attempt at an answer!

ActivityPub has actors and activities. These are very broadly defined - yes, a user is an actor, but so is a magazine in kbin. A like, a thread, and a microblog are all activities. These come from an actor, and they are sent to and cc'd to other actors in the fediverse.

NNTP, however, is not actor to actor, it's server to server, to my understanding.

In practice, the way this is implemented here, it's not that much of a practical difference, but it's interesting to know.

The other difference is that NNTP servers would forward messages to their other known NNTP servers, essentially creating a distributed network of information. Per the ActivityPub protocol however, no instance is obligated to do that on ActivityPub. The only obligation for forwarding is if a) The values of to, cc, and/or audience contain a Collection owned by the server (e.g. followers is a Collection) AND The values of inReplyTo, object, target and/or tag are objects owned by the server. So basically if I receive something from lemmy.world user actor, to lemmy.world community actor... Even if kbin.social hasn't received it and errored out, I have no obligation as the.coolest.zone to send it out to them.

[–] squaresinger@feddit.de 1 points 1 year ago

Thanks, at least one who got what I was on aboutˆˆ

Ok, so we got a push vs pull model and a bit more differentiation in the protocol. So there is at least some improvement on the concept. When reading about it, it felt like yet another reinvention, but looks like there is at least some improvement on the idea. Thanks for the summary!