This is a big problem. It creates the illusion that /c/cats on one particular instance is the real /c/cats.
This is the root of re-centralization and it must be pulled out.
This is a big problem. It creates the illusion that /c/cats on one particular instance is the real /c/cats.
This is the root of re-centralization and it must be pulled out.
Not 100%-
If, I subscribe to !lemmy@lemmy.ml on my instance, it replicates a copy of everything to me.
When lemmy.ml goes down, I can indeed still see and browse the content here. I can even comment/interact with it, (and, when lemmy.ml goes up- the changes should sync back to it)
What you are describing is just a local cache of !lemmy@lemmy.ml on your instance and it works only if it has been populated before the downtime of lemmy.ml. If lemmy.ml never comes back to life nobody can post to !lemmy@lemmy.ml proper. All the communities on in would be dead.