probably, this caching is just affecting the default lemmy web interface.
other apps or web interfaces may have their own caching implementations, though for web based stuff it's typically fine to leave it up to the browser, as long as there are suitable cache-control headers sent by the server.
there were some caching issues in lemmy-ui where it would unnecessarily eat up disk space for caching without even making use of it properly. there was a change done in 0.19.12 that was supposed to mitigate this, but for users who have already collected this it won't automatically delete the unnecessary cache until they logout: https://github.com/LemmyNet/lemmy-ui/pull/3150
even when clearing this manually though i still see this take longer than you'd expect to load, it seems that the image cache is still slowing things down.
i also had some delays on images on the front page before all media loaded. i was able to speed things up again by executing await window.caches.delete("image-cache") in my browser dev tools console, but that is certainly not something to expect from regular users.
where are you located? do you have an example of things loading slowly? for me things are loading instantly, but if you're not within the EU you're likely dealing with latency across the globe
looks like kbin.earth has a broken setup at some point where their user profiles were using http instead of https urls and that results in random breakage in lemmy:
something doesn't seem to be right there. i can reproduce it with this comment but not with other comments they created. also, the comment doesn't show up on their profile.
I don't see us going down anytime soon, and at current user numbers I don't think there's going to be a major difference in moderation workload with the influx of users compared to what we already have, but it really is not great for decentralization. We already try delegating the majority of moderation to community moderators where applicable, where on a lot of other instances the admin teams seem to be more involved in addressing community reports on admin level as well. For the most part we're dealing only with instance level topics in the admin team and provide some additional tooling to improve report notifications to community mods. There are even various benefits from a moderation perspective when users are all local and not remote, as with federation a lot of signals that would allow various types of abuse are unfortunately lost. That said, I would still prefer if there were more stable and larger instances overall, while not having a single instance stand out as massively larger than any other one. Friendly "competition" is almost always beneficial for everyone involved.
lemm.ee being the second largest instance and the shutdown only being announced less than a month before is unfortunately also not something that gives people looking for a stable instance much confidence. I hope this won't scare too many users away from Lemmy and that most will just find a new instance in the Fediverse.
Instance moderation and moderation in general are unfortunately tasks that can be very challenging at scale, even with just a few thousand users, especially when dealing with drama. It's not really a surprise that there are somewhat frequently posts from larger instances looking for new admins, while older admins on the same instance are becoming less active. Even if people aren't exhausted from their involvement, their circumstances in life may change, or they may no longer be interested in Lemmy as a platform in general, leading to a number of reasons why admins may not be as active as it seems when looking at the list of admins in an instance sidebar. It's often a thankless job with a lot of things happening in the background to deal with spam, trolls and other issues, which most users won't even see when done right.
Would you say the old “mlmym” design is more attractive than the new design?
anything that is plain html and doesn't need js is more attractive for crawlers than things that aren't plain html.
historical comparison
this doesn't provide much historical context, it's just for the last 7 days
Are you saying most of the blue requests are bots?
one way or another, yes. we definitely don't have that many legitimate users trying to access it and then stopping when they get a cloudflare challenge.
Can you estimate how much it would cost to serve all the bot requests
currently no. this was a quick fix implemented when it got to the point that we couldn't handle the traffic anymore and lemmy.world was getting outages from the load caused by these criminals. the amount of crawler traffic we see also gets spikes here and there, so what might be enough today might not be enough tomorrow. they just don't care about anything but themselves.
we'll have to see. when you're logged in you'll have that cookie anyway.
due to the structure of the page it's a very attractive crawler target for those that don't care about robots.txt and pretend they're real browsers. they're hitting it from a range of different countries that even our initial attempts of limiting the challenge to certain countries was not useful.
even after implementing this challenge we're still getting lots of requests on this domain that all fail the challenge, 42k challenges issued within the last 24h and only 371 (0.89%) solved.
mlmym also doesn't seem to be that efficient with its api call usage per page load, so it would likely also need some investigation there if that can be optimized to reduce the server load from mlmym pages compared to other clients.
criminal ai crawler operators are killing the (public) js-free web.
currently, only accounts on the community instance get 100% report coverage, as they are sent only to the reporter's instance, the reported user's instance and the community instance currently. afaik this is supposed to get better with lemmy 1.0 eventually, but this is what we have to work with for now. resolving reports on another instance won't resolve them on LW, unless you remove the associated post/comment. this should however not impact visibility when you do check on your LW account.
report counts will show next to the shield icon in the top right, to the right of the PM/mention bell icon, if there are any.
there is a small possibility that our logic for sending these messages is incorrect, but you're the first person i see mentioning this while we've had this for a pretty long time already.
MrKaplan @ MrKaplan @lemmy.world Posts 0Comments 293Joined 1 yr. ago
probably, this caching is just affecting the default lemmy web interface.
other apps or web interfaces may have their own caching implementations, though for web based stuff it's typically fine to leave it up to the browser, as long as there are suitable cache-control headers sent by the server.