Nice work π I can easily see the usecase even without a giant monorepo: a typical MVC app (eg Django or RoR or Grails) which serves both the backend and frontend can easily see the benefit from this.
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.
TIL indeed!
Verb | Noun |
---|---|
Feedack from Emacs Matrix room:
The code will fail if a sequence contains duplicates
Also, seq-* implies that it is assuming to work on any sequence type, not just lists
Now that I know which endpoints I'm interested in and which arguments I need to pass, exporting them to Prometheus is my next step. Though I wasn't sure where to begin w/ - I was thinking about writing the HTTP requests in Java or Python and export the results from there.
Blackbox exporter is definitely easier and cleaner. Thanks for the tip π―
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.
OK, I think I see your point more clearly now. I suppose that's what many others do (apparently I don't represent the norm ever π.)
So tags can be useful for not only listening but also discovery.
I guess my concern RE tag & community competing. But I've got no prior experience designing a social/community based application to be confident to take my case to the RFC.
Hopefully time will prove me wrong.
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 $$$.
Would be lovely to have a download per release diagram along w/ the release date (b/c Summer matters in the FOSS world π)