Posts by matk@mastodon.social
 (DIR) Post #Ad1hgR3mLa0A5Kc5jM by matk@mastodon.social
       2023-12-21T06:58:37Z
       
       0 likes, 0 repeats
       
       @BrodieOnLinux That's simply to avoid inconsistency - if it's called i386 literally *everywhere*, diverging in one place would be odd for people who know what it means and doesn't matter for people who don't. In the actual super end-user-facing places like https://www.debian.org/distrib/index.en.html we simply call it "32-bit PC" (which I like a lot more, because for non-technical users "i386" means nothing, but they will likely know that they have a 32-bit computer)
       
 (DIR) Post #AhUs6WXWaSgu37qgOO by matk@mastodon.social
       2024-05-02T11:28:03Z
       
       0 likes, 1 repeats
       
       I wonder: If a project deliberately unilaterally abandons a #Freedesktop  specification, would it be reasonable to ignore their voice in subsequent change discussions to that particular specification, for changes that other projects want to make to it?After all, by breaking the convention, there apparently is no longer any interest in collaboration and cross-desktop integration anyway...It would suck though, it would make the Linux desktop poorer, inconsistent and app dev's lives harder.
       
 (DIR) Post #AhpvIiDHfWkwvNToDg by matk@mastodon.social
       2024-05-13T03:55:01Z
       
       0 likes, 0 repeats
       
       @BrodieOnLinux The Debian maintainer decided to reduce the amount of plugins shipped by default (for which upstream already provides flags, so this is a to-be-expected configuration) to improve security of this piece of software. After some discussion, a "-full" variant is also provided for users who need all features.So, both the security-pedantic minimalists and the ones who want all features are happy, I don't see the issue here...https://packages.debian.org/sid/keepassxc-full
       
 (DIR) Post #AhpwLe77T00J27YjYm by matk@mastodon.social
       2024-05-13T04:06:56Z
       
       0 likes, 0 repeats
       
       @BrodieOnLinux Given that a user reported this first, it apparently wasn't discussed with upstream, so I do agree with that part. Packagers and their upstreams - also in Debian - usually have a fairly tight relationship (of course, including disagreements, but *a lot* of communication generally happens).That said, individualism is high in Debian and every packager can handle things how they see fir, sometimes for better, sometimes for worse, sadly.
       
 (DIR) Post #AhpwrAuzYCvhkdv9Zw by matk@mastodon.social
       2024-05-13T04:10:23Z
       
       0 likes, 0 repeats
       
       @BrodieOnLinux This is pretty much one fallout of the XZorcism incident, with security-sensitive distros trying to reduce attack surfaces as much as possible... sometimes going a bit overboard.If these plugins could be compiled as dynamically-loaded libraries, they could be packages separately people could pick their minimal set, but KeepassXC doesn't seem to be built that way.In any case, communication for sure was really bad here.
       
 (DIR) Post #Ahpx5GCYhiheBvr0fA by matk@mastodon.social
       2024-05-13T04:14:56Z
       
       0 likes, 0 repeats
       
       @BrodieOnLinux Yeah... Knowing Julian, that was an exceptionally harsh reply of him, and could have been way more diplomatic. But he does care a lot about security, and people are a bit on edge right now (understandably...).Sometimes when everyone is overworked, stuff like this happens, I hope it gets resolved amicably, as this is a fairly silly thing to fight over.
       
 (DIR) Post #AhpxQIq0694CRsKvBI by matk@mastodon.social
       2024-05-13T04:17:59Z
       
       0 likes, 0 repeats
       
       @BrodieOnLinux Toggles mean that users may accidentally flip things on that they don't need, or that malware is one config switch away to enable exploitable code and read all passwords ;-)Granted though, I assume a tool like KeepassXC is probably audited fairly well and there's likely higher-quality plugins that could always be there.
       
 (DIR) Post #Ahpy9OOiH0Zciv4bpY by matk@mastodon.social
       2024-05-13T04:27:03Z
       
       0 likes, 0 repeats
       
       @BrodieOnLinux Playing devil's advocate here: If they are core pieces of functionality, why can they be disabled by compile flags at all?
       
 (DIR) Post #AhqRRdvWAkvIllTLEW by matk@mastodon.social
       2024-05-13T09:55:24Z
       
       0 likes, 0 repeats
       
       @BrodieOnLinux So, the Debian maintainer reduced the default attack surface as per prior upstream discussions then, right? ;-)Maybe it's time to revise that and default-enable audited code without flag to disable it...But I'm in the peanut gallery here, that's really up to the maintainer(s) to decide!
       
 (DIR) Post #AhqVrtdMnNsopXkwgi by matk@mastodon.social
       2024-05-13T10:44:25Z
       
       0 likes, 0 repeats
       
       @BrodieOnLinux Yes, but providing options and then complaining if someone uses them is a bit odd... If you provide the knobs, you can expect someone to turn them, so if you don't want that, don't provide the options (or gate them behind a clear "use this at your own risk, using these options will result in an unsupported configuration" warning).E.g. you can build AppStream without systemd, but it's not recommended, and an error is thrown if a function is run that relies on systemd features.
       
 (DIR) Post #AhqxsOGvgIPEZMHkaO by matk@mastodon.social
       2024-05-13T15:57:47Z
       
       0 likes, 0 repeats
       
       @BrodieOnLinux TBH, my personal opinion is that xscreensaver was pretty silly.However, users should include the software version number in bug reports when they go upstream, always. And for distros, ideally bugs should end up in the distro bugtracker first and then be sent upstream by the package maintainer.That said, by introducing AppStream, I am probably directing more people to the upstream bugtracker...And also, for new users, Debian's bugtracker is particulary user-unfriendly too...
       
 (DIR) Post #Ahrn5q4SjRtcDGckfg by matk@mastodon.social
       2024-05-14T01:31:58Z
       
       0 likes, 0 repeats
       
       @BrodieOnLinux If people report bugs at all it's already a miracle...The lowest possible bar would likely be to at least make the Debian bugtracker more user friendly (e.g. with a non-email interface), but I doubt that will happen anytime soon.On the AppStream side, I should maybe add a global bug report URL override option, or the package maintainer should just patch it if the packaging delta is too large. That'd require everyone to play nice...
       
 (DIR) Post #Ahrp26D6z32V1E0wIy by matk@mastodon.social
       2024-05-14T01:54:16Z
       
       0 likes, 0 repeats
       
       @BrodieOnLinux The Debian bugtracker is controlled *exclusively* via mail. As developer, it's fine and I memorized all the commands and formatting I have to send, but for a drive-by bugreport by a non-technical average user it's pretty much impossible to file issues reliably (and then their e-mail address is public too, which they might not have wanted...).This won't change soon though, because of -ENOMANPOWER as well as debbugs having its hardcore fans for the way it is.
       
 (DIR) Post #Aie9XzPdo52ZUqhBSa by matk@mastodon.social
       2024-06-06T08:49:09Z
       
       0 likes, 0 repeats
       
       🎉
       
 (DIR) Post #Aie9Y0s2NzLi1CzNMO by matk@mastodon.social
       2024-06-06T08:58:44Z
       
       0 likes, 0 repeats
       
       https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/269
       
 (DIR) Post #AieDDjD6jgs7GtQYGu by matk@mastodon.social
       2024-06-06T10:11:35Z
       
       0 likes, 0 repeats
       
       @BrodieOnLinux It did! An unexpectedly long journey ^^
       
 (DIR) Post #AnHdtJ08LuHvIOSCuW by matk@mastodon.social
       2024-10-23T02:12:47Z
       
       0 likes, 0 repeats
       
       @BrodieOnLinux Foundational numerical linear algebra and numerical libraries are partially written in it, performant and tested code used in research for decades.It's also sometimes surprising for me to see all the random places where Fortran is used in science, but that stuff works, and fast. No need to change it 🙂
       
 (DIR) Post #AxHc2wxvm9qTxdTdzs by matk@mastodon.social
       2025-08-18T04:33:06Z
       
       0 likes, 0 repeats
       
       @BrodieOnLinux Do you mean https://stoppromotingwayland.netlify.app/ ? Stuff like that annoys me greatly, because there *are* some great points that just aren't engaged with honestly or in a balanced way. So all it does is make people defensive.And it actively makes my work on Wayland extensions a lot harder...For example, ext-zones is needed for *some* enterprise apps, but claiming that *all* enterprise apps need it and that it prevents enterprise Linux is simply disingenuous.
       
 (DIR) Post #AxHkWg51v3u1ucU3sm by matk@mastodon.social
       2025-08-18T06:08:05Z
       
       0 likes, 0 repeats
       
       @BrodieOnLinux That guess probably isn't wrong - but if it's the app you rely on and want/need to use, or if you are the developer of such an app, or if you are working on cross-platform apps, then even though it's just a minority app it can break the Wayland experience for you.Same for the window icon stuff - it can be very obnoxious in Python venv's to not have it, and some enterprise stuff may rely on it: https://issues.redhat.com/browse/RHEL-24713
       
 (DIR) Post #AyyzUCZtUDmMOCTFYm by matk@mastodon.social
       2025-10-06T19:22:05Z
       
       0 likes, 0 repeats
       
       @deobald @thelinuxEXP How would you organize it so that committee discussions don't become a public "show", damaging the accused even more, or dragging anyone who was abused into the spotlight where they don't belong and don't want to be?