![](https://kbin.run/media/a5/b0/a5b06f9184a3d94e3c48ee2bdef7c29890883528a5fe1ed0039fc7594de658c5.png)
![](https://programming.dev/pictrs/image/170721ad-9010-470f-a4a4-ead95f51f13b.png)
you flux the fluxing flux out of it
friendly neighborhood kbin.run admin, possibly a sentient lifeform… likes pizza and beer.
professional pixie wrangler and rf magician
Mbin contributor and maintainer, aka nobodyatroot on GitHub.
you flux the fluxing flux out of it
not if you want to make it back to your car at the end of the day ;-)
i know this is for the lols, but you’d be surprised how often stuff like this happens… bodge wires and dead bugging it are much cheaper than re-spinning a board/IC. anything to get the boss off your back, just make sure to give your technicians a case of beer/beverage of choice for the extra effort fixing your fuck up.
it satisfies the borrow checker or else it gets the hose again
mbin.social ;-)
https://mbin.fediverse.observer/list https://fedidb.org/software/mbin
we’re “spread” out on purpose to avoid becoming an unwieldy behemoth like kbin.social…
paging superstar @jwr1@kbin.earth
kbin.run admin here, i’m curious if this cert problem is still happening as i recently loosened up some of my super strict bot killing mechanisms… give it a shot again and DM me if it still doesn’t work so i can try to figure out what’s going on.
as for the name… yea, i should have named it something different. at the time, kbin was the only horse in town and the intent was to help alleviate some traffic from .social before the foundation took over to run it on their cluster… then things fell apart. unfortunately, i can’t rehome it to a new domain because it will break federation of all existing content, accounts, etc.
We were so preoccupied with whether or not we could that we didn’t stop to think if we should.
6.6.5 has been a massive pain in the ass with the MTK wifi in my asus g14. very happy this got released quickly, no more deadlocks!
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.
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).
Dave Plummer has a very interesting take on this since he was the dev manager for Windows CD Autorun at the time. https://www.youtube.com/watch?v=PqWjq2SdzpI
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.
Zig is really starting to grow on me, it’s basically an unfucked C (screw you, macros) and you can translate C into Zig code…and it has comptime, very nice! I don’t have the patience for Rust in my hobby projects and the standalone-ness of Zig is perfect for embedded/systems programming. it definitely needs to mature more before the masses start taking it seriously, but goddamn it’s nice to code in.
hard to say for sure, but U109 and U208 could be UART into those Cisco baseband or radio chips. one placement for the 2.4 GHz (G) and 5 GHz (A), respectively. would be interesting to probe around there and see if you get a serial interface to it… obviously for extra credit ;-)