The story continues :) for @bloomquestapp $150.98 Down ✅ $19,849.02 to go. Been a few days busy, but another one just came through. Brick by brick. We keep building. #buildinpublic

Introducing Kimi K3.1 Pro: our most capable 3T-class open-weight model. 🔹 1M-token context, 2.8T total / 104B active params (MoE), Multimodal. 🔹 Full-project coding: games in Unreal, Unity & Godot. 🔹 Excels at parametric 3D modeling in Blender & CAD. 🔹 More reliable at finance work: Accurate modeling with hallucination down by 65%. 🔹 Matching the strongest proprietary models across coding, agentic and knowledge benchmarks. Kimi K3.1 Pro and K3.1 Pro Highspeed (2–3× faster) are now live on Kimi.ai, Kimi Work, Kimi Code, and the Kimi API. Open weights by Nov 4, 2026. 🔗 API: platform.kimi.ai 🔗 Tech blog: kimi.ai/blog/kimi-k3-1-pro

Over a year in, Brackify keeps growing thanks to our amazing community! We’re looking for someone passionate about the FGC/esports scene to join our team and lead growth across marketing, outreach, community, and partnerships. Want to help shape what’s next? DM us!

I have Done it again with DR 0.8. This is a new Site, and it's 4 months old. Started SEO 2 months ago. It was steady until yesterday, it went BOOOM and that right there my friend is a true HOCKEY stick growth lmao.

Here is what we are going to do now! Move everything to a vault service. We can't trust Railway. If they had a leak, they might not have closed it. Migrate Postiz to another provider; we need to evaluate this. It's actually not as easy as it sounds. Railway pricing / UX / UI is good; this is usually why people stay after each incident. There's gonna be a downgrade in UI/UX and a price increase, but nothing beats reliability and safety. I have seen other companies with a modern PaaS service, like Zeabur; they had a major incident and then decided to shut down. I think it's better to move to the big guys, GCP / Azure / AWS. I can't avoid that anymore. AI agents will do it for me. And maybe rotate all 140 keys again. Who knows what's going on in their system. Actually, since the old Railway incident, I've always wanted to create a replica of them as a self-hosted service like Coolify / Dokploy. But with what's going on in the world- cyber-wise, I think it's better to get away from this market.

It's 9:57 am. Been up all night. Postiz is back up! Been a very hard night, and I feel like I let everybody down. All the comments I got were very encouraging; nobody scolded me. Thank you so much for that! During the day, a major PHP vulnerability was discovered, affecting about half the web. Deployments on @railway stopped, and I assumed it was because of that, even though you do want deployments to upload the latest WordPress fix. Everybody pinged Railway on Discord, and there was no answer- crickets... and people started getting extremely worried, especially because of >> PHP. Then I got an email from Anthropic and Stripe saying my API keys were compromised. Still no answer from Railway, but I didn't take the risk; I rotated them and put Postiz down. We all, even in Discord, already understood there was a leak, but Railway reported it only one hour later. So the goal was to rotate all 140 keys (that's wild), because each key is duplicated across different containers (scattered). Some have the same variable with a different value (like different DB pool connections) I was overwhelmed; it was too much, and I froze. I didn't know what to do. I am lying on my Airbnb bed, but I know I need to get into sitting mode to be more serious, so I go to the kitchen and sit on a chair. I asked claude to vibe code a system that: - Will take all the keys and values from Railway (using their MCP) - Will have an easy way to update all of them or one by one. Based on containers. - Give me categories so I can be more organized. and prioritize. I also started rotating keys from 12 am to 7 am. All while Railway is still down and deployments are paused. Once I finished I used Railway MCP to update all the env variables. if AI didn't exists I don't know how I could have done it. Then, around 8:40am to 9:00am, we started deploying everything back to Railway to minimize downtime as much as possible. And now everything is up. I feel bad because DevRels at Railway sweet-talked me into staying after each incident and promised things wouldn't happen again; after two incidents, I should have migrated. I couldn't find a platform I enjoyed as much as Railway, so I didn't want to switch. Railway problems will happen again, and I will do everything I can to make sure they don't affect me like that anymore. The main problem was the lack of communication and 17 hours of downtime, which isn't realistic. In the next few days, we will come up with a solid plan to migrate from Railway to a different service, trust is gone. Also, Postiz grew from $300k to $303k MRR overnight. If you tried to cancel your subscription and couldn't, please contact [email protected], and they'll issue a full refund (super sorry about that). This week, will be security week for everybody!

You have to be an absolute loser to be a grown man calling out of work just to play GTA 6