I was hesitant to use thelounge because of the self-hosting part, but it seems is fairly straightforward to spin up an instance even with just free fly.io resources
Sound capture was a major pain point here 😅 I had to hardcode an alsa loopback device identifier, and beyond that it's very manual - loading alsa's loopback kernel module, connecting my music player to the pipewire device and such
Thank you! I've made small tweaks since posting, like adding config flags to CLI, for instance --style fill will display "filled" bars instead of "striped":
a) the larger the codebase and the less familiar you are with it, the more of a nightmare it will be to hunt bugs or search places to insert code; this is where an IDE becomes extremely helpful by e.g. letting you search a struct across multiple modules, showing lints, compiler errors etc.
b) IDEs are only as helpful if they can be configured with your codebase, and sadly there are probably numerous codebases that won't play nice and let you crate a working config
why not both B)