-
-
Notifications
You must be signed in to change notification settings - Fork 884
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Check to make sure Instances are live #2221
Comments
Seems like a good idea, especially in order to not keep sending dead instances activities. It is complicated tho by the fact that an instance might go down for a while, then come back up. @Nutomic might have some ideas. I'd rather it not have to be explicitly defined ( IE add the dead instances to the blocklist ), but that might be unavoidable. |
If its only about the /instances page, it should be easy enough to list only instances from which we received a new post in the last 30 days. |
It might go beyond that... that lemmy will try to push activities to instances that have been dead, potentially for more than a year. |
Yes thats a separate issue. |
* Check for dead federated instances (fixes LemmyNet#2221) * move to apub crate, use timestamp * make it compile * clippy * use moka to cache blocklists, dead instances, restore orig scheduled tasks * remove leftover last_alive var * error handling * wip * fix alive check for instances without nodeinfo, add coalesce * clippy * move federation blocklist cache to LemmyNet#3486 * unused deps
* Check for dead federated instances (fixes #2221) * move to apub crate, use timestamp * make it compile * clippy * use moka to cache blocklists, dead instances, restore orig scheduled tasks * remove leftover last_alive var * error handling * wip * fix alive check for instances without nodeinfo, add coalesce * clippy * move federation blocklist cache to #3486 * unused deps
Issue Summary
Re: https://lemmy.ml/instances
When you are looking through this list of instances, you find a lot of them are not active. This takes away from the user experience and could give a bad first impression to people.
My suggestion would be to run an automated check once a day or once a week and exclude them from the list if they are not active.
Examples of dead links included in the instances list:
https://eope.xyz/
https://forum.purplerabbit.xyz/
https://lemmy.161.social/
https://lemmy.2labz.com/
etc
The text was updated successfully, but these errors were encountered: