31–37 of 37 posts
Yall trust LLM providers sweeping up keys and passwords? Sometimes you have a little .env file or config files in your repos that are not checked in... LLMs like to read that stuff and send it in. I don't trust any of the LLM providers, but less so the ones seated in China.
So DeepSeek v4 will cost 2x between 9:00 to 12:00 and 14:00 to 18:00, Beijing Time. This is UTC+8 so to get cheaper DeepSeek: - in London (BST / UTC+1): 11:00 to 02:00, and 05:00 to 07:00. - in NY (EDT / UTC-4): 06:00 to 21:00, and 00:00 to 02:00. - in California (PDT / UTC-7): 03:00 to 18:00, and 21:00 to 23:00. Subscription plans like OpenCode Go might not even pass down this 2x cost since most customers are EU/US.
I thought they just used open weights models on infrastructure they get from someone else. They say,
“What about data and privacy?
The plan is designed primarily for international users, with models hosted in the US, EU, and Singapore for stable global access. Our providers follow a zero-retention policy and do not use your data for model training.”
So DeepSeek v4 will cost 2x between 9:00 to 12:00 and 14:00 to 18:00, Beijing Time. This is UTC+8 so to get cheaper DeepSeek: - in London (BST / UTC+1): 11:00 to 02:00, and 05:00 to 07:00. - in NY (EDT / UTC-4): 06:00 to 21:00, and 00:00 to 02:00. - in California (PDT / UTC-7): 03:00 to 18:00, and 21:00 to 23:00. Subscription plans like OpenCode Go might not even pass down this 2x cost since most customers are EU/US.
Does opencode go use deepseek infrastructure? I thought they just used open weights models on infrastructure they get from someone else. They say, “What about data and privacy? The plan is designed primarily for international users, with models hosted in the US, EU, and Singapore for stable global access. Our providers follow a zero-retention policy and do not use your data for model training.” https://opencode.ai/go
A bit weird that it also applies to weekends. I guess it helps not creating wrong incentives for companies, but it hurts open and personal projects a bit.
A bit weird that it also applies to weekends. I guess it helps not creating wrong incentives for companies, but it hurts open and personal projects a bit.
Quite simple. Chinese software companies rarely have true weekends. Most have alternating "Big/Small Weeks" (alternating between two days off and one day off) or just a single day off. This is the origin of the word "996" (working from 9 AM to 9 PM, 6 days a week) in the 996.icu movement initiated by Chinese programmers a few years ago.
https://github.com/996icu/996.ICU
Now they are just thinking about to not to lose their jobs now. Even worse working environment.
So DeepSeek v4 will cost 2x between 9:00 to 12:00 and 14:00 to 18:00, Beijing Time. This is UTC+8 so to get cheaper DeepSeek: - in London (BST / UTC+1): 11:00 to 02:00, and 05:00 to 07:00. - in NY (EDT / UTC-4): 06:00 to 21:00, and 00:00 to 02:00. - in California (PDT / UTC-7): 03:00 to 18:00, and 21:00 to 23:00. Subscription plans like OpenCode Go might not even pass down this 2x cost since most customers are EU/US.
Does opencode go use deepseek infrastructure? I thought they just used open weights models on infrastructure they get from someone else. They say, “What about data and privacy? The plan is designed primarily for international users, with models hosted in the US, EU, and Singapore for stable global access. Our providers follow a zero-retention policy and do not use your data for model training.” https://opencode.ai/go