this post was submitted on 15 Nov 2023
5 points (100.0% liked)
/kbin meta
1 readers
4 users here now
Magazine dedicated to discussions about the kbin itself. Provide feedback, ask questions, suggest improvements, and engage in conversations related to the platform organization, policies, features, and community dynamics. ---- * Roadmap 2023 * m/kbinDevlog * m/kbinDesign
founded 1 year ago
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
This is one of the biggest issues and barriers to discoverability with the Fediverse in my opinion.
As I understand it, unless an instance has already subscribed to a community (magazine in kbin parlance), then in order to make that community (magazine) appear in your own instance, you need to:
Contrast this to reddit, where (because it's a centralised system) searching for a subreddit produces immediate results, you can join a subreddit immediately, and you can immediately see all current and past content for that subreddit. Much more intuitive and useful to users.
Unfortunately the activitypub protocol that underlies lemmy and kbin doesn't appear to have been designed for reddit-like communities in mind. Ie communities that tend to feature long-form content, posted relatively sporadically, and where having access to the community's archive is very useful to members. It works somewhat better for twitter-like communities where it's easier to jump in "mid-stream" and - because posts tend to be only a few words long - you're more likely to start seeing new content after only a short delay.
I wish that this is something that's addressed at the Fediverse level.
there actually is a way to "backfill" content, being the outbox. (although it was not meant to be used this way, from what i can see from reading what little documentation is out there)
lemmy uses it to federate about 10 or so (i think it was?) of the latest posts, and most microblog implementations use to federate the "pinned" posts of an account
activitypub has quite a lot of quirks, both spec-wise and implementation wise, and there are many reasons including an apparent near civil war inside the working group which resulted in this messy state it's ended up in
honestly the fact that this protocol works at all is a miracle
I'm a bit lost in the jargon. What is backfill and what is the outbox?
@Doll_Tow_Jet-ski@kbin.social I don't know if that's the official word for it but I'm using "backfilling" to refer to loading the history of a person or group after first federating with it.
the outbox is a special collection (list in activitypub speak) that's intended to work kinda like an old school email outbox where you put messages to be delivered and it would deliver them to the inboxes of people (and servers that were offline at that time would later pull them in from the outbox)
or, well, that's what the spec says. nobody uses it like that in reality because activity pub was intended for a completely different kind of social media than how it ended up being used (it seems to expect more "everything apps", including an entire client api that would completely abstract away the instance into nothing more than a dumb pipe for activities unlike the current reality where instance software dictate what you can do)
this probably confused you even more but it's getting pretty late here so I can't words good, sorry!