cassidy

cassidy, 1 day ago

@gloopsies I can’t speak officially for the whole of GNOME, but my understanding is that the design and release teams are investigating this. I don’t think there’s a decision yet, as different solutions all have different trade-offs—but yeah, we’re working on it. :)

cassidy, 1 day ago

@aylamz we're actively working on completely revamping notifications; it's a long road because all of the different notification APIs on Linux are messy—but we're gonna wrangle it. :) https://blogs.gnome.org/shell-dev/2024/04/23/notifications-46-and-beyond/

cassidy, 2 days ago

@SpaghetMeNot this is SO PRETTY

cassidy, 2 days ago

@9to5google I really hope it’s just those screen-takeover ones and not the adorable little animated emoji. The animated emoji seem subtle, self-contained, and harmless but I don't need like three arms randomly popping out of a message because I acknowledged it with a 👍

cassidy, 3 days ago

@berkough I would be happy for someone to actually take the idea and make something decent from it. But I discontinued it because it didn’t really work well in a Flatpak world plus it was way over my head for responsible maintenance.

I didn’t even know it was being packaged by Fedora, let alone just there in the app store in Fedora 40.

cassidy, 3 days ago

@berkough nothing about the app listing lets you know it is unmaintained. To the contrary, it shows as a “Safe” app developed by me, provided by Fedora. It contains my app description that I wrote for it on elementary OS. You have to click into the detailed version history to even see how long ago it was last updated (3 years ago!).

cassidy, 3 days ago

@BrodieOnLinux @berkough GNOME upstream is much more nuanced, but yeah, I am starting to think we should not have a “safe” badge at all if stuff that is safe gets downgraded for reasonable permissions while a three-years-outdated unmaintained web browser packaged against its developer's wishes that crashes in launch is considered “safe.”

cassidy, 3 days ago

@BrodieOnLinux @berkough right which is why part of the equation is developer verification, human review of app submissions and permission changes, and a more nuanced safety rating that takes into account network access—all the case with Flathub + GNOME.

Buuuut even then it seems like it would be easier not to promise safety, but to warn on more critical potential issues.

cassidy, 3 days ago

@makendo dnf. It was never packaged as a Flatpak.

cassidy, 3 days ago

@adamw I'm just shocked that it's been sitting there in Fedora, with my name on it, unmaintained three years after I stopped updating it and two years after I explicitly marked it as EOL. And there's no easy way to tell that from Software on Workstation. 😬

I shouldn't have to create a bugzilla account and comment on a random issue to make it clear that it is entirely abandonware and irresponsible to ship to users.

cassidy, 2 days ago

@carlwgeorge @adamw thanks! I'll do that. I'm still just surprised by the situation considering it was clearly abandoned & archived.

To turn this into a positive thread/suggestions, maybe:

• Package building scripts should check if the source repo is archived, and not build it and/or amend the appstream to mark it as EOL
• GNOME Software could better expose when a package is that outdated
• Fedora should amend the appstream when an app is unsupported by the developer, like you see on Flathub

cassidy, 2 days ago

@carlwgeorge @adamw I wouldn’t have even known where to have this discussion on an issue tracker—I stopped updating it over three years ago and archived it two years ago. I think the issue stems from the fact that the app was packaged and “maintained” against the wishes of the upstream by someone clearly not doing the maintenance work. For something as critical as a web browser, that just seems flawed out of the gate.

cassidy, 2 days ago

@carlwgeorge @adamw If none of the above would have helped, then Fedora’s packaging policies should be revisited. Because this should not be an acceptable outcome.

It’s tiring to be told, “hey you should go out of your way to come into our community and co-maintain your app that you don’t want to maintain for this platform/packaging format/etc.” but that’s exactly what happens when distros, Snap, etc. package my stuff. The burden falls on me to support it when I never intended to.

cassidy, 2 days ago

@carlwgeorge @adamw I only happened to realize this because I was testing something on Fedora Workstation 40 and saw it when searching for a different app of mine. Otherwise I’d have never known it was shipping to people, in Software, under my name, with no indication of it being unsupported/outdated.

cassidy, 2 days ago

@carlwgeorge @adamw I mean, I went to social media to vent because I was surprised and didn't even know where to start. I was given an email address, so I've sent an email to it if you want to move this to a mailing list instead.

That said, I don't really have anything else to add. I'm not interested in being told how to Google things or how to use social media.

cassidy, 2 days ago

@bashfulrobot I would love to bring some its ideas to GNOME Web or maintain a minimal Flatpak version or something in the future, but I just don have the time. I think @isantop had something similar in the works??

cassidy, 2 days ago

@alatiera ha, now I want to get it running just for giggles. I recall I did a tiny bit of work to make it look better (basically so it could be used on Pop!_OS by a friend), but yeah… I was not actively testing that.

cassidy, 2 days ago

@carlwgeorge @adamw dude, I posted a two sentence post at 11 PM while dicking around with the new Fedora 40 on my couch before going to bed.

I am not in the Fedora community. I don’t know (or really care) how package maintenance works in Fedora. I did not suddenly feel the need to investigate the ins and outs of the Fedora project before sharing my shocking (to me) discovery.

cassidy, 2 days ago

@carlwgeorge @adamw And then I wake up to replies from several Fedora folks that all I had to do was follow this specific Fedora process documented on Bugzilla, I’m “attacking” the maintainers, my “excuse” is “weak,” me communicating my wishes is “not fair,” my communication is not “appropriate,” I should have used an issue tracker or scoured the wiki to understand who to email…

I’ve shared my thoughts and wishes. It sounds like it’s being taken care of. I don’t need a lecture, too.

cassidy, 2 days ago

Classic Mastodon @-reply/threading confusion, sorry!

I was not referring to you specifically @adamw; you’ve been very helpful. Thank you!

I’ve received replies from others (including I think maybe the package maintainer?) and @carlwgeorge that included what I quoted there. I was replying directly to Carl’s post.

cassidy, 3 days ago

@cameronbosch @flathub possibly a sort of unintentional self-DDoS. 😅 Developers smarter than me could probably explain it better, but I think the new homepage’s significantly increased API calls plus a ton more traffic than usual (plus maybe the API caching not working correctly?) brought things down. But they’re working on fixing it up so we can bring it back.

cassidy, 2 days ago

@heydon …maybe