this post was submitted on 06 Sep 2023
2 points (100.0% liked)

Community Meta Discussion

725 readers
4 users here now

founded 1 year ago
MODERATORS
[email protected]
2
Not seeing posts in subs from other instances--Where's the problem? (ttrpg.network)
submitted 1 year ago by [email protected] to c/[email protected]
5 comments fedilink hide all child comments
 

Basically what I said. This is the latest episode in the main speedbump I keep hitting with lemmy.

I'm trying to follow broadly when new TTRPG instances crop up. (DIYRPG.org is the latest I know of, and the one I'm currently having trouble with.) When I navigate to the communities from my ttrpg.network account, I can't see any of the existing posts.

So is the problem on this end (ttrpg.network isn't asking for the content) or their end (diyrpg.org isn't sending the content)? And is there anything I can do about it?

If this can't work smoothly, I'd at least like to know how it works.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 1 points 1 year ago (2 children)

Aha. I guess it's just that. So if I want to interact with the stuff that's already there when I subscribe, I'm out of luck?

[–] [email protected] 2 points 1 year ago

I'm not an expert on the subject, but you can kind of force a sync by using the search option.

example

I just put the url from a part over there https://diyrpg.org/post/246 in the search box in our insurance and it started showing up here (without any of the comments)
Presumably, older comments could be synced manually with a link too, but that sounds like a lot of work and I haven't tried it.
If there a specific comment you wanna interact with is not too bad, don't this manually for all comments doesn't sound fun.
I think there might be browser extensions to "open this in your preferred instance" but I haven't tried any.

Silver lining is that stuff that happens after you first added the community should be more seamless.

[–] [email protected] 2 points 1 year ago

yeah, the above is likely the issue. If there's a community with 0 subscribers on on this instance, then none of the content will sync. As soon as there is at least one subscriber here, all new stuff will begin to sync, but it will never sync the history over unless you explicitly search it out as mentioned below. This is how Lemmy is designed to work, and i assume the reason is because syncing a huge back-catalogue could be very problematic from a resources perspective.