I’ve been recently thinking about the future of lemmy-meter and where should we go next from where we stand today.
It quickly became obvious to me that I’ve got no clue where do we stand today. I’ve been too caught up with my life (and possibly too lazy and distracted) that I never ran a survey to gather any sort of feedback.
Since many of you have been using lemmy-meter for more than a month already, I’d like to redirect the following important questions to you:
Strengths
What do you think lemmy-meter does right?
What are its strength?
In other words, what makes you enjoy using lemmy-meter (if at all)?
Weaknesses
Where do you think lemmy-meter falls short?
What are the things that make unsatisfied or even disappointed?
Potentials
Do you see any areas to explore that we haven’t touched yet?
Do you think lemmy-meter can expand to cover new realms?
What could be the ideas that would take lemmy-meter to next level?
Thank you, Your friendly neighbourhood observability enthusiast
Works well in browsers with images disabled. Interesting to see vector graphics pay off.
The most important info is here:
https://infosec.pub/c/isitdown
I don’t care about small variations in performance. I care when a server admin pulls the plug. Lengthy downtime can be infuriating, particularly without news… without knowing what happened and whether your msgs are lost permanently.
The presentation unfairly makes nodes centralised on Cloudflare look good. Cloudflare obviously makes a site perform well but the price we pay in sovereignty, loss of privacy, and netneutrality makes those nodes unacceptable. Centralisation defeats the purpose of the fedi. So the CF nodes should be delisted. Or well marked with a warning.
An open dataset might be useful.
You might want to harvest and present !isitdown info somehow.