“Protecting our community," by destroying it. If you don't have a community, then it can't be toxic. Were the comments so bad that this was the only solution?

Exactly what I expected from them. The same interests that want chat control are here as well.

This sort of thing is the reason that the kernel has its own cve authority / cna now.

It's interesting, that it would be hard to make a case that there was a "vulnerability" in the ip package. But it seems like this package's entire purpose is input validation so it's kind of weird the dev thinks otherwise.

Yes, input validation, probably for forms. What the Dev disputes is that he cannot see a case where it is used in a security critical way where

1. the input format is unknown and
2. it is essential to know if the IP is public or private.

I don't know how it compares to nsxiv, but imv supports Wayland.

If you need arm, then you probably have to install libhoudini https://github.com/casualsnek/waydroid_script

With usb-c you should be able to load a driver that allows network connectivity regardless of otg mode. Or was it Thunderbolt?

Update: I thought of thunderbolt-net which works with Thunderbolt 3 and probably USB4

I had at least hoped for FastStream. (Essentially bidirectional SBC for good quality audio while using the microphone)

At least this prevents impersonation of well-known publishers or their software. Maybe all changes to metadata like the description should require a manual review even for established packages.

So ein privates Flugtaxi wäre ja auch ein toller Dienstwagen. Kein Stau mehr. (/s oder doch nicht?)

There is an actively maintained project for github: https://github.com/josegonzalez/python-github-backup

Here are some interesting lists of alternative instances:

https://jitsi.github.io/handbook/docs/community/community-instances/
https://ladatano.partidopirata.com.ar/jitsimeter/
https://timo-osterkamp.eu/random-redirect.html

By the way, by default jitsi is not end-to-end encrypted if you have more than two people in the call or need to use the videobrige for other reasons. https://jitsi.org/e2ee-in-jitsi/

Update: The e2ee implementation seems to have some issues as well: https://eprint.iacr.org/2023/1118

Firefox <116 is currently not able to use the e2e-encryption, blink based browser already support it. Firefox 117 will provide the necessary infrastructure as well. I don't know if jitsi would have ot be patched to detect the firefox implementation. https://bugzilla.mozilla.org/show_bug.cgi?id=1631263#c58