Yeah, I’ve gone over 24 hours now without it occurring… but not calling it “fixed” until at least a week.
I also have backup accounts on these instances:
https://beehaw.org/u/lodion
https://sh.itjust.works/u/lodion
https://lemmy.world/u/lodion
https://lemm.ee/u/lodion
https://reddthat.com/u/lodion
Yeah, I’ve gone over 24 hours now without it occurring… but not calling it “fixed” until at least a week.
I’ve been seeing similar since upgrading to 0.18. Upgraded to 0.18.1-rc.9 yesterday… haven’t seen it reoccur again… yet.
Here is an example I happened to be at my PC for:
Your instance must be very new, very few users, very inactive… or all of the above. I stood up aussie.zone just under a month ago, Postgres DB is currently 9.6GB.
Yep, that is nearly but not always the case.
Nope… thats what I’m talking about… image posts to remote communities, with the images being sourced from my instance. Like I said, next time I spot it I’ll dig into it further.
What software is your instance running?
Yeah profile pics are fine. I’m specifically talking about image posts. Next time I spot one I’ll see if the post came from a user on my instance. If not, I have no idea why the post image would be on my instance.
Yeah post content I understand. Linked or posted images though are not consistently handled, so I’m not sure what circumstances lead to my instance pulling the image from a remote community.
That may explain it… point being, content for remote communities isn’t entirely “remote”. I’d like to understand what goes where a lot better. I’ve not found it explained anywhere, and I’m not a coder so can’t just “read the code yourself”.
That isn’t entirely true. I’m not exactly sure why, but I’ve definitely seen image posts made to remote communities that are hosted on my instance.
I’m using S3FS to achieve the same thing, but without modifying the ansible config or using native object storage within pict-rs.
I like their sense of humour. The definitely don’t take themselves too seriously.
Good bot.