As the statement says I wont - it will be fully discontinued. This statement applies to the official app only. It doesn’t say anything about other apps or forks - any existing once can and hopefully will continue to exist. Also all the code is free.
I am not the creator, funnily that is/was one of the Lemmy creators: Nutomic :)
I am a syncthing co-maintainer that kept the android app on life support since a while.
It’s all in the open, you can go dig around for reasons. As usual there wasn’t a single simple one. Neither was it some kind of complete fallout, we e.g. collaborated on translations and I have been in contact around various things with the one that forked.
Oh don’t worry to much, mine too: If there wasn’t an alternative for syncthing on android, I might have kept it on lifesupport :)
What?! All that noise about Switzerland mandating usage of open sourced software in gov (there was a great step, but it’s far from mandating anything) was already weird, now we are switching to linux? And caring about security and fiscal responsibility? There has to be another country called Switzerland than the one I live in.
That’s indeed confusing. The wording linked below suggests the eula is for packages distributed by owncloud. so to my understanding the source itself and any third party packages don’t need to care about it.
https://github.com/owncloud/ocis?tab=readme-ov-file#end-user-license-agreement
Oh dang, I got excited about a new update. Then I started getting deja-vus. And finally I checked the date: This is from early May. Still a good read, unless you already did read it before :P
Technically that wasn’t the initial entrypoint, paraphrasing from https://mastodon.social/@AndresFreundTec/112180406142695845 :
It started with ssh using unreasonably much cpu which interfered with benchmarks. Then profiling showed that cpu time being spent in lzma, without being attributable to anything. And he remembered earlier valgrind issues. These valgrind issues only came up because he set some build flag he doesn’t even remember anymore why it is set. On top he ran all of this on debian unstable to catch (unrelated) issues early. Any of these factors missing, he wouldn’t have caught it. All of this is so nuts.
Right. I was focusing on the point that what matters is the copyright notice. While your pointing out that you can relicense MIT code because MIT is so permissive, while you can relicense GPL to almost nothing, as it’s not compatible with most other licenses. However that’s kinda moot, you couldn’t include GPL code into an MIT licensed project anyway due to the copyleft.
(Thanks for the “ingenuous” correction, I did indeed - to my non-natively speaking brain the “in” acted as a negation to the default “genuous”, which yeah, just isn’t a thing of course)
Well yeah, that’s how licenses and copyright work - licenses can change. And sure on an adversary take-over (or corporate overloads taking control), that’s problematic. However the beauty is, it’s still MIT code: It can be forked (see what’s happening with redis). However a project copyright (and DCO) is not in place to enable just that, it’s in place to enable any license change by the project. Say a license is updated and there are good reasons for the project to move to the updated license - I think it’s pretty reasonable that the project would like to be able to do that and therefore retain copyright. Of course you are also free not to contribute such a project. However claiming it’s a license violation or unheard of is pretty disingenuous (formerly ingenious, thanks :) ).
This has nothing to do with GPL or MIT: If you own copyright of a GPL licensed code-base, you can change that license at any time. Of course that only applies to new code. And that’s the same for GPL or MIT or any other license.
Removed by mod