Comment on Is there a fix for, "This profile is from a federated server and may be incomplete."
modem_down@thebrainbin.org 1 week agoThanks for your reply. I should have been clearer!
It's not the banner that bothers me, it's the fact that that microblog's posts (toots) aren't being displayed when viewed from Mbin!
Is there anything I can do in order to get those posts to propagate through to Mbin? Would I have to contact the admin for the Mbin instance hosting my account? Something else?
You could type in the url of the post in the search bar, but if you follow a user their future posts will be sent to your server. We were talking about implementing a backfill option, but there is no eta yet, so no guarantee it will be implemented at all. But since it is an annoying problem, maybe it will
modem_down@thebrainbin.org 1 week ago
OK, got it. That's the reason I couldn't see those toots on Mbin.
Backfill would be great! (Server capacity concerns notwithstanding.)
In the meantime, clearer wording for the info banner would help:
Before subscribing: "This Fediverse profile is hosted on a different server than yours. If you, or another user on your server, were to subscribe to this profile, the profile's subsequent posts will be displayed here. The profile's older posts can be viewed on their server"
After subscribing: "This Fediverse profile is hosted on a different server than yours. Now that you have subscribed, the profile's future posts will be displayed here. The profile's older posts can be viewed on their server"
About backfilling, if @modem_down come across any yet unfederated links in the wild, maybe worth mentioning search links are standardized and hard-coded, making even redirect scripts efficient. Like e.g.
https://thebrainbin.org/search?search[q]=https://mastodon.social/@artologica@chaos.social/116986639666818550yieldinghttps://thebrainbin.org/m/random/p/829840(and using a remote link from a third instance to further make my point hehe).Though about the instance itself doing backfilling, it could be pretty taxing on both the requesting and requested instances, so I worry communications may get timed-out or the requesting instance may inflate to the point storage becomes a big concern.