Ramin Farajpour Cami
593 posts
@realraminfp
Software | Security | Blockchain (Web3 - Solana) Engineer Power is always dangerous. It attracts the worst and corrupts the best - Ragnar
I will say it again, we used GPT5.4 and Opus, and we were able to autonomously find zero-days in the Linux Kernel (in the last 3 weeks) Mythos is probably better at the task of finding potential issues in code, but imo the threshold for "scary" was reached in December or even earlier This is a great hype machine for Anthropic, especially that they plan to do IPO eoy I totally agree - this is not a new capability
What if your logging bill could be 73% lower? 📉 We see two major problems with traditional logging infrastructure - Massive log storage costs and - Complex logging infrastructure Grafana Loki solves this, but it does it differently than systems you might be used to (like Elasticsearch). Unlike traditional logging systems, Loki only indexes metadata (labels + timestamps), NOT the full log content. Why does this matter? By splitting the Index and the Chunks, Loki allows you to store massive amounts of data in cost-effective object storage like S3 or GCS (as shown on the left side of the image). This provides long-term retention without breaking the bank. But there is a tradeoff thats worth it! Loki prioritizes cost-efficiency over raw query speed. If you run a massive, content-heavy search without using label filters, it will be slower than a full-text search engine. But for 95% of observability use cases, the cost savings make it an easy choice. We have a comprehensive guide breaking down Loki's architecture, from chunk storage to query execution. Read it Here: devopscube.com/grafana-loki-a… What is your experience with logging costs? Have you tried Loki? Share your thoughts below! 👇 (𝗡𝗼𝘁𝗲: Multiple reports, such as a case study from ActiveCampaign, suggest sizable reductions around 73% in hosting costs after migrating to Loki.) #DevOps #Kubernetes #Observability
GitHub is planning to charge for self-hosted runners starting March 1, 2026. Meaning that you're paying for your server + $0.002 per build minute. $10 for 5000 build minutes. On self-hosted runners. Classic Microsoft move.
ok wtf charging for self hosted?
