@ebassi Moving from Perl to python was unforgivable sin. I never thought of it this way but now it explains why I could never digest gtk-doc after ~2010ish.
Also I haven't met yet a distro without perl. Except docker. And maybe alpine. which is all the same, not a distro really. But plenty of distros without python. Call it a luck.
@gnome so... you're going to deprecate gkr, right?
@PINE64 Don't want to spoil your feast but can someone look at RMA case 8035? Even simple response like "sorry but we'll never send it back to you" would suffice. Thank you.
@mntmn why one needs to remove batteries first? Aren't they individually controlled?
@mntmn that reminds me my early works with opengl library in university :)
@lunduke agree, appeared after irc and xmpp and other federated systems but learned nothing from them and is stupid by design.
@mntmn good like "not-evil" (eg unlike others) or good like, well, not bad
@kyle @purism I would rather disagree here. I as a corp CISO just apply zero-trust model and ring-fence corp data at all perimeters, starting from user-end-point and ending internet/service perimeter. I, as a parent, want to protect my kid from dangers of the digital wilds. Now this is for convenience (I'm not a watch dog, i teach my kids but I know they are not ready yet. Kids develop themselves differently).
@purism @kyle and then there's UEM/EMM/MDM - but you still have a choice - if you don't want the corp to control your device (with your consent - which is important) just don't access corp resources from your device. simple.
My point is - corp control of corp owned endpoints has nothing to do with the mess google and apple are throwing upon us. they may use similar tech, but that's about it.
@purism
"The most common justification for these policies is convenience."
stopped reading.
@kyle with all due respect I know you can do better than that. Parental control is about controlling *your* device from your kids (when they buy their own you lose that control). Corp policies are about controlling *corp* devices. When you go all byod you apply NAC and security posture control as you cannot change device you don't *own*.
@kyle something is wrong with you :) I'm wearing my pebble for about the same time but I only check them when a) i need to check time b) it vibrates so i _may want_ (not *must*) to check what's there c) I want to use some of the apps (calendar, compass, weather) d) whether bluetooth is connected (eg do I have a phone with me or forgot it somewhere)
@fnord @kyle It's about ToS. In corp network you have your standards and even the fact of being non-compliant with standards is ToS violation. ISP may cut your subscriber's line if you violate ToS (eg detected malicious activity/abuse) but not proactively because they suspect you may do it due to using unpatched devices.
@dos no, just debian is not up to being rolling, try arch and stay calm while still rolling. any time I try to use deb or rpm based system I'm becoming pissed with the [way] upgrades [are done]. and switch to either gentoo or arch.
@agx @x51@cybre.space I did, but in here [1] it's just a static boolean property, not sure what is supposed to track it.
1 - https://gitlab.gnome.org/GNOME/gtk/-/blob/master/gtk/gtkapplication.c#L1206
@agx @x51@cybre.space The reason being - system-activeness will likely be used by system services (non-toolkit apps) and top-of-the-stack while is a shell concept may still be wrapped into toolkit.
@agx @x51@cybre.space I would expect it rather opposite :) the screensaver (system-active) to be on a well-known dbus path and top-of-the-stack (app-active) to be toolkit-specific.