Conversation

Notices

1. Embed this notice
   Totally with Ю ⁂ (yuliyan@nahe.social)'s status on Sunday, 19-Jan-2025 21:27:16 JST Totally with Ю ⁂

   One of the hurdles for new fediverse users is historic discoverability of content. For example, if we view someone's profile from a remote instance, we only see the posts dating back to the first federation with our home instance. If you are on a large instance this might not be a big deal. It is for smaller instances like mine though.

   #Mastodon #Fediverse #ActivityPub #Federation… (1/3)

   • Embed this notice
     Totally with Ю ⁂ (yuliyan@nahe.social)'s status on Sunday, 19-Jan-2025 21:27:14 JST Totally with Ю ⁂

     in reply to

     And I as a user I see what I would expect visiting a profile: The content the profile has published. Not only the content the profile has published at a point where someone caused federation from my instance.

     Why not make this a standard (opt-in) feature of the official front ends, apps etc.?

     "Fetch remote content directly, if available." (3/3)

   • Embed this notice
     Totally with Ю ⁂ (yuliyan@nahe.social)'s status on Sunday, 19-Jan-2025 21:27:15 JST Totally with Ю ⁂

     in reply to

     My Mastodon client ( Mona) has the ability to fetch historic posts directly from the remote instance into the app. (Source to front end). Without leaving my client I am able to interact with older content from a profile, that predates the moment of federation. It circumvents the need for my instance to have fetched the content. This seems so efficient. The content is fetched directly from a place where it is already publicly available. My home instance does not need to bother with it. (2/3)

     Tim Chambers repeated this.