mbin is a very recent fork (has all the latest commits from the kbin dev branch as of today), so not much of anything "new" or groundbreaking has happened yet. i think the main thing right now is catching up on the backlog of PRs that have been stuck in the kbin queue for months, even basic things like bumping the dependency versions to improve package security was enough to convince me to move my instance over.
debounced
i use Tailscale on everything these days (or use Headscale if you want to self host the control plane). with the free plan you get up to 100 devices on a "tailnet", just set the right ACLs to only allow the remote connection ports of choice, pair it with self hosted RustDesk, and you should be good to go. the NAT traversal of Tailscale is pretty good from what i've observed, but sometimes you might get stuck on a relay (called a DERP) if it can't get across the firewall(s).
omg me too... a much nerdier friend of mine told me to install Gentoo on my first custom build back in the early aughts. printed out the guide and spent over a week 24/7 compiling everything with an athlon 64 3500+... and had never used Linux before this... good times, man.
it probably wouldn't be too hard to diplex it with one of the low band antennas, wouldn't be great reception but it'd give you something for FM stations that are close enough. a relatively big ass coupling inductor and small series cap before the antenna tuner shouldn't do too much insertion loss damage, these cellular front ends are lossy AF already... and the lowest low band freq is like 6x higher from the FM band, so isolation should be ok... dunno, obviously adds more cost than what it's worth to the bean counters in charge i'm sure.
from what i recall almost every QCOM chipset has the circuitry baked in, it's just disabled. https://www.wired.com/2016/07/phones-fm-chips-radio-smartphone/
it's also a big FU to everyone accessing Gmail's web interface over geostationary satellite internet connections. i had to deal with that shit for a few months and HTML mode was the only way to ease the pain from how bad the latency can get. the "normal" view would hang like a mofo all the time.
war thunder forums, your one stop shop for restricted military documents
ow, my [registry keys]
seems like this is an area that a nice "arrangement" could be made, that is, US congress: you grant T-Mobile their band 41 licenses that are being held up by your own incompetence in exchange for T-Mobile actually addressing their own repeated incompetence involving anything related to data security. sell it to the public under the guise that it would be detrimental to the US consumer by letting T-Mobile continue to expand their public reach while completely ignoring the importance of data privacy and security of said public... and you can go on taking bribes from AT&T and Verizon in the meantime, dunno, sounds like a win-win to me.
Yep, find a cheapo 5g modem with an ethernet port that's capable of being given an identity crisis from the usual sources and you'll be golden...ask me how I know. We ain't got shit out where I am other than garbage DSL, but decent 5g coverage from the big 3 surprisingly.
Starlink only serves a purpose in truly rural or remote areas where, unsurprisingly, they'll make no money. The number of people I see using it as a backup connection or aggregate it with terrestrial cable or fiber connections is obscene... and a waste of money imo.
we're making it super easy for any existing kbin instance to migrate to Mbin, just a matter of pointing git at the new repo, pull, and update as usual.