BSD Cafe Billboard

@usul Oui je me perds un peu je crois

For one of my blogs, I use dotclear, and wrote in french, notes when I did the installation at https://ludovic.hirlimann.net/2023/04/installer-dotclear-sur-freebsd-13.html #freebsd #dotclear

https://ludovic.hirlimann.net/2024/05/giving-nomadbsd-spin.html I was unable to have it work on my latest work laptop, but I'll retry cause it was nice with the newer 15.1 based release. #nomadbsd

Would it make sense to have a job section? Ludo

NextBSD goal, mission and visions · nextbsd-redux · Discussion #406 The first of Joe's responses was last week. Two highlights: … one person's trash is another persons treasure. … – and: Download Server (The preview you see today, with after the superset finishes a few more touches like pkg hook to create LaunchDaemons) Download App (Cross platform management app) Download Desktop (Gershwin) I think that when these key things roll out more, is how it will better align with the rally cry. That said I've wanted to do some research excursions and deviations out of interest here and there … August 15 2026 - Linux compat work, ARM64 ISO lands, and KMS drivers for virtualization (WIP) … I want virtualization on Apple silicon to work better than any other BSD starting with UTM as a first target via QEMU and the native hypervisor working as a follow up stretch goal if it can be done. …

https://littlefedi.org/ a small ActivityPub server written in Go. It ships as a single static executable with a server-rendered web interface, a Mastodon-compatible client API, a durable federation queue, moderation tools, and optional PostgreSQL and S3 support. No runtime to install, no services to wire together. Via https://littleone.littlefedi.social/@stefano/08d20839-b21b-47bc-a1b6-800d1137f36e | https://mastodon.bsd.cafe/@stefano@littleone.littlefedi.social/117076101948770274 @stefano@littleone.littlefedi.social

26/08/11 ⇒ Cleaning costs, or, examining the OpenBSD -fret-clean flag I start with apologies to williewillus, calvin, and reezer on Lobste.rs. Prior to July 9, I would have agreed with you all. But it appears I was wrong. There is no need to further engage; it is clear that critique-from-within is undesirable. Which is perfectly OK, because I stepped away from being on the inside. So let's just keep evaluating OpenBSD's mitigations and we'll continue to learn interesting things along the way. https://briancallahan.net/blog/20260811.html

Always great to see active DOS communities!

26/08/03 ⇒ Show memory information on OpenBSD Finding memory information and usage on OpenBSD requires a few commands and the right places to look. If you are used to Linux, then commands like free are no longer available. Let’s have a look at memory details on OpenBSD. https://bsd-audit.com/openbsd/memory-information-on-openbsd/ 26/08/05 ⇒ Running your own mail server with OpenBSD and OpenSMTPD Self-hosting your own services such as a blog, website, or email is a valuable skill. It gives you a better understanding in the technology and usually also fun to do. With privacy under pressure and Big Tech continuing to store our data, this might be a good time to host your own mail server. https://bsd-audit.com/self-hosting/running-your-own-mailserver/

Tribblix and OmniTribblix m41 released http://tribblix.org/download.html This doesn't have any significant breaking changes on the application side, just a lot of normal version updates, but does pick up the handful of illumos CVEs we've had recently.

Hey, thanks! Now I know to keep them cooler.

Setup a simple web server with bozohttpd on NetBSD. https://bozo.httpd.rocks/

NomadBSD based on FreeBSD 15.1-RELEASE from @pfriedma@pfedi.pfriedma.org : r/NomadBSD cross-posted to r/freebsd.

...and it was an idiot error. I had to enable wg in the host kernel. I knew it was built into the kernel these days...I just hadn't realised I needed to enable it. -->facepalm<--

26/08/01 ⇒ MidnightBSD 4.0.7 RELEASE MidnightBSD 4.0.7 RELEASE is uploading right now. It contains a number of security updates and is recommended for all users. https://bsdsec.net/articles/midnightbsd-security-midnightbsd-4-0-7-release

@grahamperrin Optimus is a trademark of NVIDIA for their implementation of hybrid graphics.And other manufacturers like AMD calls almost the same thing differently.From the CPU-side of the view, PRIME is the underlying interface for iGPU and dGPU (not limited with NVIDIA) to offload heavy graphics tasks to mighty dGPU, mainly using efficient (but poor in performance) iGPU.Before Austin's port of nvidia-drm.ko appears, the only "working" way to achieve hybrid graphics was to use VirtualGL, with configuring individual "screen" for iGPU and dGPU respectively, and screen rendered by dGPU was needed to be transferred to another (for iGPU) with software BitBlt, as physical framebuffer cannot be shared with this method.And current implementation of nvidia-drm.ko relies on PRIME to work. Without PRIME, there's no way (arbitrations) for dGPU to access (part of) physical framebuffer of iGPU.See detailed and precise info by Austin here. https://badland.io/prime-configuration.md

@stefano Thank you.

There's usually booths and a room dedicated to BSD at Fosdem, seem interesting to me to add it, no? Ludo

A follow-up to https://mastodon.bsd.cafe/@82mhz/117002938483503805 @82mhz The linked article (June 2026) began: The work at Include Security has us working with AI day in and day out (hacking it, using it, training it, etc). .. – 18–23 minutes, according to Firefox Reader. I used AI to get a concise timeline. The text below is taken from Claude's response. … The general practice: 2015 The root of it all is Hola VPN / Luminati (Bright Data's predecessor). In May 2015, it was discovered that Hola — a free "VPN" — was quietly turning users' devices into paid exit nodes sold through a sibling brand, Luminati, at up to $20/GB. The discovery came after 8chan's admin, Frederick Brennan, traced a wave of DDoS/spam attacks against his site back to Hola users being abused as a botnet, and outlets like The Register, Fortune/Motherboard, and TechRadar covered it within days. Hola's Luminati brand was described as "the world's largest VPN network," routing HTTP, HTTPS, or TLS requests through millions of idling end-user devices. Luminati (founded 2014) was Hola's mechanism for selling access to its userbase as exit nodes, charging $20 per gigabyte for bandwidth from its free VPN users, and it later rebranded as Bright Data. So the general "your free app is secretly selling your connection as a proxy" pattern is a 2015 story, not a 2026 one. The smart-TV-specific angle: February 2026 The TV angle specifically is much newer, and predates the IncludeSecurity teardown by about three and a half months. Independent tech journalist Janko Roettgers broke it in his Lowpass newsletter (syndicated by The Verge) in late February 2026: with Bright's SDK, a viewer's smart TV becomes part of a massive global proxy network that crawls and scrapes the web, alongside apps on desktop PCs and mobile devices, with the company claiming roughly 150 million such residential proxies worldwide, gathering data later resold to train AI models. Multiple later write-ups explicitly credit this as the origin point: "Lowpass, syndicated by The Verge, first surfaced the smart-TV angle in February, and this is the technical teardown." The AI-scraping tie-in and platform response: 2025–early 2026 Around the same period, the broader AI-scraping-via-residential-proxy story was already building: Krebs reported in October 2025 on botnets like Aisuru fueling large-scale AI data harvesting, and Google dismantled the criminal IPIDEA proxy network in January 2026. By April 2026, FlatpanelsHD was reporting that Amazon, Google and Roku had restricted Bright Data and similar residential proxy networks from their app SDKs (Fire TV, Google TV, Roku OS), while Bright Data continued listing LG's webOS and Samsung's Tizen as partners, with over 200 apps on webOS alone. Your June 2026 post: the deep technical teardown The IncludeSecurity/Buchodi post you linked was the first to actually reverse-engineer the SDK rather than just report on the business model — documenting the peer channel's weak authentication and the iOS VPN bypass — which is why it got picked up so widely (Hacker News, Krebs, CyberSecurityNews, etc.) even though the underlying phenomenon was already known. Aftermath A follow-up Spur.us platform scan in June 2026 quantified the scale: Bright Data, Bright Data Ltd, and Bright SDK accounted for 367 proxy-flagged apps in their dataset, with residential proxy SDKs found in nearly half of scanned LG webOS apps and over a quarter of Samsung Tizen apps. And just last week, Krebs on Security reported LG moving to ban these SDKs from its smart TV apps entirely. So the short answer: the general practice (apps quietly monetizing users' devices as residential proxy exit nodes) was first exposed in 2015 with Hola/Luminati; the smart-TV-specific version of that story broke in February 2026 via Lowpass/The Verge; and your June 2026 link is the deep technical forensic follow-up, not the original discovery.

Here's the title: [image: 1785202914963-dad79b73-5dbc-4b83-ac05-c3326b52f602-image.jpeg] above the editing toolbar. The position is unexpected.