Fediverse

19 readers

2 users here now

This magazine is dedicated to discussions on the federated social networking ecosystem, which includes decentralized and open-source social media platforms. Whether you are a user, developer, or simply interested in the concept of decentralized social media, this is the place for you. Here you can share your knowledge, ask questions, and engage in discussions on topics such as the benefits and challenges of decentralized social media, new and existing federated platforms, and more. From the latest developments and trends to ethical considerations and the future of federated social media, this category covers a wide range of topics related to the Fediverse.

founded 2 years ago

Is there a way to populate an magazine with posts from before the first person on an instance subscribes to it? (kbin.social)

submitted 1 year ago by Rainbright@kbin.social to c/fediverse@kbin.social

3 comments fedilink hide all child comments

I recently subscribed to pensandpaper@lemmy.ml on kbin.social. I was the first person to do that as it was clear that the kbin copy was created with me clicking subscribe. It's not a very active community with only two old posts but the only way to see those is by going to the original instance that it's hosted on.

Is there a way to pull those two posts to the kbin version of that community? Or is it inherent to the Fediverse that things only start syncing with the first subscription on an instance and it's not retroactive?

Let me know if there is a better place to ask this question.

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

[–] CodingAndCoffee@lemmy.world 0 points 1 year ago (1 children)

In a word, no

[–] 0x1C3B00DA@kbin.social 0 points 1 year ago (1 children)

This is accurate for the current state of lemmy/kbin, but there are ways it could be done. Mastodon made the decision to only fetch posts made after subscription/follow and all fediverse services have followed that pattern. But they don't have to.

In ActivityPub, Actors (users and communities) have an outbox property. Any public post that actor makes should be available in that outbox. So when a user follows a user or community, their server could request a page by default, which wouldn't be too much data, and present a Previous button in the UI that would fetch another page on demand. Since this would be a user interaction, it would happen later than the original follow and outbox request and would keep the requests spaced out so it doesn't overload a server.

[–] Rainbright@kbin.social 1 points 1 year ago

That's very helpful and makes sense. Thanks!

Hopefully we can add that to @ernest's ridiculously long and ever growing feature request list.