dump1090_rs VS The Lounge

I test it all the time with my own https://github.com/rsadsb/dump1090_rs. But it should be able to use the adsbexchange c program: https://github.com/adsbxchange/readsb.

github/dump1090_rs

I'd like to use the following: https://github.com/kevinmehall/rust-soapysdr, but for now I'm using my own bindings that just support rtlsdr: https://github.com/rsadsb/dump1090_rs/blob/master/src/rtlsdr.rs

The github projects are https://github.com/rsadsb/adsb_deku and https://github.com/rsadsb/dump1090_rs.

Thanks, I'll have to fix my ui scaling it looks like. Also, I have a rust version of dump1090: https://github.com/wcampbell0x2a/dump1090_rs.

https://github.com/wcampbell0x2a/adsb_deku https://github.com/wcampbell0x2a/dump1090_rs

dump1090_rs is a demodulator that can forward info to the radar and 1090 apps included with my library for the display of the information.

IRC as a protocol is indeed incredibly simple and easy to get started with. Years ago did discover this when I was able to make [this atrocity](https://github.com/creesch/discordIRCd) bridging IRC and discord where for IRC I effectively did a simple server implementation.

There is a caveat, though. Like many older protocols (ftp) there is a lot that was not initially written down or left up to clients and server implementations. This, does lead to a lot of edge cases you need to be aware of once you want to actually support a wider user group.

Also, as this is apparently is still a discussion. IRC is not simple from a modern user UX perception. Registration can be complex and confusing, though hidden a bit through clients. Managing channels with various flags is a whole other thing. Then there is also the fact that these days people are no longer used to the fact that they can't see messages from periods where they were not connected. Of course, the latter can be easily handled by a BNC or fancy clients like https://thelounge.chat . But, that is only easy for technically inclined folks.

> It’s 2024, people aren’t going to go out of their way to setup “bouncers” to keep up with conversation that happens when they’re not online or leave their computer running 24/7.

You can just set up something like The Lounge [0].

[0] https://thelounge.chat/

Excellent idea! You'll have a mature, open standard protocol under the hood, with no vendor lock-in, excellent extensibility, and great modern frontends like The Lounge (https://thelounge.chat/) or Convos (https://convos.chat/) to choose from (and you can choose).

For the other layers one can front-end IRC with TheLounge [1][2] or Convos [3][4]. TheLounge only persists history in private mode meaning that users are created in that front-end and chat messages are in Redis. For small networks or groups of friends this is probably fine.

Notably missing is voice chat. I use the Mumble client [5] with the Murmur or uMurmur [6] server which is light-weight enough to run on ones home router. I use it on Alpine Linux, works great. It's not a shiny and attention grabbing as Discord but probably fine for everyone else. For people to create their own voice channels would require the full-blown Murmur server.

[1] - https://github.com/thelounge

[2] - https://thelounge.chat/

[3] - https://github.com/convos-chat/convos/

[4] - https://convos.chat/

[5] - https://www.mumble.info/

[6] - https://github.com/umurmur/umurmur/wiki/Configuration

As another self-hosted solution, I quite like TheLounge (https://thelounge.chat)

TheLounge (https://github.com/thelounge/thelounge) - web IRC client that I set to listen on my vpn/mesh. Works great on desktop and mobile, and supports push notifications.