Posts by jf@hachyderm.io
 (DIR) Post #AT5eCLxSWJrq3iRmDI by jf@hachyderm.io
       2023-02-27T01:57:37Z
       
       0 likes, 0 repeats
       
       @codewiz @dropbear42 @globalc That was never "killed" it was always trivial to add it back with extensions, many distributions did that. However this has arguably caused worse problems because every API for it has been pretty flawed and caused broken behavior in apps. So I don't think it was premature, it likely should have been removed sooner.The background apps API is the only one that actually works correctly but it took this long just to design it.
       
 (DIR) Post #AT5iS6Kuliha3jBP04 by jf@hachyderm.io
       2023-02-27T02:15:15Z
       
       0 likes, 0 repeats
       
       @dropbear42 Yes, that is why I refer to distributions, e.g. this was supported by Ubuntu and a few others so they would keep the extension working whenever they did a release with a new GNOME version. So you could be reasonably sure an Ubuntu extension would work elsewhere.But even so, this was still trivial to keep working, I don't think the shell extension API for indicators has actually changed at all since the first release of GNOME 3 despite being considered "unstable"
       
 (DIR) Post #AT5mk5b4ejI8nMZfDE by jf@hachyderm.io
       2023-02-27T03:33:19Z
       
       0 likes, 0 repeats
       
       @codewiz I think I am understating just how broken the old APIs were. They are unworkable. Like they are so busted that there is no way to transition them without breaking them further. They just don't work. This was all written up here a few years ago: https://blog.tingping.se/2019/09/07/how-to-design-a-modern-status-icon.htmlSure it would have been great to have the design of the background apps API twenty years ago! But it took lots of years of experience to just get to this point where it could be designed.
       
 (DIR) Post #AT61lA315nQECVc58y by jf@hachyderm.io
       2023-02-27T03:37:41Z
       
       0 likes, 0 repeats
       
       @codewiz And BTW this is what I was getting at. One of the reasons why it was important to just remove it early was to *avoid* this situation where some unworkable API gets dumped into someone's lap who didn't ask for it, and they are stuck trying to figure out how to transition away from it forever.Pipewire is an interesting example because there are actually many broken edge cases with Pulse compat that likely won't ever be implemented, you can see them if you check the Pipewire bug tracker.
       
 (DIR) Post #AT68UfiUnI11B16D2G by jf@hachyderm.io
       2023-02-27T07:37:04Z
       
       0 likes, 0 repeats
       
       @codewiz Well, the app indicators were always an optional thing on Linux, e.g. in KDE or GNOME 2 or whatever you could just delete the indicator widget from the panel. So apps needed to support a fallback for this anyway, if someone's workflow was disrupted then the app was buggy from the start.
       
 (DIR) Post #AT6AcotQlBtprUE83M by jf@hachyderm.io
       2023-02-27T08:00:43Z
       
       0 likes, 0 repeats
       
       @codewiz The backgrounding API has been around for a few years. It is a pretty simple API, it depends on a concept of a running app so it needs Flatpak or some other sandbox to work correctly. https://flatpak.github.io/xdg-desktop-portal/#gdbus-org.freedesktop.portal.BackgroundFor Rust apps, ashpd already has a binding too: https://docs.rs/ashpd/latest/ashpd/desktop/background/index.htmlThere is no need for the apps or portal to interact with systemd, Flatpak will automatically spawn systemd scopes for any Flatpak app.
       
 (DIR) Post #ATWK4X851m8MnhaFWK by jf@hachyderm.io
       2023-03-11T15:40:51Z
       
       1 likes, 0 repeats
       
       @web3isgreat Another one for the "code is law" and "not your keys not your coins" greatest hits albums
       
 (DIR) Post #ATWKR1G5gkpecE3KXg by jf@hachyderm.io
       2023-03-11T22:52:22Z
       
       0 likes, 0 repeats
       
       @seldo I was severely addicted to espresso and had to quit years ago... Went cold turkey, suffered through a week or two of severe and debilitating withdrawal and now I never wanna have caffeine at all. Not even a snickers bar. Probably one of the better dietary decisions I made but not for everyone 😶
       
 (DIR) Post #ATaeGDXgS8rTF8FRRY by jf@hachyderm.io
       2023-03-14T00:53:18Z
       
       0 likes, 0 repeats
       
       @mjg59 Living the dream!
       
 (DIR) Post #AUULKK5ZD9w1yqxCi0 by jf@hachyderm.io
       2023-04-09T21:45:46Z
       
       0 likes, 0 repeats
       
       @BrodieOnLinux I hate to be this person, but IMO after seeing where that discussion fizzled, there is no solution. This is a self inflicted problem in open source, it is simply not possible to have apps that are fully customizable and also look perfect 100% of the time.Again just my opinion, it seems KDE will circle the drain for a while before theme authors get mad, and then they will have to make some tough decisions. Same thing that happened to GNOME...
       
 (DIR) Post #AV5Q5QwkFjPATXYF9s by jf@hachyderm.io
       2023-04-27T19:03:32Z
       
       0 likes, 0 repeats
       
       @tante If anything, Mastodon is another indicator to me that the FLOSS model of "sovereignty" is just more hyperindividualistic nonsense. Nobody cares about that except nerds who enjoy playing with servers for fun. I've been that person, and while it can be fun, I can admit that particular personal quality doesn't necessarily make a person suited to running a social network. Musk is just the most extreme example who can't admit it...
       
 (DIR) Post #AWJR1BYMIVU5FDHbeK by jf@hachyderm.io
       2023-06-02T16:10:07Z
       
       0 likes, 0 repeats
       
       @codemonkeymike The recommended workflow in GNOME is to not use tray icons, instead put telegram on another desktop, and switch to it when you need it. IMO tray icons are a very bad UI, they are obsolete on any DE once you have the ability to do virtual desktops properly, or even if you just have a taskbar/dock that can shrink the icons like in Plasma.
       
 (DIR) Post #AWJR1CtfIm7bPaG8Uy by jf@hachyderm.io
       2023-06-02T16:23:06Z
       
       0 likes, 0 repeats
       
       @topher Sorry, this comment makes no sense to me whatsoever. I think you are talking about something else. All those situations are handled by notifications, not tray icons.Even in the screenshot above it just shows a "Z" icon with no additional information about what is actually happening. The actual info of the chat messages (e.g. "Alice says 'hello'" or "6 updates are available") is in  notifications. Tray icons are just an icon with no particular meaning.
       
 (DIR) Post #AWJR1DiiEyxFxu8u48 by jf@hachyderm.io
       2023-06-02T16:25:37Z
       
       0 likes, 0 repeats
       
       @topher And for load averages you are better with an extension that shows a real widget or just have something that sends you notifications. Tray icons are too small to convey any useful information there, you can't even mark a graph or show any text.For CPU overheating that is an extremely bad solution. You need to setup sensor watches or fix your PC fans, because if you are away from the computer when that happens or you don't happen to notice the tiny icon, then your CPU will just melt.
       
 (DIR) Post #AWJR1GyQ92Io3UVzSy by jf@hachyderm.io
       2023-06-02T16:30:26Z
       
       0 likes, 0 repeats
       
       @topher Like even then, you probably want something like this that will actually show you the exact temperatures or allow you to show more than one thing https://extensions.gnome.org/extension/841/freon/