![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://lemmy.world/pictrs/image/8286e071-7449-4413-a084-1eb5242e2cf4.png)
IPv6 binds on wildcard addresses include binding to the IPv4 addresses.
IPv6 binds on wildcard addresses include binding to the IPv4 addresses.
What does ss -tlnp
return? Does the process listen on any ports?
That should only affect ports below 1024.
Your two bind addresses might be in conflict with each other since [::]:5234
includes binding to the first one.
Python packaging and stability is a total mess. It has gotten to the point where I just look for alternative tools when I find out something new I found is written in Python.
You want https://tabby.tabbyml.com/ instead of tabby.ml
ist das glaube ich recht klar, dass öffentlicher Nahverkehr 'ne ziemlich zukunftssichere Technologie für die urbanen Regionen von Heute und der nächsten 10 - 20 Jahren sein wird.
Aber, aber, was wenn der Vladimir da auf alle Städte Atombomben wirft, dann ist doch da die Bevölkerungsdichte für Nahverkehr überhaupt nicht mehr geeignet. /s
the info required was there already, just you needed to put effort in
Not really. This is mostly what this is all about. The companies are insisting that open source projects should do analysis of security impacts in addition to fixing the bugs whenever some “security researcher” runs some low effort fuzzing or static analysis thing that produces large numbers of bug reports and assigns CVEs to them without the consent of the project. The problem is that such an impact analysis is significant effort (often orders of magnitude more than the fix itself) by people with deep knowledge about the code bases and only really useful to the customers of those companies who want to selectively update instead of just applying all the latest fixes.
Ich habe das mal so ausgelegt dass z.B. der Sohn das Bild von der Klassenkameradin auf dem Handy hatte und es darum ging das an die Eltern der im Bild dargestellten weiterzuleiten.
While true essentially forking the latest stable version of the kernel to make an LTS branch or a vendor version only multiplies the problem, it also does not contribute to solving it.
Haven’t used it myself but you could give https://rustdesk.com/ a try.
The worst thing is when it happens in this way and you can’t remember even though it was your own question https://xkcd.com/979/
Yeah, but when was the last time you decided to upload hardware device data for a root server to some hardware survey? That is something almost exclusively done by the kind of people who want to show off their system in some way.
I wonder how representative that is of actual software used. I would imagine hardware probes are run from installers and live systems quite frequently. I would certainly not expect several percentage points of “neither” in practical settings.
that even the thousands of developers who wrote most of that code don’t understand how their own code works anymore?
The bugs I have fixed that were written by that idiot “me from a few weeks/months/years ago”…
Any of those 2,034 people can push malware to Fedora
Maybe, but that is still a significantly higher bar than allowing everyone to publish a package the way most language specific package repositories work (or just use any random github repo even like some others).
auch wenn 300k (+CSU Wurmfortsatz) immer noch mehr als 125k sind).
Ich denke wenn man das mit Restlebenserwartung gewichtet sind die 125k wahrscheinlich deutlich mehr.
“you’re using it wrong” seems more like the official motto of Wayland whenever anything that isn’t working on it is brought up.
There are so many people who think sid is a distro when really, as far as the Debian project is concerned, it is a staging ground.
Ich würde es als Teilleistung bezeichnen da ja von Seiten der Praxis Räume und Personen bereit waren zu behandeln.