![](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.
I’ll do YOU one better: WHY is @[email protected]?
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…
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.
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 ;-)