That is also a product of many variables (including software quality). maybe time to go back to the drawing board.

For this project I’m mainly testing distribution models

What do you expect to learn from those so called tests? (no offence)

The big questions in closed vs open is that there are different scenarios :

for closed source -> less competitor -> more users -> more money -> more investment in the project -> better product.

for open source -> more users want to use it and contribute to it -> better software -> more users -> more potential for making money.

The problem is that for the outcomes you want to track (more money or better software). there are so many variable involved that influence those outcomes so it’s hard to deduce that the license is improving the outcomes or making them worst.

It’s another case of OSPNS - Open source projects names sucking .

List of servers (pretty small)

Not really, i did play around with it and added a few reviews and saw nothing like it.

neodb has other stuff besides books (games , movies ,podcasts, music ) , also bookwyrm license isn’t OSI approved which i don’t like (not looking to start a holy war on this, form your own opinion).

Example instance.

I don’t use GIMP really but i feel like this “gimp sucks” thing you read on social media is just a good example of how social media can be overly negative.

Two review websites (g2 , capterra) have thousands of reviews and the average rating is pretty good , around 4.3-4.4 out of 5.

it’s just that it doesn’t work efficiently enough.

Yeah, but we live in a world of limited resources. in particular labor and specifically knowledgeable linux nerds willing to answers questions for free. If everyone will have that mindset there won’t be a lot of time left to answer the difficult questions .

With that said i agree that occasionally if its done its probably no big deal, there is also linux 4 noobs for those who want to ask some questions to help getting started with linux.

Active users and number of servers also recently reach all time high.

If you want to learn how to create a good open source project for the fediverse. i think peertube is the best role model for that.

We have lemmy apps that still aren’t supporting API changes added over a year ago. We even had one such case last week.

That sounds like something could be improve. is there some sort of warning mechanism in place?

Say when using a lemmy client. the client either specifies its a production build. or if its not then the lemmy server reports where deprecated API’s are used.

Not sure that is the correct approach. break frequently break often seems better (that’s what PHP and java seem to do as far as i can tell, unlike python 3 which caused a lot of drama).

notify a API is deprecated. give some time for users to update to the new API (1 year?) and then remove it.

Of course after version 1.0 there might be less breakage so it won’t be a be problem.

This isn’t what i had in mind. i meant more like changing the line to something like:

We’d like to thank our many contributors and users of Lemmy for coding, translating, testing, donating money and helping find and fix bugs.

With “donating money” maybe replaced with “funding”.

We’d like to thank our many contributors and users of Lemmy for coding, translating, testing, and helping find and fix bugs

I feel like people giving their hard earned money for lemmy also should get a show of appreciation.