MinRes aren’t in the CBD, they’re out in Osborne Park.

I’m locking this post. There has been some good discussion within the comments, but I don’t believe the linked article is in good faith, and the discussion here is heading off the rails.

I disagree. Its deliberately inflammatory and offensive. I only leave the post here as responses such as this one have value.

This has upset the applecart at work today. Thankfully I’m just a lowly packet pusher, not a cloud jockey. 😀

Good bot.

Hmm sorry I can’t help. Though this sort of question may see a better audience over at Whirlpool. Much higher density of nerds over there 🤓

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:

I have no intention of every placing ads on aussie.zone. Should finances ever become an issue, I’ll send up a 🚩 with a stickied post.

For now, finances are fine 🙂

I was speaking in general terms, there is currently no “delete oldest content” functionality in lemmy, so far as I know. But yes I imagine it would simply mean that for any older non-local content, users would need to initiate a pull from its home instance somehow.

On the point of being unsustainable I disagree. Instances will need to find an equilibrium between cost/expense and retention of old content. The higher the revenue/cost tolerance, the older the content that can be retained. I expect most instances will end up purging non-local content after an amount of time, but retain local content as long as possible. Maybe I’m naive, but I have confidence that people smarter than me will come up with systems to do this. It may result in a usenet style setup where instances boast about their retention periods.

On your second point re: community contributions, I agree entirely. I’ve been very fortunate that there have been some generous donations from aussie.zone users, so I’m not worried about server costs at this point. Server costs will go up as data volumes increase, that is unavoidable. How the community decides to handle this in the future is the real question, based on what I’ve experienced so far I’m confident we’ll be around for a long time to come.

Streaming providers are known to have different bitrates in different regions.

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.

Check 12ft.io