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

Yeah I was also thinking about multiple users for this, but that's a terrible hack on so many levels...

Yeah that sounds good too, but it's not the same thing. I just want a client side filter for lists of communities. No need to involve AP or get consensus amongst many users/communities, just my preferences. If we want to get fancy, have some APIs to store these lists server side so or can with across clients - still strictly single user. It feels so simple I am tenors to get my hands dirty, but for one diving into a new project is usually quite since work and it hardly ever turns out to be as easy as it seems (then again the new python lemmylike thing already has it instance wide, so it at least is doable).

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.

As far as I know xwayland in plasma/kde already does that. However as it's KDE, it is most likely configurable and might not be enabled by default :P

Honest question out of interest: Are you doing moderation on lemmy? I just remember reading about admins/mods complaining about the lack of tooling, sometimes plain functionality (removal of certain things) for effective moderation. I am not doing any myself so that's very 3rd-party-ish knowledge (if you even want to call it that).

Outlook (no I don't want it) (still) (really not) (WTF I SAID NO)

Could you do your best dunk on ES for me please? Not as in factually great, just whatever. I (ab)use quite a bit in my work, and can't say I have particularly strong opinions/feelings around it either way - I could use some help to change that xD

Looks like a federated wiki, which is great. And not a Wikipedia alternative. What makes wikipedia wikipedia is not the tech. Social and knowledge problems can't be solved with tech ;)
As much as Wikipedia has issues, as the ibis announcement states, it also works in many places. And federating it won't help with the issues of bad moderation, quite the contrary. And as much as I like nutomic (thanks for syncthing-android ;) ), I don't hear many good things about the lemmy moderation story. So I have my doubts. Lets hope I am wrong. Plus anyway, federated wikis is a great thing to have, ignoring the whole Wikipedia aspect.

Is this a case of !whoosh@lemmy.zip on @douz0a0bouz and bunch of upvoters part, or on mine?

Also wenn ich die Änderung beim Care amendment (Rolle der Frau) lese, und meine link-sozial Biases spielen lasse, kann ich schon sehen warum man da Nein sagen würde: Da wird eine sinnvolle Änderung (Streichen der Reduktion der Frau als Mutter, und alleinige Verantwortliche für unbezahlte Care-Arbeit) mit einer starken Abschwächung des Schutzes eben dieser unbezahlten Care-Arbeit verbunden.

Vorher (emphasis mine):

[...] ensure that woman shall not be obliged by economic necessity to engage in labour to the neglect of their duties in the home.

Nachher:

[...] shall strive to support such provision [of care within the family].

Gut: Der Artikel betrifft jetzt Care in der Familie allgemein, ohne das auf Frauen/Mütter zu reduzieren. Schlecht: Vorher hat der Staat zu sichern, dass diese Care möglich ist ohne ökonomische Zwänge. Jetzt hat der Staat nur zu versuchen diese Care zu unterstützen. Das ist extrem viel schwächer, und löst bei mir alle Alarmglocken aus für eine neoliberale Abbau von sozialen Massnahmen. Persönlich bin ich ja dafür und halte es für gut für alle involvierten, wenn Elternteile arbeiten und Kinder in die Kita gehen, aber warum sollte das die einzige Variante sein: Viele möchten zu Hause sein und das finde ich auch ok. Und ich habe das Gefühl diese Haltung ist weit verbreitet hier, und in einer (ehemals?) sehr traditionell, katholischen Gesellschaft wie Irland kann ich mir gut vorstellen dass das auch so ist.

Allerdings sehe ich nichts dergleichen beim Family Amendment, also liege ich wohl eher völlig daneben mit obigen xD

Ähnliches nervt mich auch in der Schweiz bei Initiativen so häufig: Da werden extrem wichtige und gute Änderung häufig überladen. Manchmal ideologisch/absichtlich, aber manchmal scheint es mir auch einfach aus einer Übereifer hinaus: Aka "Wenn wir schon den Aufwand machen, dann doch gleich richtig". Und dann kommen halt auch Nebensächlichkeiten in die Änderung, die im besten Falle die Angriffsfläche erhöhen und im schlechtesten Fall ein Grund sind für viele abzulehnen, obwohl sie die Kernforderung eigentlich unterstützen.