Eustáquio Rangel

I have seen Omarchy Linux ... but for some reason I missed Omfreebdy FreeBSD based alternative. I personally use X11 and prefer it over Wayland - but I now know that Omfreebdy comes with X11 version as well. Great to see such option available. omfreebdy.dba.wtf #freebsd

I still wonder what would have happened if you had discovered that Linux is this good a few years ago. Would the timing have been as perfect as it is now? I mean, regarding the maturity of Arch at the time, the tools that existed, your vision of the whole thing. Maybe it wouldn't have been as well-oiled as it has been recently. Often, for the trained eye, there are no coincidences. 😉

I used to dream of having a fully operational system installed in 15 minutes. Then the goal became 5 minutes. Now the goal is 1 minute. We're getting close!

Sway 1.12 Wayland Compositor Released with HDR10 Support via Vulkan Renderer # Most of times using @freebsd I use @hyprwm , but sometimes I boot Sway to take a look how things are going there. :-) 9to5linux.com/sway-1-12-wayl… via @9to5linux #Linux #OpenSource

Tempos estranhos.

@ayubio Cara, tá foda.

Estou aqui no FIB 16 assistindo o representante do Debian defender a aferição de idade em sistemas operacionais abertos. O que raios fizeram com o movimento do. Software Livre, hein? Assustador.

@ayubio 😮

@inazarova Hey, talking about reading, I sent you and @palkan_tula some DMs here. 🙂

I was thinking about this - the CS fundamentals that are most useful for non-engineers now building with agents. My answer rn is to go through guides.rubyonrails.org while building an app - because Rails has perfected the fundamentals of web development.

@iAnonymous3000 @brave Hey @BrendanEich , we can install @brave on @freebsd using the Linux compatibility layer, but there's a lot to install. Just wanna know if is there even a remote possibility to have it native there someday.

Linux distros we can confirm ship @Brave as the default browser: Zorin OS, Nobara Linux, and RefreshOS. That list should be longer. For most desktop users, it is the main security boundary for the modern web. Untrusted JavaScript, media parsing, GPU and WebGL paths, WebRTC, extensions, login sessions, fingerprinting, phishing, and cross-site tracking all converge there. So the default browser matters. A serious browser has to assume hostile web content will eventually hit a renderer bug. The real question is what the attacker can still reach after that. This is where Chromium’s architecture earns its keep: - Site isolation puts different sites into separate sandboxed renderer processes. - The sandbox limits what a compromised renderer can touch locally. - Linux seccomp-bpf reduces exposed kernel syscall surface. - Privilege-separated browser, GPU, network, and utility processes reduce blast radius compared with a monolithic browser. - Chromium’s broader hardening around allocation, control-flow integrity, and use-after-free mitigation makes exploitation harder. There is a second axis a lot of architectural debates skip. A default browser also has to land Chromium security fixes fast. Time-to-patch is part of the threat model. A distro that picks an architecturally strong browser but ships updates slowly has not actually given users a safer default. At Brave, we inherit that Chromium foundation and remove the parts that make no sense as a privacy default: no Google account dependency, no Chrome Sync dependency, no Google-style cross-site surveillance ad model, and no need to install an ad blocker just to get baseline tracker protection. On top of that, we ship real protection on day one: - Shields on by default - third-party ad and tracker blocking - cross-site cookie protections - CNAME uncloaking (canonical-domain resolution) - fingerprinting protections - ephemeral third-party storage - bounce-tracking protections - URL tracking-parameter filtering - De-AMP - a native Rust adblock engine One note for maintainers: packaging is part of the browser security model. Linux distributions should stop treating the browser as a legacy preference.

As a @primus fan, I bought this album when it was released, but on CD. Now my vinyl copy has arrived! Who else likes the band? As a bassist, I'm crazy about their sound. 🎸

New "war paint" ready on my computer running @freebsd ! Here's a spoiler: after the video I made about Ken Thompson and Unix, I decided to revisit the little knowledge I had about the @golang and I'm liking what I'm seeing. I'm always learning new languages and of the last ones I've seen, Go has sparked the most interest.

This is exactly what I was expecting from @NASA @NASAArtemis a showcase of technology!

Minimum requirements for Linux

Para comemorar que o Set agora é parte do core e não mais da standardlib em Ruby, já ganhando um incremento em performance, fiz um vídeo falando sobre isso e um pouco sobre O(n) e O(1). Espero que gostem! 🙂 youtu.be/atOsDq9C_Uw?si… #ruby

@nateberkopec I'm the weirdo! 🤪🙋🏼

Interesting to hear this (pretty good!) advice from the hackers themselves. Restricting IDEs sounds tough though. What do you do about the weirdo on the SRE team that uses Neovim?

I must confess that every time I hear or read about Mitre, I automatically imagine a Kaiju. It must be because of Mothra. 🤪 Anyway, it's going to be related to some kind of threat. 🙂

Ouch. #github #rpoQm20zzu" target="_blank" rel="nofollow noopener">limewire.com/d/GfED8#rpoQm2…

Daqui alguns dias (talvez uns 15) vou mostrar como que eu desenvolvo de boa utilizando Ruby e Rails no @freebsd . Enquanto não consigo tempo para montar o script e gravar o vídeo, aqui tem um aperitivo da coisa. 🙂 😈 #ruby #rails #freebsd youtube.com/shorts/DPyq953…

⚠️Claude Code's Network Sandbox Vulnerability Exposes User Credentials and Source Code Source: cybersecuritynews.com/claude-codes-n… Anthropic’s Claude Code AI coding assistant harbored a critical network sandbox bypass for over five months, allowing attackers to exfiltrate credentials, source code, and environment variables from developer systems, and the company issued no public advisory for either incident. A second complete bypass of Claude Code’s network sandbox, marking what he describes as a consistent implementation failure rather than an isolated bug. The vulnerability, a SOCKS5 hostname null-byte injection, affected every Claude Code release from v2.0.24 (sandbox GA on October 20, 2025) through v2.1.89, spanning approximately 130 published versions over roughly 5.5 months. #cybersecuritynews

We're building a Moon Base! @NASAMoonBase will serve as a habitat where astronauts live and work during long-term science missions. Join us at 2pm ET on Tuesday, May 26, for a live news event where we’ll share updates on our lunar exploration plans: go.nasa.gov/4uinkLi