I think the key concepts are “at scale” and paying for that scale. Getting someone “to pay” to support a product can take many forms. Subscription is a big one and probably the one that comes to mind immediately because of Patreon, etc. but when one hosts their own Mastodon instance or if they would host their Lemmy server, etc.; one is still paying indirectly for the product in terms of web hosting, admin time, ISP, certs, etc.
I’ve worked on some open-source software products in the past (back in the early 2000s) and you are right, we didn’t need sponsors. We had a paypal address in the readme.txt file that someone could donate to if they wanted (which never happened) but it was also software that installed on one’s linux box. There was no ongoing cost to maintain it from version to version, what you got in that version was what you got and if there were bugs or features that should be added then that is why it was open source. A web application (albeit an open source one) seems like a different animal to me. Maintaining an open-source application on the internet is inherently more cost and potential liability as well as the potential for the damage that can be done through a vulnerability or compromise being higher.
I don’t have any answers and like you, I am happy to be corrected, but it seems to me that to have BOTH scale and still remaining FOSS for a web-based application: you either need to have a subscription or you need to distribute “cost” through a federated model where people are still “paying” but in a different way by eating the overhead collectively.
I think the key concepts are “at scale” and paying for that scale. Getting someone “to pay” to support a product can take many forms. Subscription is a big one and probably the one that comes to mind immediately because of Patreon, etc. but when one hosts their own Mastodon instance or if they would host their Lemmy server, etc.; one is still paying indirectly for the product in terms of web hosting, admin time, ISP, certs, etc.
I’ve worked on some open-source software products in the past (back in the early 2000s) and you are right, we didn’t need sponsors. We had a paypal address in the readme.txt file that someone could donate to if they wanted (which never happened) but it was also software that installed on one’s linux box. There was no ongoing cost to maintain it from version to version, what you got in that version was what you got and if there were bugs or features that should be added then that is why it was open source. A web application (albeit an open source one) seems like a different animal to me. Maintaining an open-source application on the internet is inherently more cost and potential liability as well as the potential for the damage that can be done through a vulnerability or compromise being higher.
I don’t have any answers and like you, I am happy to be corrected, but it seems to me that to have BOTH scale and still remaining FOSS for a web-based application: you either need to have a subscription or you need to distribute “cost” through a federated model where people are still “paying” but in a different way by eating the overhead collectively.
deleted by creator