![](https://burggit.moe/pictrs/image/fee82de8-0f9e-4e6c-a729-85fa2b1b16ef.jpeg)
![](https://burggit.moe/pictrs/image/b6ca24f2-a12d-48b0-99a2-71d19c717d0d.webp)
Moar like, Dork mode! 😆 Jokes aside, this is really awesome. Thanks for making this!
>:3
Moar like, Dork mode! 😆 Jokes aside, this is really awesome. Thanks for making this!
Yeah, I saw. Very unfortunate that they couldn’t retain their users/data.
I saw this when I was lurking the admin chat. They’ve got a tough road ahead of them since they have so many users subscribed to so many communities on the fediverse. They’d have to unsubscribe and resubscribe to all of them to resume federation with each instance.
We were fortunate enough to have few members and very few subscribed communities when we swapped domains while we were just starting out. So it was no biggie for us.
That’s not how it works. Instances don’t cache images from other instances. If you hover your mouse over an image you can clearly see the site it’s hosted on is in fact not originating from the instance you’re browsing on. It works like Pleroma, Akkoma, Rebased, and other Pleroma forks.
IANAL, but I believe you can’t be held liable for hosting links to other images on a site, regardless if they’re embedded through the website’s UI. They’re not stored there, afterall. The client is rendering them.
All that gets cached, I believe, is the text and users from remote instances. And by cached, I mean stored in the postgres DB.
Might’ve been the recent update to 0.18.4 I did. Whoops.