UPDATE: lemmy.ml is now on lemmy-meter 🥳

“Announcment”

It used to be quite common on mailing lists to categorise/tag threads by using subject prefixes such as “ANN”, “HELP”, “BUG” and “RESOLVED”.

It’s just an old habit but I feel my messages/posts lack some clarity if I don’t do it 😅

First off, I was ready to close the tab at the slightest suggestion of using Velocity as a metric. That didn’t happen 🙂

I like the idea that metrics should be contained and sustainable. Though I don’t agree w/ the suggested metrics.

In general, it seems they are all designed around the process and not the product. In particular, there’s no mention of the “value unlocked” in each sprint: it’s an important one for an Agile team as it holds Product accountable to understanding of what is the $$$ value of the team’s effort.

The suggested set, to my mind, is formed around the idea of a feature factory line and its efficiency (assuming it is measurable.) It leaves out the “meaning” of what the team achieve w/ that efficiency.

My 2 cents.

Good read nonetheless 👍 Got me thinking about this intriguing topic after a few years.

Update 1

Thanks all for your feedback 🙏 I think everybody made a valid point that the OOTB configuration of 33 requests/min was quite useless and we can do better than that.

I reconfigured timeouts and probes and tuned it down to 4 HTTP GET requests/minute out of the box - see the configuration for details.

🌐 A pre-release version is available at lemmy-meter.info.

For the moment, it only probes the test instances

• enterprise.lemmy.ml
• ds9.lemmy.ml
• voyager.lemmy.ml

I’d very much appreciate your further thoughts and feedback.

Agreed. It was a mix of too ambitious standards for up-to-date data and poor configuration on my side.

sane defaults and a timeout period

I agree. This makes more sense.

Your name will be associated with abuse forevermore.

I was going to ignore your reply as a 🧌 given it’s an opt-in service for HTTP monitoring. But then you had a good point on the next line!

Let’s use such important labels where they actually make sense 🙂

beyond acceptable use

Since literally every aspect of lemmy-meter is configurable per instance, I’m not worried about that 😎 The admins can tell me what’s the frequency/number they’re comfortable w/ and I can reconfigure the solution.

You can hit the endpoint /api/v3/site for information about an instance including the admins list.

Exactly what I was looking for. Thanks very much 🙏

Thanks for the link. Had no idea about that.

I’m nitpicking but can you properly quote your code?

A bit too long for my brain but nonetheless it written in plain English, conveys the message very clearly and is definitely a very good read. Thanks for sharing.

When i read the title, my immediate thought was “Mojolicious project renamed? To a name w/ an emoji!?” 😂

We plan to open-source Mojo progressively over time

Yea, right! I can’t believe that there are people who prefer to work on/with a closed source programming language in 2023 (as if it’s the 80’s.)

… can move faster than a community effort, so we will continue to incubate it within Modular until it’s more complete.

Apparently it was “complete” enough to ask the same “community” for feedback.

I genuinely wonder how they managed to convince enthusiasts to give them free feedback/testing (on github/discord) for something they didn’t have access to the source code.

PS: I didn’t downvote. I simply got upset to see this happening in 2023.

Thanks all for the input 🙏

I did a quick experiment w/ the APIs and I think I have identified the ones I’d need. Obviously, all is open source (GPLv3) available on github: lemmy-clerk

As the next step, I’m going to expose that data to Prometheus for scraping.

I still haven’t made up my mind as to what is a good interval. But I think I’ll take a per-endpoint approach, hitting more expensive ones less frequently.

So far I can only think of 4-5 endpoints/URLs that I should hit in every iteration as outlined in the post above.

web/mobile home feed
web/mobile create post/comment
web/mobile search

I think those will cover most of the usecases.

Thanks. Yes, lemmy-status.org was where I got the initial idea 💯

automatic list

For the website I’m thinking about, I’d rather keep it exclusively opt-in. I don’t wish to add any extra load since most of the instances are running off of enthusiasts’ pockets.

That’s a fair point 👍 I just wanted to point out that I’m not the author.

As I said, I very much like the idea. It helps raise awareness around the current trend of switching licenses to curb competition/make $$$.

I articulated my thoughts on the topic in a separate post: [DISCUSS] Website to monitor Lemmy servers’ performance/availability

Please share your thoughts/feedback over there.

a list or database of projects that were open but then closed down

That’s a great idea! Esp if the list is actively maintained & updated.

Since I am NOT the author of this extension, do you think you could write down your thoughts on the project’s issue tracker?

Created an issue on the repo: https://github.com/galdor/github-license-observer/issues/5

Yes, written communication is so tricky, esp RE sensitive topics like this. As a non-native speaker, I kind of knew I was going to mess it up, but I guess I just couldn’t help my OCD 😂

donate to you instance.

That’s a good sign of support and I’ve already done that 😎 Honestly the quality of the software and the friendliness of the community made it a no-brainer for me only a few days after logging in for the first time.

That said, I think there’s more I can do than my humble donation - I’ve got plenty of, hopefully, relevant experience under my belt and am eager to put it to good use for Lemmy.

Servers are expensive and improving reliability will increase hosting cost.

Definitely 💯

What I was trying to get at in my post was not rather improve the hardware or ask lemmy.ml folks to sweat more for free. By the gods, no! Rather I was suggesting that maybe w/ a couple of, hopefully, easy and not time consuming moves we could up our level at lemmy.ml. Though I realised what I was talking about, wasn’t among the main concerns of the community. Which is totally reasonable.