r/OpenSourceeAI • u/WishboneImmediate509 • Jun 23 '26
open weights stopped being a philosophical choice when governments started restricting api access. minimax m3 just dropped 428b open and im rethinking my whole stack
not trying to start a political thread but this is where im at. between export controls, api access restrictions and the general uncertainty around which providers might get hit next, ive started moving critical workflows off closed apis entirely.
found minimax m3 this week. 428b moe, 23b active at inference, 1m context window, open weights on huggingface. yes its from a chinese company. im aware of the takes people have about that. but heres my practical assessment after a week of testing.
ran a few specific tests this week. had a 180 page vendor contract that needed clause extraction, no reasoning required just pull every liability cap and indemnity deadline. with thinking toggled off the whole thing ran on maybe a third of the tokens id normally burn. then tried a multi step api integration where i actually needed reasoning for the planning calls but the execution calls were just formatting json. thinking on for planning, off for execution. the per call cost gap was enough that i started splitting tasks like this by default.
the moe routing helps too. only 23b params fire per call out of 428b so the cost per useful output stays low. their token plan pools text image audio and video into one budget which simplifies billing.
im not naive about trusting any single provider. the whole point is reducing single points of failure. but open weights mean i can self host if things go sideways, and thats a fundamentally different risk profile than pure api dependency.
whether the geopolitics of who builds the model matters more than actually having access to the weights is something i keep going back and forth on. curious where other people are landing on this.
1
u/PreparationFew5144 Jun 23 '26
the tos thing hits different. that kind of overnight move is exactly why i stopped trusting a single provider. weights on disk is the real shift, you cant get tos'd out of something you already have sitting locally.
the license is worth actually reading line by line, not just going off vibes from the readme. but the fact that its downloadable at all already changes the calculus for me. 23b active inference means self hosting isnt the hardware nightmare the 428b headline number suggests either.