• 3 Posts
  • 29 Comments
Joined 11 months ago
cake
Cake day: August 31st, 2023

help-circle

  • well, the point of flatpak is to have bundled dependencies so they run predictably no matter the distro

    if one of your software’s dependency gets updated, and your software isn’t, you may run into issues - like a function from the library you’re using getting removed, or its behaviour changing slightly. and some distros may also apply patches to some of their library that breaks stuff too!
    often, with complex libraries, even when you check the version number, you may have behavioural differences between distros depending on the compile flags used (i.e. some features being disabled, etc.)
    so, while in theory portable builds work, for them to be practical, they most often are statically linked (all the dependencies get built into the executable - no relying on system libraries). and that comes with a huge size penalty, even when compared to flatpaks, as those do have some shared dependencies between flatpaks! you can for example request to depend on a specific version of the freedesktop SDK, which will provide you with a bunch of standard linux tools, and that’ll only get installed once for every package you have that uses it









  • There are tons of ActivityPub implementations out there already

    but none are widely used by such a massive amount of people as threads, and especially people who don’t understand/care about spec compliance or even how federation works

    honestly, i think in the best scenario, threads will create their own activitypub “fork”, and most instances won’t want to follow it, forcing the people who were on non-threads instances to chose between going to threads to keep in touch with their threads mutuals, or staying on non-threads instances and no longer having a reliable way of keeping in touch with those people.

    worst case would be instances following what meta does and making them the spec dictators pretty much, the spec would become closed source and all other fedi implementations would lag behind in features compared to threads, and they can at any point change the spec and break other instances.

    i think the point of defederating with threads isn’t just the defederation, but is about sending a message that we don’t want to play their game, we want to keep doing our things our ways. if they want to interract with the fediverse, they’ll have to play by our rules, we don’t want to follow theirs




  • as much as i agree,

    1. accessibility is usually pretty horrendous on most matrix clients, none i could find have full, proper reduced motion support, which i need to properly use pretty much any piece of software. discord is far from perfect in this regard, and getting worse and worse, but still miles ahead of most chat apps i’ve tried, especially proprietary ones. I have barely used revolt, and in my memory it’s far worse than discord, and i have yet to figure out how xmpp works…
    2. none of my friends are on it. while i could convince some to move, here discord is already a quite “niche” chat service, and as a student, i’m more or less required to be on any chat service whatever group project i need to do is organised. same with friend groups, i’m usually not a “group leader”, and join in friend groups that already exist, so it’s much harder to insist on moving anyone over to a new thing no one but me has ever used before
    3. ux isn’t great. it’s improving, but i’ve had quite a few “key exchange” issues with matrix especially… Also, i found most clients quite messy, but that’s more to personal taste!







  • ^_^

    i know i’ve wanted something like this for a while. i really didn’t want to have to figure out how to get the existing keyman keyboard layout to work on linux, because fcitx works fine for all my other input needs, and i already knew how fcitx worked as i made an addon to get on-screen keyboards to work with it a while back…

    as i know not many people would dare venture in the world of fcitx addons, due to the quite horrendous state the documentation is in… so if i wasn’t gonna do it, likely no-one else was, so i did it! and shared it with everyone, because the worse that could happen is that someone helps me make it better!