Posts in category 'hacking'

  • Zen + Flatpak + KeePassXC

    I switched to using Zen via flatpak as my primary browser, and then remembered that getting a sandboxed browser working with a native KeePassXC is FUN. Then I found a workaround so I’m re-documenting it here with additional details that are required by my feeble brain.

    First off, a critical security caveat: These instructions bust open the flatpak sandbox by giving Zen (or Firefox–you can adapt these same instructions to work with any FF-based browser) the ability to run executables on the host system.

    Now, in my case, the alternative is running a native version of the browser via tarball or AppImage, so for me it’s six of one and a half dozen of the other. But you have been warned!

    Secondly, I should note these instructions are specifically for getting a flatpak version of Zen (or Firefox) working with a native KeePassXC installation. If your KeePassXC install is also a flatpak, you’re gonna have to look elsewhere (I tend to use native packages as much as possible and only fall back on Flatpak when I have no other option).

    With that disclaimer out of the way, here’s the instructions I lifted from this Github comment, but with a bit more exposition to make various assumptions in that comment explicit.

    Continue reading...
  • Taking Control of Chat

    Documenting my absurd journey to bridging an IRC client to a bunch of messaging services. Totally nuts and totally worth it.

    IRC, or Internet Relay Chat, is unquestionably the progenitor of modern online chat systems. IRC preceded instant messaging platforms like ICQ or AOL Instant Messenger, and in doing so connected people in real-time in a way that would lay the groundwork, not for just those instant messaging platforms that would follow, but for modern social media platforms as we know them today. And today, while certainly diminished, IRC still plays an important role in connected communities of people, particularly in the IT space.

    But IRC isn’t without its flaws, and those flaws created openings for many competitors:

    1. Chatting is ephemeral. If you’re not connected there’s no way to receive messages that were sent while you were away.
    2. Text-based. No images or giphy animations here, and file sharing is direct, client-to-client only.
    3. The mobile story in general, and notifications in particular, are weak.

    Now, the IRC community has worked hard to address the first problem with bouncers and changes to the IRC protocol (I’ll dig into this later).

    Issue two… well, bluntly, I actually view that as a benefit rather than a drawback, but obviously that’s a matter of personal taste.

    As for issue three, it’s still true that the mobile story isn’t great, though there is slow steady progress (Android now boasts a few pretty decent mobile IRC clients).

    But IRC also has some enormous benefits:

    1. It’s open and federated. Running a server yourself is trivial.
    2. Clients are heavily customizable for power users.
    3. It’s fast and lightweight.

    And these various other products (like Slack, Signal, etc) have some mirror image drawbacks:

    1. Closed walled gardens.
    2. Zero ability to customize.
    3. Heavy, memory- and CPU-intensive clients.

    And then there is the fragmentation. My god the fragmentation. Every app is its own beast, with its own UX quirks, performance issues, bugs, and so on. Even the way they issue notifications varies from product to product. And some (I’m looking at you, Whatsapp) don’t offer a desktop client product at all.

    I spend every day working with these messaging products, and I wanted to find out: Is there some way I could use an IRC client of my choice to interact with these various walled gardens (recognizing that, yes, that would come with some loss of functionality)?

    Well, with a lot of hacking and elbow grease, I can definitely say the answer is yes! Though… this is, as is the case with many of my projects these days, probably not for the faint of heart…

    Continue reading...