Do any of the UHD/4k tv channels work?
Been trying to watch the FOX UHD for the soccer games but doesn’t work.
Been trying to watch the FOX UHD for the soccer games but doesn’t work.
Dan does a great job of explaining how close, or far, according to some, the open source vs. SOTA model race is. Really enjoyed this video https://youtu.be/cFYdiynrxpQ?si=0vamlAqO3rx0FKV2
For those who frequently complain here, it's important to note that open-source models aren't designed to compete at the highest levels. They are great bargain-bin daily drivers and more than adequate for 90% of the work we expect to get done.
The 5-hour limit bar and the weekly limit bar seem to be arbitrary. If they added a bar that depicts the usage vs total usage for the plan in Plan Usage, it would be more helpful, I feel.
UPDATE: They added this now, I put a screenshot in the comments with my grievances.
Title says it all
Looking at the documentation here https://platform.minimax.io/docs/guides/image-generation the payload still has image-01 as the model.
payload = {"model": "image-01","prompt": "men Dressing in white t shirt, full-body stand front view image :25, outdoor, Venice beach sign, full-body image, Los Angeles, Fashion photography of 90s, documentary, Film grain, photorealistic","aspect_ratio": "16:9","response_format": "base64",}
so now instead of image-01, should we use MiniMax-M3 as the model name there?
A US federal court has rejected Chinese AI company MiniMax’s attempt to toss out a copyright infringement lawsuit brought by some of Hollywood’s biggest studios. The ruling keeps alive claims that MiniMax scraped protected content, including Marvel and Star Wars characters, to train its Hailuo AI image and video generation system.
China's MiniMax loses bid to end Disney copyright lawsuit over AI system | Reuters
Mimo has cut its pricing down to match DeepSeek and now I am regretting getting the Plus annual plan.
https://platform.xiaomimimo.com/docs/en-US/news/v2.5-price-update
I’m using MiniMax-M2.7-highspeed through an Anthropic-compatible endpoint inside an agent framework called Hermes.
MiniMax appears to advertise a large context window, around 204,800 tokens, but I’m seeing API failures well below that.
The error looks like this:
⚠️ API call failed (attempt 1/3): BadRequestError [HTTP 400]
🔌 Provider: minimax Model: MiniMax-M2.7-highspeed
🌐 Endpoint: https://api.minimax.io/anthropic
📝 Error: HTTP 400: invalid params, context window exceeds limit (2013)
📋 Details: {'type': 'error', 'error': {'type': 'invalid_request_error', 'message': 'invalid params, context window exceeds limit (2013)'}, 'request_id': '065b1bb0eab63a4b21e50cb78514'}
⏱️ Elapsed: 2.61s Context: 106 msgs, ~134,146 tokens
Provider reported overflow amount only; keeping context_length at 204,800 tokens and compressing.
⚠️ Context length exceeded at minimum tier — attempting compression...
🗜️ Context too large (~134,146 tokens) — compressing (1/3)...
🗜️ Compacting context — summarizing earlier conversation so I can continue...
My questions:
Processing img z1yb3e61rx1h1...
Why does compaction happen at token 106k when my token max is 204k? Started seeing this alot recently.
I am looking to move my Hermes VPS implementation from a reactive chat tool to a persistent agent similar to "Felix" from the Nat Eliason interview: https://www.youtube.com/watch?v=nSBKCZQkmYw
I have a few questions on the mechanics of proactivity:
The Wake Up Trigger: How does the agent theoretically "wake itself up" to perform unprompted actions? For example, if a bug is reported or a new feature is requested via a ticket, do you use an MCP to trigger an interrupt, or a persistent heartbeat loop that polls for new tasks?
Autonomous Coding: For a bot that builds its own features, how are you handling the handoff to worker sessions? I want the agent to identify a bug, spawn a persistent worker to fix it, and notify me only when the PR is ready. How do you prevent the OS from killing these long sessions?
Memory Consolidation: For 24/7 operation, how do you handle nightly context cleaning? I want the agent to extract "nuggets" from the day into a knowledge graph without overwriting core system rules or hallucinating data.
If you have structured a "Heartbeat" skill or a specific config for proactive workflows, I would love to see how you are bridging that gap.