ah, understandable. i’m a EE by day and all of the coding i contribute to Mbin is purely for fun with no bearing on real-life, so my github profile is expendable/only for Mbin. ;-)
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.
ah, understandable. i’m a EE by day and all of the coding i contribute to Mbin is purely for fun with no bearing on real-life, so my github profile is expendable/only for Mbin. ;-)
if you can, please create an issue for this specific problem at https://github.com/MbinOrg/mbin/issues if one doesn’t already exist or thumbs-up/add a comment to an existing one so it gets visibility. broad fediverse compatibility is one of our main project goals, but not all platforms conform to the AP spec (or it’s not addressed by the spec) and instead do their own thing, so it sounds like we’ll need to work out a common ground.
no, we maintainers (~6 active out of 13 total) have full merge power and admin rights over the repo, all it takes is 1 other maintainer to approve a PR for it to be eligible to get merged into our main branch… C4 ftw https://github.com/MbinOrg/mbin/blob/main/C4.md.
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 ;-)
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 @[email protected]
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.
@[email protected] pointed out that after reviewing the html source there’s a link to this https://github.com/Linuzifer/domain_seizure… looks like a joke or a hack.
We were so preoccupied with whether or not we could that we didn’t stop to think if we should.
prozac
though i’ll be honest, the several months of dialing-in the initial dosage were an absolute hell, but once it starts working… like hot damn, a whole new person. i can’t function without it, but everyone reacts differently to SSRIs… so YMMV and it’s definitely something to consult a physician about if you’re serious.
The Fly… fuck.
Mbin’s API is 100% compatible with kbin as of today, so @hariette should have little to no issues pointing Artemis at Mbin instances.
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.
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 don’t care what you want on it, every pizza comes with pepperoni and with 9mm bullets on it. If you don’t like it, I don’t care cause you’ll receive one anyhow. The only difference is, maybe the 9mm bullets will be in the gun or maybe they’ll be on your pizza.
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).
undergrad C/C++ background, PHP is a cakewalk by comparison :-)