Comment on Annual General Thread
Nath@aussie.zone 2 days agoI’ll pay the imgur thing. It happened during school holidays and we went away for the (WA) long weekend in there as well.
I did have a shot at looking into it, but didn’t try very hard. I didn’t really prioritise it, because it only seemed to affect thumbnails and even then, it wasn’t consistent. I didn’t see it as that big of an issue.
The lemmy.world lag drama was more nuanced. It’s not a time issue, rather the precedent that one would require. We would have needed to spin up a new server somewhere close to lemmy.world in Finland, batch their feed and send it home. All for an issue with one remote instance that the Lemmy devs said was about to be fixed.
We didn’t want to eat into the finances for a temporary problem. Had we known in May that it would take until November to resolve, we may have made a different call. But the point is that one wasn’t a time problem.
Baku@aussie.zone 2 days ago
Thanks for sharing your perspective. I do politely disagree with the statement it wasn’t that big of an issue, as from what I could see, it completely prevented every Imgur image post from loading, thumbnail or not. Perhaps you mean the pictrs troubles (which are still intermittently happening, but primarily affect thumbnails and although annoying aren’t dire)?
Perhaps I’m mistaken, but Lodion specifically mentioned it was a time not financial problem when asked 3 months ago. I’m pretty sure there was a similar response when it was asked previously, as well
lodion@aussie.zone 2 days ago
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.
Blaze@feddit.org 2 days ago
I’ve been following this from far away, what were the factors that solved the issue if LW didn’t update?
lodion@aussie.zone 2 days ago
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.