[-] [email protected] 1 points 5 days ago

Another web scraping bot blocked.

22
submitted 1 week ago* (last edited 1 week ago) by [email protected] to c/[email protected]

We've seen some issues with AZ again today. On investigating it looks like more DDOS/abuse traffic from overseas. I've applied the same sort of block as last time we saw this, and things appear to have returned to normal..

The sharp drop is when the "attack" started, the jump is when it was blocked... the red line is blocked requests.

11
Go Private? (aussie.zone)
submitted 1 month ago* (last edited 1 month ago) by [email protected] to c/[email protected]

Lemmy 0.19.11 (which I've just upgraded AZ to) has a new feature to allow regular federation, but require users be logged in to view content.

I'd like to gauge feedback from users on this. It will not add privacy, or limit the propagation of posts/comments etc. But it will limit AZ server resource consumption by bots or users that are not logged in.

Thoughts/concerns on enabling this feature?

Update: thank you all for your thoughts and feedback on this. We'll leave AZ as it is, though may use this feature in future if we need to mitigate attacks or other malicious traffic.

38
Issues 23/3/25 (aussie.zone)
submitted 2 months ago by [email protected] to c/[email protected]

Not entirely clear to me what is going on, but we've seen a large influx in traffic from oversea today. This has lead to high CPU and performance issues.

I've put in place a block to what seems to be the source of the traffic, but its not perfect and may cause other issues. If you see/hear of any please let me know here.

25
Upgrade to lemmy 0.19.8 (join-lemmy.org)
submitted 5 months ago by [email protected] to c/[email protected]

I'm about to restart services for this upgrade. Shouldn't be down longer than a few minutes.

33
submitted 6 months ago* (last edited 6 months ago) by [email protected] to c/[email protected]

I'll be working on upgrading aussie.zone to lemmy 0.19.6 today. All going well disruption will be brief, but there may be some performance issues related to back end DB changes required as part of the upgrade.

I'll unpin this once complete.

[-] [email protected] 34 points 6 months ago* (last edited 6 months ago)

Made some time at work, don't tell my boss...

Think of lemmy instances as countries: when you visit a country/instance you're expected to abide by their local rules, whatever they may be. And when users from other countries/instances interact with Australia/aussie.zone they're expected to behave in line with our rules.

Not agreeing with the population of a country/instance doesn't mean you can't visit it. If/When you visit, you can't expect them to adhere to your rules at home... or to apply their own rules consistently.. just like the real world.

Defederation of an instance will only be done when:

Legal- the instance is generating content that may raise legal concerns for Aussie Zone. For example porn.

Technical- the instance is generating content that may cause performance/security issues for Aussie Zone. For example large volumes of automated traffic or malicious traffic.

Trolls- an instance whose users predominantly interact in bad faith with communities outside of their instance.

I don't believe lemmy.ml meets any of these, their "quirky" politics are largely self contained on their own communities from what I've seen. If they're crashing aussie.zone communities and posting outside of our rules, please report them.

To address some comments in this thread (paraphrasing):

we should defederate instances with bad admins or admins heavily moderating alternative views to their own

So far as their actions do not trigger any of the defederation criteria noted above, they can do as they see fit (even if it does make hypocritical dickheads).

no incentive to create alternative communities
If there is no incentive, then it can't be a large enough issue to enough users.

pro-authoritarian bias
Given how simple it is for a user to block an instance for themself, I'd rather allow our users had the option to decide this for themselves. Some prefer to engage with people from an alternate perspective, for those that don't they can block the instance.

TLDR

Not defederating lemmy.ml at this point in time, if their user behaviour outside of their instance changes in future my stance may change too.

11
submitted 7 months ago* (last edited 6 months ago) by [email protected] to c/[email protected]

I've spun this up for fun, to see how it compares to the base lemmy UI. Give it a whirl, and post any feedback in this thread. Enjoy!

It could go down at any time, as it looks as though the dev is no longer maintining it...

edit: using this https://github.com/rystaf/mlmym

UPDATE Tuesday 12/11: I've killed this off for now. Unclear of why, but was seeing a huge number of requests from this frontend to the lemmy server back end. Today it alone sent ~40% more requests than all clients and federation messages combined.

14
submitted 7 months ago by [email protected] to c/[email protected]

Its been 6 months or so... figure its time for another of these. Keep in mind there have been some major config changes in the last week, which has resulted in the oddities below.

Graphs below cover 2 months, except Cloudflare which only goes to 30 days on free accounts.

CPU:

Memory:

Network:

Storage:

Cloudflare caching:

Comments: The server is still happily chugging along. Looking even happier now that I've properly migrated pict-rs to its integrated object storage config, rather than the bodged up setup.

RAM/CPU are all fine. Storage use is growing slowly as various databases grow. Still a long way from needing to purge old posts, if ever.

Cloudflare is saving less traffic these days, since Lemmy added support to proxy all images. Not a concern, well under the bandwidth cap for the server.

As usual feel free to ask any questions.

5
submitted 7 months ago by [email protected] to c/[email protected]

testing

38
Pictures are broken (aussie.zone)
submitted 7 months ago* (last edited 7 months ago) by [email protected] to c/[email protected]

I'm in the process of migrating images to a properly configured object storage setup. This involves an offline migration of files. Once complete, I'll start up pict-rs again. Until then, most images will be broken.

All going well this will finish by morning Perth time, and once up and running again may help with the ongoing issues we've had with images.

17
submitted 7 months ago by [email protected] to c/[email protected]

After some users have had issues recently, I've finally gotten around to putting in place a better solution for outbound email from this instance. It now sends out via Amazon SES, rather than directly from our OVH VPS.

The result is emails should actually get to more people now, rather than being blocked by over-enthusiastic spam filters... looking at you Outlook and Gmail.

11
REBOOTING (aussie.zone)
submitted 9 months ago by [email protected] to c/[email protected]

About to reboot the server, hold onto your hats.

[-] [email protected] 89 points 11 months ago

It was removed deliberately during the reddit exodus in order to direct new Lemmy users elsewhere. Rather than to overload lemmy.ml further.

26
Lemmy 0.19.4 (aussie.zone)
submitted 11 months ago by [email protected] to c/[email protected]

Hey all, following the work over the weekend we're now running Lemmy 0.19.4. please post any comments, questions, feedback or issues in this thread.

One of the major features added has been the ability to proxy third party images, which I've enabled. I'll be keeping a closer eye on our server utilisation to see how this goes...

[-] [email protected] 19 points 11 months ago

pict-rs upgraded to 0.5... which is now performing its own backend update. No idea how long it will take... currently ~7%.

[-] [email protected] 47 points 2 years ago

The way lemmy caches images isn't well documented. Some third party images are not cached, others are. I don't want to risk it.

Nuking it from orbit, only way to be sure.

[-] [email protected] 43 points 2 years ago

Tldr of what I've posted elsewhere; I'm undecided at this stage but leaning towards defederating. When more information is available I'll make a post soliciting feedback, I don't want to make a change like this without user feedback.

[-] [email protected] 21 points 2 years ago

When I looked there previously it looked like a bunch of mostly harmless cookers. Looking again now, I see hateful posts such as this:

I've now defederated them. The NSFW focused instances are defederated to minimise potential legal complications, ie to protect this instance.

[-] [email protected] 38 points 2 years ago

Mushroom mushroom!

Damn I'm old. For those too young, check this out.

[-] [email protected] 31 points 2 years ago* (last edited 2 years ago)

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.

[-] [email protected] 19 points 2 years ago

Many of the largest instances block lemmygrad. You can check by clicking the "instances link at the bottom of the page.

view more: next ›

lodion

0 post score
0 comment score
joined 2 years ago
MODERATOR OF