AliveBeef

@BakkesMod gg 2016-2026

Thanks to everyone for your support over the last decade, but it's time to move on and close this chapter. More info here: bakk.es/articles/bakke…

@conne_psd @CacheisOut yep

@CacheisOut i was here. it was a good run.

no, maybe this will be our last no.

@CacheisOut It actually was

@CacheisOut Goodbye this account, I guess Cobblestone when?

Yes.

@CounterStrike HOLY SHIT IT FINALLY HAPPENED

Today we are excited to release de_cache: steamcommunity.com/games/CSGO/ann…

Welc☢️me back.

@BraveNightly Generated by GPT 5.5

Linux distros we can confirm ship Brave as the default browser: Zorin OS 17.3+, Nobara Linux 42+, RefreshOS. That list should be longer. The browser is the user's main security boundary for the modern web. Untrusted JavaScript, media parsing, GPU code paths, WebRTC, extensions, login sessions, fingerprinting, phishing, cross-site tracking. All of it converges there. So the default browser matters. A browser has to assume hostile web content will eventually hit a bug. The real question is what a compromised renderer can still reach. That is where Chromium's architecture earns its keep. - Site isolation puts different sites into different sandboxed renderer processes. - The sandbox limits what a compromised renderer can touch locally. - Linux seccomp-bpf cuts kernel syscall attack surface. - Dedicated service processes keep risky functionality out of one shared security context. - Hardened allocation, control-flow protections, and use-after-free mitigations make exploitation harder. The goal is not "no browser bugs." The goal is making one bug less useful. Brave inherits that foundation and strips the Chrome parts that make no sense as a privacy default. No Google account dependency, no Chrome Sync dependency, no surveillance-ad business model, no need to install an ad blocker to get basic tracker protection. On top of that: - Shields on by default, - third-party ad and tracker blocking, - cross-site cookie protections, - CNAME uncloaking, - fingerprinting protections, - ephemeral third-party storage, - bounce tracking protections, - URL tracking protections, - De-AMP, - a native Rust adblock engine. The distro-default question is not "can Firefox be hardened?" It is "what does a normal user get on day one?" Most users will never install 5 extensions, audit settings, or paste in an about:config hardening guide. A distro default should protect those users immediately. One note for maintainers: packaging matters. A browser's internal sandbox is part of its security model, and some packaging formats change it. Native packages from official repositories should be preferred over random repackages. Linux distributions should stop treating the browser as a legacy preference. It is the user's main security boundary for the modern web.

@CacheisOut Maybe. Well if it is, then I was here, I guess. Good run.

@github Well, GitHub Copilot is certainly never going to be used again

Starting June 1st, GitHub Copilot will move to a usage-based billing model as GitHub Copilot supports more agentic and advanced workflows. In early May, you'll see a preview bill experience, giving visibility into projected costs before the transition. 👉 Read more about the upcoming change: github.blog/news-insights/…

Well well well

Don't forget to do a data export.

See you next time, Sora. Good riddance.

@DivyanshT91162 First of all, nobody with a working mind would use a vibe coded captcha. Second of all, Anubis exists

CAPTCHA IS OFFICIALLY OUTDATED A new open-source library called Cap is changing how websites stop bots. No puzzles. No traffic lights. No “select all bikes” anymore. Instead, it uses a SHA-256 proof-of-work system — simple, silent, and fast. Why devs are switching: • Only ~20KB in size • Zero tracking, zero data collection • No images, no user friction • Works with any JS runtime • Fully customizable (visible, invisible, floating modes) • Zero dependencies • Can be deployed instantly via Docker This is a full replacement for traditional CAPTCHA systems. Cleaner UX. Faster websites. Better privacy. 100% open-source on GitHub Link in comments.

@CounterStrike [Cache]

@CounterStrike Holy shit, it might actually be happening

What are you doing next week?

@ChatGPTapp As I said previously, it seems OpenAI no longer use RLHF and have transitioned into RLHCPS (Reinforcement Learning from Hyper-Cryptic Shitposts)

all you can eat

@ChatGPTapp OpenAI no longer use RLHF and have transitioned into RLHCPS (Reinforcement Learning from Hyper-Cryptic Shitposts)

@bridgemindai This isn't AI. It's slop. Anyway, what do you expect from China? [not even exclusive to China] Run it yourself or wait until other providers run it.

You're paying $1.74/$3.48 per million tokens for DeepSeek V4 Pro to train on your prompts. Read that again. You pay them. They use your code to make their model better. OpenRouter's privacy guardrails literally block it by default. Ranked #14 on LMArena Code. Trains on your data. And you're paying for the privilege. This isn't an AI model. It's a data collection service you pay a subscription for.

@deepseek_ai What is this month???

🚀 DeepSeek-V4 Preview is officially live & open-sourced! Welcome to the era of cost-effective 1M context length. 🔹 DeepSeek-V4-Pro: 1.6T total / 49B active params. Performance rivaling the world's top closed-source models. 🔹 DeepSeek-V4-Flash: 284B total / 13B active params. Your fast, efficient, and economical choice. Try it now at chat.deepseek.com via Expert Mode / Instant Mode. API is updated & available today! 📄 Tech Report: huggingface.co/deepseek-ai/De… 🤗 Open Weights: huggingface.co/collections/de… 1/n

@OpenAI Drunk Sam Altman leaked it. Anyway, cool. But this isn't Spud, is it?

Introducing GPT-5.5 A new class of intelligence for real work and powering agents, built to understand complex goals, use tools, check its work, and carry more tasks through to completion. It marks a new way of getting computer work done. Now available in ChatGPT and Codex.

I'm a vibe coder, scare me with one word.