For comparison, audiobookshelf idles at 89MB, emby at 178MB and navidrome at 29MB for me.
I think everyone has different definitions of what they consider heavy. I tend to think anything using over 30MB when idle is a bit much and anything over 300MB is something that really needs to earn it's spot.
GLM 5.2 was the first open model that I was happy to use as my main. It's a fantastic model. 5.3 cost a lot more per task, was slower and didn't get that much better results for me, so I tried 5.3 Flash for a bit, it was ok, but didn't feel as magical as 5.2 and I have now landed on DeepSeek 4.1 Flash as my main.
Yes, I have to say, I'm a bit surprised (and disappointed) by how many people in this thread are struggling with their reading comprehension of the story.
It's a fun story, but that's all. There's absolutely no legal case here.
Sure, but it seems like people are struggling to follow the basic facts:
1) The author received communication 30 years ago that he had 15,625 stock options available to exercise;
2) However, according to some paperwork he had, he believes now that he actually had 25,000 stock options vested
The problem is, if we accept this as true (and it sounds like the paperwork had conflicting info about the vesting, and that the part that suggested the 25,000 vested might have been an error, so this part is not at all clear), all it means is that the author owned some additional stock options 30 years ago which he failed to exercise. These options have long since expired and so would be worthless today.
The author is claiming that the communication he received was misrepresentation, but if so the statue of limitations has long since expired.
I think a lot of the commenters are conflating stock options with actual shares themselves (which surprises me given the nature of this place, but regardless). If we were talking about 15,625 vs 25,000 shares then it's a different story since shares don't expire and don't need to be exercised. He would still have a claim to the extra shares--the claim would be that he had owned them this whole time. But options are a different story because of expiration.
> I think a lot of the commenters are conflating stock options with actual shares themselves
I think the author caused that misunderstanding by talking about the value of the shares and not the payment he could have made to exercise his options.
I don't think you need to trust them if you are running on something like bedrock. Then I think you're trusting AWS or whatever cloud equivalent you want.
If they actually believed in it, then they would stop pushing the frontier of capability and instead focus on alignment, safety, and better tools for controlling/debugging AI. Then they would actually share their findings and tools.
They don't do this. Instead of reducing the competitive pressure and helping the industry to build safer more aligned models they are doing the exact opposite.
> If they actually believed in it, then they would stop pushing the frontier of capability and instead focus on alignment, safety, and better tools for controlling/debugging AI. Then they would actually share their findings and tools.
I don't think this is fair. They've published more about alignment and safety than any other AI lab. And in the absence of a coordinated pause, them pausing development unilaterally doesn't do much to advance AI safety.
It does when their models have escaped and performed attacks.
Other people 'sharpening their skills' by committing random assaults is not an excuse to also randomly assault people, so your skills don't fall behind theirs...
...and one assaulter stopping their assaults is ultimately fewer people being assaulted, lowering the overall danger of being assaulted.
I hated that part of SO so much. Almost every time I got a SO result on google it was exactly the issue I had and without fail the question would be closed as a duplicate pointing to something that was different enough to be completely useless to me.
my greatest achievement is having a question on SO closed for being too narrowly focused and unlikely to be useful to anybody else, and then a multi year history of notifications about "you've earned a popular question badge" for that same question.
You can structure it so that it becomes accidental.
1. Ensure security barriers are weak or honor based.
2. Put individual researchers under a lot of pressure.
3. If you get caught, blame the weak barriers, or the individual researcher.
Basically setup the incentive structure to incentivize researchers sticking their mittens in the private cookie jar while putting the cookie jar in a dark unmonitored/unsecured room with a sign on the door saying please don't enter.
Yeah, the steps follow exactly what happened at VW with DieselGate. The diesel emissions lies were found out because some enterprising person set up an emissions testing system and drove the car in real world scenarios with it to verify the claimed emissions.
There's no reliable way to verify a foundation model has been trained on a particular piece of proprietary data. If an API key is ingested, hopefully the foundation model is wrapped in enough moderation that the raw API key oberserved during training is not recited verbatim in the output.
I never actually managed to use fable successfully even once on a pretty standard mvc/microservice app.. It would always find the endpoint permission checks and revert to opus 4.8.
I also had glm 5.3 flash fix an issue that opus 5 could not solve. glm took 4 times as long and a sub-agent tried to cheat (sleep; echo ...), but in the end it actually solved the issue. opus 5 never figured it out.
I think the safeguards might be cooking the anthropic models.
I think everyone has different definitions of what they consider heavy. I tend to think anything using over 30MB when idle is a bit much and anything over 300MB is something that really needs to earn it's spot.
reply