

Do we know what the real embargo date was supposed to be? Like was the upload off by hours, days, weeks?


Do we know what the real embargo date was supposed to be? Like was the upload off by hours, days, weeks?


Ja, ohne das technische Wissen oder jemandem im Bekanntenkreis, der helfen kann, ist das dann halt so.
Manche interessieren sich auch schlicht nicht dafür, selbst wenn es denen erklärt wird. Andere kriegen Panik in den Augen wie das legal sein kann.
Ich hab einfach keinen Fernseher. Zum einen weil keinen Bedarf, aber auch weil es quasi nur noch “smarte” TVs gibt.


Eine weitere Möglichkeit ist das Internet an Router für das TV komplett zu sperren. Dann richtet man einen weiteren, netzinternen Router ein (Opensense, OpenWrt, …), der ins Internet darf. Den Fernseher bekommt dann den als Gateway (default route).
So kann man den verkehr für den Fernseher komplett steuern und kontrollieren.Erfordert halt etwas Aufwand und Know-how, aber das ist auch lernbar, wenn man sich etwas damit befasst.


Natürlich geht das. Braucht genau zwei Regeln in der Firewall: erlaube DNS abfragen an externe Server durch pihole, und verbiete alle anderen externe DNS Anfragen.


Or another TV of the same manufacturer that has Internet access.


Doesn’t always help. There was a controversy a few years back that some TVs that are not connected to the Internet will use other TVs of the same manufacturer they find in WiFi range as a relay to offload their telemetry to the manufacturer anyway. I can’t remember how or if that was ever resolved. Or if it’s even illegal (anywhere).


Also sick of hearing about it. Not because I want to play it, but because I don’t care about it, at all.
Congratulations, you added to that kind of noise. For no reason, too.


While it’s nice to use a bit less sand, charring at 350°C doesn’t sound like negligible energy usage. Especially if done with fossils. Always good to have options, I guess?


Stable vs Unstable does not mean anything to do with bugginess or prone to breakage
It would be great if that’s how the words were actually used, but in most discussions I’ve seen it is certainly not the case. Also, when talking to new users, they are supposed to magically understand and know the word is used in a niche way in this context? It certainly won’t be what they take from it when hearing or reading it.
Unstable means packages update frequently including major versions
That’s what we have rolling or bleeding edge for. Sure, unstable can mean that when used within the same project/context. So having different releases be stable and unstable for the same thing, but across projects/distros that’s just confusing, especially for new people. Yes I’m aware of the historic reasons and the roots in software development, but I’d argue it isn’t helpful to convey the practical reality of the differences.


I didn’t claim anything is bad, anywhere.
Also I didn’t “try to use Debian in a way it wasn’t inteded to be used”. I am using debian on 90% of my servers/vms/containers to this day. Have been for literally decades. To give a specific example: I was running a nextcloud, which required PHP, and wanted to update that. The newer version reuqired a higher PHP version, because the currently installed PHP version was EoL and not supported anymore (by PHP maintainers or Nextcloud). So updating required removing the debian-provided PHP version and installing one from other sources (external repo or compile from source), which honestly defeats the point of a “stable” distribution if the software provided is EoL, doesn’t it?
And to be clear this is just one example I can specifically remember. The “issues” I encouter when using debian are usually of that general type. And to be clear, that’s mostly the point of using it on a server, where I use it, but even there it sometimes goes a bit too far.
And finally: I was originally arguing the semantics of calling debian stable and arch UNstable, which it is not. It is rolling, it might be bleeding edge. It’s also isn’t the same as having a stable and unstable release branch (within the same distro) when applying the label to the most stable release of different distros.


I didn’t say “it suddenly breaks”. I said I have more issues with it, which is decided different from “it just works”, which has been my experience on CachyOS. Specifically I mean issues with installing (up to date) software, or using software that has requirements that I just can’t install the required version cause the repo has a version from 3+ years ago. Not everything has to be “bleeding edge”, but being so stable that everything is utterly outdated is also a kind of unstable.
Sometimes this goes so far that the “stable” version shipped by debian is already unsupported upstream with all the security implications that entails (I had that once with PHP, I think).

In large parts of the world (at least most of Europe) live and neutral aren’t distinguished. There is no coding or assignment on the outlet. Maybe that’s where their experience came from?
Functionally it should be irrelevant.
… in what?


Telling YouTube that you’re “not interested” does work, but it’s somewhat tedious. If that’s worth the effort to you depends on how you use YouTube, basically.


Thank you. Yes, it was indeed a genuine question.


Compare the other extreme Debian, which is very stable.
In the sense that is unchanging, sure. But that’s one hell of a bad word to describe that in this context. In my experience the incompatibilities caused by only ancient versions of things available in the repo of even a newly released Debian are not helpful. Stable wouldn’t be the word I choose to describe the situation, or the fiddling and tinkering that results from that. Often having to go outside of the repo to solve, defeating the whole point of said repo.
Arch in my limited experience is much more stable, in the sense of “just works” and always having up to date software. If I want to use something, I can just install it (from the repo), the chance of it not being the current release are slim.
Similar to NetGuard there is Tracker Control. It also uses the VPN “slot” but it can additionally run a wireguard tunnel itself now. So you can combine access control, adblocking on DNS level and actual vpn.
Edit: added link


I have no idea what people keep talking about when they say Arch/CachyOS is “unstable”. I have had so many more issues with running Debian (usually on servers) over the years. Since I swapped my desktop to CachyOS over a year ago, I have basically no issues at all. Just one very minor thing that fixed itself after a few days (bug in kde on new version released). For like 15 months of use, that’s spectacular compared to any other system I’ve ever used (especially including Debian and of course Windows, obviously).
What exactly is the goal? How do you make “no issues” and “it just works” more stable?


My go-to is LocalSend for this, but sure, why not.
The Carbin in the woods (2012)