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.
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 @melroy@kbin.melroy.org?
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.
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.
and they better watch out, there’s a live stick of dynamite next to that ekg machine. time’s a ticking, hurry up and buy!
war thunder forums, your one stop shop for restricted military documents
undergrad C/C++ background, PHP is a cakewalk by comparison :-)