It’s covers a pretty wide range of topics hence the bigger number…
Radium@sh.itjust.works 1 year ago
I miss the days when awesome lists were curated to actually have awesome stuff instead of being a list of 250+ self hostable apps.
There is no way these are all awesome. Call it the giant list of self hosted apps or something that actually makes sense.
stevedidWHAT@lemmy.world 1 year ago
Radium@sh.itjust.works 1 year ago
In this analogy, GitHub would be the library and the awesome list would be the recommended by the librarian section. If my librarian stopped curating that section and just filled it with a specific type of book no matter the quality I would stop browsing their curated section.
stevedidWHAT@lemmy.world 1 year ago
Again, large size doesn’t necessarily equate to being washed out…
matricaria@feddit.de 1 year ago
I would expect an „awesome-books“ list to not include every book ever written.
somedaysoon@lemmy.world 1 year ago
I read it as the lists are awesome, not necessary everything in the lists. Also, you are free to fork it and set your own criteria. But personally, I wouldn’t follow a list with bullshit, subjective criteria because I don’t want someone making those subjective decisions for me.
RustedSwitch@lemmy.world 1 year ago
Do you think it’s fair to say that one size does not fit all, so a giant list of self hosted options for people to choose from, is itself awesome?
c0mbatbag3l@lemmy.world 1 year ago
I’d rather a bulk list of everything that can be set up on a home lab, personally. I’ll decide what is and isn’t useful to me.
vegetaaaaaaa@lemmy.world 1 year ago
awesome-selhosted maintainer here. This critique comes up often (and I sometimes agree…) but it’s hard to properly “fix”:
Any rule that enforces some kind of “quality” guideline has to be explicitly written to the contribution guidelines to not waste submitters’ (and maintainers) time.
As you can see there are already minimal rules in place (software has to be actively maintained, properly documented, first release must be older than 4 months, must of course be fully Free and Open-source…). Anything more is very hard to word objectively or is plain unfair - in the last 7 years (!) maintaining the list I’ve spent countless hours thinking about it.
For example, rejecting new projects because an existing/already listed one effectively does the same thing would give an unfair advantage to older projects, effectively “locking out” newer ones. Moreover, you will rarely find two projects that have the exact same feature set, workflow, release frequency… and every user has different needs and requirements, so yeah, users of the list are expected to do some research to find the best solution to their particular needs.
If we started rejecting projects because “I don’t have a need for it” or “I already use a somewhat equivalent solution and am not going to switch”, that would discard 90% of entries in the list (and not necessarily the worst ones). I do check that projects being added are in a “production-ready” state and ask more questions during reviews if needed. But it’s hard to be more selective than we already are, without falling in subjective “I like/I don’t like” reasoning (let’s ban all Nodejs-based projects, npm is horrible and a security liability. Let’s also ban all projects that are so convoluted and impossible to build and install properly that Docker is the only installation option. Follow my thoughts?)
Another idea I contemplated is linking each project to a “review” thread for the software in question. But I will not host or moderate such a forum/review board, and it will be heavily brigaded by PR departments looking to promote their companies software.
A HTML version is coming out soon (based on the same data) that will hopefully make the list easier to browse.
I am open to other suggestions, keeping in mind the points above…
spez_@lemmy.world 1 year ago
Are the unmaintained apps stored anywhere? Sometimes unmaintained apps work fine for many years afterwards or consider themselves complete
vegetaaaaaaa@lemmy.world 1 year ago
These are usually kept for some time (or at least, not actively hunted and removed). You can also check pull requests labeled
curation
, or search the git log forremove
.