Users who use the website that the community is hosted on have access to the full library of it. They need to boost stuff. And people who subscribe from remote sites need to boost older content that they’ve seen.
but relevant users cant see it, its never fetched for them to see it. Sure users on the home instance can see it, but they’re on the home instance, it’s already fetched for them. Ive run into this problem on here, where there is a lot of content on other instances that isnt visible from kbin. I have the option of visiting the home instance to see it, but it takes me completely off of kbin, I cant boost it from that page.
Someone just needs to follow. The community owner either needs to seed the community to big instances using accounts on them, or people who find the community via other instances need to subscribe and know that fresh content will come. Then they can boost older content from the hosting site.
Things take some conscious effort here. That isn’t necessarily a bad thing.
“Then they can boost older content from the hosting site.” No that’s the problem. Like you yourself said back catalogues arent fetched. They can’t see the older content to be able to boost it, they’ll only see new content.
If my instance follows a community at time t = T, and your instance starts following it at time t = T+10, I can boost content posted between T and T+9 so that you can see it.
Meanwhile, if people on the hosting instance boost things posted from times earlier than T, we both get to see them. Then, once they’re visible to us, we can continue to boost them for new instances to see.
Users who can see the content need to boost it?
Users who use the website that the community is hosted on have access to the full library of it. They need to boost stuff. And people who subscribe from remote sites need to boost older content that they’ve seen.
but relevant users cant see it, its never fetched for them to see it. Sure users on the home instance can see it, but they’re on the home instance, it’s already fetched for them. Ive run into this problem on here, where there is a lot of content on other instances that isnt visible from kbin. I have the option of visiting the home instance to see it, but it takes me completely off of kbin, I cant boost it from that page.
Someone just needs to follow. The community owner either needs to seed the community to big instances using accounts on them, or people who find the community via other instances need to subscribe and know that fresh content will come. Then they can boost older content from the hosting site.
Things take some conscious effort here. That isn’t necessarily a bad thing.
“Then they can boost older content from the hosting site.” No that’s the problem. Like you yourself said back catalogues arent fetched. They can’t see the older content to be able to boost it, they’ll only see new content.
If my instance follows a community at time t = T, and your instance starts following it at time t = T+10, I can boost content posted between T and T+9 so that you can see it.
Meanwhile, if people on the hosting instance boost things posted from times earlier than T, we both get to see them. Then, once they’re visible to us, we can continue to boost them for new instances to see.
This seems needlessly convoluted.
This is why the functionality was hidden behind the upvote button initially, but people wanted the arrows to match the arrows on Lemmy.