But why rewrite programs that existed for decades and have proven their stability and safety? Rewriting them to Rust won’t make them safer, it will just introduce the kind of issues original versions have got fixed long ago.

Of course rewriting them will introduce some new issues, but it will also eliminate classes of bugs from which there are definitely still a great many in old “stable” C code (bugs which are now being discovered and will presumably continue to be discovered at a much faster pace due to LLMs).

The whole project is about abolishing GPL. And Rust is just an excuse.

I don’t think it is just an excuse; I believe that improving security is also a goal… but removing GPL code is clearly also part of their motivation :(

No, it is not a good time. A project like Ubuntu should now be in freeze as they had about 3 months before release

This bug was reported (and resolved by rolling back to the GNU coreutils version of cp) on June 30, a little over 15 weeks prior to the scheduled release date.

Which distros have a feature freeze that far in advance?

Ubuntu hasn’t even scheduled theirs for 26.10 yet; if you edit that url to look at previous releases’ schedules you can see their feature freeze and debian import freezes are typically about 2 months prior to release. (See here for descriptions of all of the different types of freezes…)

What an absolute shitshow

I’d say the month of June is actually a good time to be breaking and fixing things in a release that is due to come out in (checks notes) October.

Beyond that, I recommend that you post on !nostupidquestions@lemmy.world or somewhere similar if you need people to explain why telegram is offtopic in communities about privacy technology. (This discussion is very offtopic in this thread so I won’t reply further here. If you really feel the need to argue about the above I recommend you do it in a new thread somewhere it isn’t offtopic; if you tag me maybe i’ll reply there.)

And I never got the actual reason

imo the reason is pretty clear in the modlog you’re linking to. the ban duration was disproportionate though, so, i just unbanned you. (please do not advocate for the use of telegram in !privacy@lemmy.ml though! lmao)

This led to a few larger instances blocking it (.world I think is the kargst to have done so) blocking it, so their users cannot access *.ml communities.

Huh? Lemmy.world has not blocked lemmy.ml, nor have (correct me if i’m wrong?) any other large instances.

Here is this very comment from me (on lemmy.ml) viewable on lemmy.world, btw.

The existing chess community on lemmy.ml/c/chess seems to be dead

it looks like !chess@lemmy.ml is averaging a few posts per month this year and has 2.4k subscribers; not very active but i wouldn’t call it dead.

moderators are not reachable

the mods do seem inactive; i and other lemmy.ml admins remove spam if/when it gets reported (which has happened four times this year). if someone (with some posting history) wants to be added as a mod of it just let me know and i’ll add you.

and is hosted on .ml which is defederated by many instances

huh? which instances have defederated lemmy.ml?

which music genres do you like?

Did you not read the post? OP clearly says:

I ran the numbers and I like every single music genre pretty much equally

😂

As others have said it is a huge amount of work to maintain a fork of such a complicated piece of software.

Especially around security: web browsers constantly process potentially-malicious data, which gives them a large attack surface. Every browser regularly has new vulnerabilities discovered which must be fixed. Hard forking a browser means that, even ignoring any bugs in the new code the fork has added, every time a bug is discovered and fixed in the code they forked from someone needs to analyze the upstream’s fix and port it to the fork. The more they diverge, the more work this is. Failing to do this work lets any malicious website exploit the bugs and install malware on users’ computers.

They absolutely eat bread

By “they don’t” the person you’re replying to means “they shouldn’t”.

Search for “bread” and “birds” to find thousands of web pages explaining why bread is bad for birds and you should not feed it to them.

sure.

moderator reports still don’t federate to other instances

you are mistaken. reports are federated from the reporter’s instance to the community’s instance, as well as to the instances of all moderators of the community, and to the instance of the user who posted the comment or post being reported.

colonies

If you think China colonized Xinjiang, well… yeah, they did. But that was 22 centuries ago, a millennium before the [people now known as] Uyghurs had even arrived there. The demographics and ruling empires unsurprisingly changed a few times in the ensuing millennia, but since the Qing dynasty committed the Dzungar genocide there (from 1755–1758, with help of several peoples including Han and Uyghur) it has mostly remained a part of China.

The ancient history is interesting, but more recent events (eg Al-Qaeda-affiliated groups the US has been funding there) are more relevant to the present situation.

I did watch the first three minutes. Everything he shows is true, everything he explains as interpretation is just full of shit.

What specifically is he full of shit about? I recommend watching more than three minutes of it.

Here and here are two texts on the subject which cover some of the same things as that video (albeit not from a first-hand person-from-the-US-traveling-in-Xinjiang perspective like the video does).

i recommend this recent video by Eric Hovagim to learn more about the Uyghur topic (but i guess you’ll probably skip it based on its title?)

that kernel release (which most distros have still not shipped yet) fixes only one of the two vulnerabilities (CVE-2026-43284); afaik even upstream still doesn’t have a patch for the second one (CVE-2026-43500) at this time.

(for people relying on Linux privilege separation, here are mitigation instructions.)