Post #1274586

2026-02-25 23:08 UTC

@Texan_Reverend @rockario Would it be possible to have those posts from local storage still be available to pull from their originating instance? So, alice@masto.soc posts a picture, nobody sees it, it gets purged, two years later, bob@mato.soc is flipping through alice's posts, gets to the end of the local storage, kind.soc throws off a "hey, gimme the next hundred posts and I'll store them again", then they get purged? that way history can still get cached locally, but preserved?

Replies (2)

@Texan_Reverend@kind.social 2026-02-25 23:53

@blackcoat @rockario The short answer is that the backend doesn't currently work in a way that would support that. I think it could be useful to have some method of asking your own server to check for more posts on a remote user's profile, similar to the current system for loading more replies to a post when they've been found. However, the way it works now is that a server stores new posts from remote accounts after those accounts have become known to it - through user searches, follows, etc.

Open ##1274587
@Texan_Reverend@kind.social 2026-02-26 00:00

@blackcoat @rockario I also want to make sure something's clear. In your example, you had someone on a remote server looking for the posts of someone else on that server; that wouldn't involve Kind.Social's server settings at all. I'm assuming you meant something like: Old posts from alice@mastodon.social get purged due to lack of interaction. Then, blackcoat@kind.social scrolls their profile, reaches the end of stored posts, and wants Kind.Social to pull remaining ones from Mastodon.Social.

Open ##1274588