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 :)

Can turn it off and find out. I’ve done this a few times, each time I’ve ended up turning it back on… I figure better brief downtime at a low usage time, than random downtime that may require intervention to resolve.

I’ll give as much notice as possible, whatever ends up happening.

All good questions, that I don’t have any answers to. Plenty of time to figure it out… I’ll probably be looking at the larger players to see where this goes, and what clarifying information the government put out next year.

Bugger

Yeah I like it too… but it was generating an abnormal amount of traffic. I’ll see if I can figure out what is going on… but mlmym is pretty basic, doesn’t seem to have much in the way of configuration options.

I especially like the look on this guy’s face…

Was told there would be puppies. A++ would view again.

Yeah… I understood outgoing federation of activities was linear FIFO. The new feature in 0.19.6 allows N instances of linear FIFO, with related activities federated in sequence.

Our outgoing activities go out very quickly, aussie.zone has a very low activity rate so remote instances don’t tend to get behind at all.

How a LW user replied to a current AZ post and had it show up here in a decent timeframe is a mystery to me, seeing as they’re still running their custom version of 0.19.3

I can only guess the order activities are federated in is random? Which doesn’t make much sense.

It’s configurable… defaults to 1 thread. Given we’re slowly catching up with LW during low activity parts of the day, I think 2 should be enough.

Not sure about the whole picture, but credit to Keating for bringing in compulsory superannuation.

0.19.6 includes many fixes and new features… the biggest for me is “Parallel federation sending”. This allows instance admins to send multiple federated activities in parrallel, rather than singly in series.

Not that its a real issue for other admins with activities from AZ, but I have set this to 2 for our outgoing activities.

Hopefully the lemmy.world admins will upgrade to 0.19.6 soon and do the same, this should allow AZ to catch up with activities from LW, and stay up to date. Over time as activities from LW have decreased we’ve “caught up” to within ~5 days of live. Doubling the rate that LW sends activities to AZ will help massively.