It was an example. I don't have a fucking clue how all the maintainers are named.
The main question was: why can a maintainer NACK something not in their responsibility? Isn't it simply necessary to find one maintainer who is fine with it and pulls it in?
Or even asked differently: shouldn't you need to find someone who ACKs it rather than caring about who NACKs it?
Can a maintainer really NACK any patch they dislike? I mean I get that Hellwig said he won't merge it. Fine. What if for example Kroah-Hartman says "whatever, I like it" and merges it nonetheless in his tree?
Damn, so that was the issue. I spent 2h trying around with different packages I suspected to cause an error during start. Then I desperately moved my .config dir out of the way to rule out an incompatible config and lo and behold... it worked. I then moved it back and tried to delete configs more finegranular. After a few iterations without success I just removed almost all kde and plasma related configs and reconfigured everything from scratch. I should have scrolled through my feed earlier 😁
The second one gives you the necessary flashbacks to catch up if you should intend to follow the story. It also explains all the basics of the game mechanics as part of the quests.
Maybe only using the pause timer would work. Once you start procrastinating, start the timer, allow yourself to do whatever but once the timer is done, back to work.
I even heard people being surprised it's not Geralt. When they were surprised I started to question myself if I just dreamed that they announced that wayyyy back.
Typically I get easily distracted or bored during movies. The only exception in recent years was Oppenheimer. It had such a fantastic pacing that the three hours rushed by and I didn't pick up my phone even once. It was incredible.
Or preferably: don't care about the game at all until it releases. Ignore previews or alpha demos, beta footage, gameplay trailers/teasers, etc. That way you don't build up hype that has a big chance to disappoint you. Take the game for what it is at release and either like it then or not.
Is that really a relevent attack vector in your day to day use, that full disk encryption wouldn't cover? My browser is rarely closed when I am on the PC, so it would be accessible (because unlocked).
What ZigBee Coordinator do you use? I know deconz and zigbee2mqtt have the ability to add support for new devices via config files. But that's a bit of a rabbit hole into the ZigBee protocol. They also have forums/issue trackers where one can request support for new devices.
Stalwart is 95% awesome. What holds me back is, that Mails are stored in a Database and not Maildir. Maildir is insanely trivial to backup incrementally and to restore individual mails if necessary. That currently holds me on dovecot.
But that's the neat thing: the system is well structured into different layers and subcomponents. They are not all involved to control lightbulbs; that's mostly your local hue bridge. One component will make sure, Alexa can control your bulbs (if you want that). If that component fails, only Alexa stops working. Another component handles push notifications to your mobile devices. If that fails, the rest is unimpacted. And so on.
That was, for a long time, the main reason I heavily recommended Hue: the bridge can be used completely offline and still offered a good local API and pairing system. Unfortunately last year that made online accounts a requirement. I assume besides the App you can still use many things even if your network connection is broken, though.
What's wrong with that? Do you expect their backend to run off a single server with a little PHP script? The components seem pretty reasonable (with the actual business logic being just a small part).
While I like and appreciate the campaign, the issue IMO is bigger. IoT devices for example even have environmental impact when services behind them get discontinued.
I would therefore like a more general rule: whenever a product is discontinued for whatever reason, all necessary documents, sources, etc need to be released to allow third parties to take over maintenance (that also includes schematics for hardware repairs).
It was an example. I don't have a fucking clue how all the maintainers are named.
The main question was: why can a maintainer NACK something not in their responsibility? Isn't it simply necessary to find one maintainer who is fine with it and pulls it in?
Or even asked differently: shouldn't you need to find someone who ACKs it rather than caring about who NACKs it?