@_elena@juandesant in case it helps anyone: to avoid this conundrum I've first deleted my Twitter/X account, then waited for the "expiry" period, and finally then re-registered it as a fresh/empty account. (But of course it's risky for popular accounts that others might want to take over.)
Hey @nextcloud , I understand it's not your fault, but the fact that on #android Nextcloud can no longer remove pictures from local folders (e.g., DCIM) after upload is a major UX regression. Is there any workaround possible/planned?
"Il paradosso della scienza italiana, un’eccellenza in perenne agonia
Abbiamo i migliori ricercatori del mondo, ma più della metà se ne va e non torna. L’università è sottofinanziata, ora che finiranno i fondi del Pnrr rischiamo il tracollo"
New #paper out: « The impact of the #COVID19 pandemic on women’s contribution to public code » (Empir. Softw. Eng. 30(1): 25 (2025)) where we establish, using #econometrics techniques, that the pandemic disproportionately impacted women's ability to contribute to the development of public code, relatively to men. #Openaccess preprint at: https://hal.science/hal-04716803/
@flomaraninchi@ArneBab@zimoun specifically in FOSS, I think it comes from a culture of co-design with your user base, "having" to answer to user requests, bug reports, etc. It takes really experienced maintainers to say upfront "no" when a requested feature is not in line with the original vision (assuming there was one).
There's also Lehman's 1st law of software evolution, of course, but it is not clear cut on new features vs context adaptation (e.g., platform changes).
@zimoun@ArneBab completely agreed that that is a real problem. My point is that it is a problem that has nothing to do with software freedom. (In fact, software freedoms make it *better*, due to the right to fork, but that was not my point here.)
@zimoun@ArneBab To further that point, the decision of an upstream author of a FOSS software to change it in a way that is backward compatible (or incompatible) has no impact whatsoever on the freedom of modifying it by downstream recipients. (Unless the license is changed, of course 🙂.) And it does not impact either that freedom for the author themselves.
@zimoun@ArneBab it seems to me you are conflating the freedom of modification, which is in generally considered as something valuable for *downstream* in FOSS, with the fact that *upstream* author of a software can decide to change it in backward compatible or incompatible ways. The latter is true for any software, no matter its license, and I don't think that being FOSS has any impact on it.
Full professor of computer science at Polytechnic Institute of Paris. Co-founder & CSO Software Heritage. Free Software activist. Previously: Debian leader, Open Source Initiative board.