You’re wrong, I’ll leave it at that. Won’t be replying any further.

Thanks, I hadn’t seen this one. I’ve updated our nginx config and AZ now passes the test on that page. No idea if it will help with GIFs etc.

With the resources available its not feasible for AZ to develop/deploy custom solutions that can be resolved by remote instances with trivial configuration changes.

I’m not going to address specific parts of your post, suffice to say I disagree on almost everything you said.

As I said previously, if you have a workable solution please do devlop it and submit a PR to the lemmy devs. I’d be happy to try your suggestion should they roll it in.

You’re contradicting yourself there. By definition adding an external service is a customization to lemmy. I’m not interested in running un-vetted software from a third party.

This has been discussed previously with a request from a reputable source to batching content from LW. That setup required an additional server for AZ, close to LW. And for LW to send their outgoing federation traffic for AZ to it, which then batched and send to the real AZ server. This offer was declined, though appreciated.

I’ve been transparent and open about the situation. You seem to think this is the fault of AZ, and we’re willfully not taking an action that we should be taking. This is not the case.

As it stands the issue is inherent with single threaded lemmy federation, which is why the devs added the option for multiple concurrent threads. Until LW enable this feature, we’ll see delayed content from them when their activity volume is greater than what can be federated with a single thread. To imply this is the fault of the receiving instances is disingenuous at best, and deliberately misleading at worst.

Note I said lemmy AND the activitypub protocol, ie lemmy does not currently have this capability. If it were added to mainline lemmy I’d be open to configuring it, but its not so I can’t.

The root cause of the issue is well understood, the solution is available in lemmy already: multiple concurrent outgoing federation connections to remote instances. AZ has had this configured since it was available. LW have not yet enabled this, though they’re now running a version that has it available.

Appreciate the offer, but I’m not interested in customising the AZ server configuration more than it already is. If you write it up and submit a PR that the main lemmy devs incorporate, I’d be happy to look at it.

That isn’t how lemmy and the activitypub protocol work. Source instance pushes metadata about new content, remote instance then needs to pull it. If we’ve not received the push yet, we can’t pull the additional info.

And for anyone curious… blue line is traffic from a country we don’t normally see much traffic from. The unusual spike, then drop when I blocked the specific sources:

The traffic stopped a few hours back, from all IPs at once. Definitely seems to have been some sort of deliberate action.

The unusual traffic all appeared to be coming from one location on the internet, with the same user agent string. Any traffic from that network will now receive a captcha from Cloudflare. I’m not aware of any lemmy instances hosted there, but will keep an eye on things.

For some context, CPU usage jumped when the traffic started… and dropped after the block was applied:

It sure doesn’t feel like autumn so far

Not sure how I should feel that the bubble I live in seems far more accepting and empathy towards asylum seekers.

I don’t think the people I live/work/socialise with are particularly extreme… but according to this we’re collectively not representative of wider Australian views.

I choose to believe their sampling was flawed and somehow only sampled the worst of us.

If you’re posting as an uninvolved third party about an event you’re interested in, it’s not an ad.

As for spam, if you post a ridiculous volume about such events it could be construed as spamming. So long as you’re manually posting this shouldn’t an issue.

Basically, don’t be trying to sell anything or abusing the AZ site.

Don’t get me wrong, I’m happy you posted this. If there are unvoiced concerns or issues, here is a good place to discuss them.

I’m not as active on lemmy as I’d like, so I’m likely not aware of issues unless they’re raised somewhere like this.

For potential meta issues such as age verification, I’ll be seeking input from the community when they arise and information around them is known and understood.

The volume of activity from LW reduced, and it also looks like they made some config changes on their side… at a guess more federation worker processes, allowing an almost constant stream of activity to be sent to AZ.

When the LW lag issue was previously discussed, my main constraint was (and still is) time. Longer term it would have been a financial concern.
Either way, the issue has cleared up now due to a number of factors, none of which required time or finances on our part. I call that a win.
Worth noting, LW have still not upgraded their instance to the version that introduced multiple sending threads to a remote instance. If their volume of traffic were to increase substantially again, we could “lag” again.

I’m happy to hear feedback, but tbh you should think of AZ as a benevolent dictatorship rather than a democracy. So the analogy to a company AGM isn’t quite right 😃

Sure.

Finished.

A minor Christmas miracle… AZ is no longer behind on LW content:

Hopefully this stays the case :)