old, stupid
its been suggested… i think its called ‘community groups’ or something like it. you could aggregate any community subscriptions into an arbitrary group
it was suggested as a fix for all the same-topic different instance issue… you could add the ‘cats’ community from all the different servers into one group. would fit your needs it sounds like.
why ask why, try bud dry
its in active development, for starters.
the point of mbin wasnt originally differentiation of any kind, it was that the lone kbin dev did not share duties, or actually develop on a normal timeframe. this behavior kept kbin from flourishing and implementing all kinds of suggested, developed PRs.
it was forked to mbin as a community project where anyone who wants to contribute basically can by committee instead lone stewardship. you would need to check the repo for all the changes per version… but the best part is, its an active dev group.
hell they could have called it anything… seems like they couldnt get past their egos to see the value in a new designation
not really. kbin is kinda dead. long live mbin
i hope so. its part of the reason i run an instance. to give people a place to migrate to, but still be able to contact their peeps.
well, kbin is somewhat defunct. mbin is under active development, and many of these things are on their radar. moderation tools are coming along, user list is not really an issue. they even got mfa workin!
these applications and the environments they are building are in their infancy. instance admins cannot expect a mature product, or that they wont need to get their fingers dirty to implement features they want. lemmy is at what, 0.19.4?
the image caching/filtering is good example of an ongoing concern 'verse-wide. as the lemmy devs pointed out, if this is a solid concern as an admin you would implement file scanning. if you absolutely want to use lemmy and need a user list, build it.
this removed is not turn-key
e. ive been running mbin at https://moist.catsweat.com almost a year
answer; big engines have acoustic/vibration side effects making them unstable. smaller engines more reliable, reduce risk of overall failure.
my favorite bit was how no one at microsoft actually understood their own licensing pricing. for decades, you could call microsoft for pricing and get different answer from people in cubicles next to each other or even from your own rep.
it was as if they were making it up as needed.
feels like this post was sponsored by Anne Hathaway
firefox
no. no reason to expand poor practices into linux because microsoft removeded up. we need ‘least access required’ methodology even at home because the world is full of bad actors.
if microsoft had correclty implemented security into dos/winx.x we wouldnt have had half the virus issues we did in the late 90s.
i think the other half was caused by activex
microsoft doesnt want to annoy people, but in a corporate environment this requirement is fully implemented on windows.
i was never under the impression macs belonged in a business environment. maybe apple just doesnt find that level of security important.
i am no fan of the proprietary model here, but i think they disingenuously compare it to the rabbit R1 device.
i love the idea of an local-llm-in-a-box, and they claim to have a working (minimal featureset) model that could be expanded. the rabbit device is a glorified siri
with everything being web-based, windows is slowly turning into a fancy dummy term/thinclient. exactly the control businesses want.
linux on the other hand is being fleshed out as a true desktop pc with all the customization most of us expect of a daily driver.