CD #Burning

@lproven@vivaldi.net "...it's a clear sign it's AI!!!!!" 😆

Em dashes are fucking amazing

https://psychotechnology.substack.com/p/em-dashes-are-fucking-amazing

An ode to a punctuation mark

@grunfink@comam.es this is extremely cool!!!

$ ls -l
total 920
-rwxr-x--- 1 grunfink src 607888 jul 25 13:42 snac
-rw-r----- 1 grunfink src 330882 jul 25 13:43 snac-2.93.tar.gz

Back to normal in Harwood. It's a soft, light rain which should soak in if it lasts. #NPennines #Weather

@stefano

An ingenious Fediverse design idea, fully implemented in the most frugal of hardware setups (in NetBSD). So charming.

Bravo, Stefano.

"The post you wrote is the blog post. Same database, same act of writing, still boostable, still repliable, still part of the conversation on the fediverse side. The blog is just a second representation of the same content, generated automatically."

"As a status, it lives in the fediverse, interactive, part of the conversation, subject to replies and boosts like anything else. As a static page, it lives on the web, durable, indexable, with a permalink, something an RSS reader can hold onto. You don't have to decide in advance which posts deserve to last."

#blogging #MicroBlogging #FediToWeb #FrugalComputing

#StefanoMarinelli #lttleFedi

Absolut fantastisch, der Strand von Nõva Rand! Feiner Sand, Dünen und Kiefernwälder. Naturschutzgebiet. "Am Wochenende kann es voll werden", heisst es in der Beschreibung. Das bedeutet wohl, dass noch andere Leute hier am Strand sind. So waren wir weitgehend allein.

#estonia

@EnigmaRotor@bsd.cafe it definitely is

Hey y'all, meet Sunny! (name might change, not sure yet)

I think he could totally replace the #Firefox logo. 😄

#FloofSon #Sunny

Before making this public, it'll probably be wise to make a test instance with more users. I'll think if this will be a BSD Cafe instance or not.

#littleFedi

@blint@tutter.org currently not. the posted media will appear at the beginning (or end, still unsure which is the best approach) of the post. It would be a sort of quirk to implement it in the middle but still...maybe I can use some sort of custom shortcode like [1] for the first photo, etc and make sure it will be removed by the fediverse post, keeping only the photos... thinking...

@blint@tutter.org thanks. the idea is: it's not BSSG, it's not Wordpress, it's just another way to keep and distribute contents.

The Blog Option in littleFedi

littleFedi, like many social platforms, had both a strength and a limit. Posts, by their nature, are ephemeral. They get published, federated (unless local-only, which littleFedi handles) and then, over time, lost. Partly through self-deletion, partly through their normal blending in with the thousands of other posts that pile up over time. Sometimes, though, we want something to stay. And not just stay as a social post, but as an actual blog. A bit like with BSSG, I had thought it would be convenient to have a minimal system. Not to compete with WordPress or other solutions, but to have a small blog, integrated into littleFedi, that would produce and serve a blog updated every now and then, whenever the person writing felt like doing it.

And that's why the blog option was born.

The idea is simple: when you write a post, from the web UI or from the CLI, there's a checkbox, "blog post". If you check it, that post stops being just a status that will scroll past and disappear. littleFedi renders it into a real static site. No JavaScript, just HTML and CSS, an Atom feed, tag pages, a chronological archive. Nothing exotic, nothing that needs maintenance five years from now.

The blog isn't a parallel system you have to feed separately. It's not an export, not an import, not a bridge to some other CMS. The post you wrote is the blog post. Same database, same act of writing, still boostable, still repliable, still part of the conversation on the fediverse side. The blog is just a second representation of the same content, generated automatically. Every time you create, edit, or delete a blog post, the whole static site for your account gets rebuilt from scratch, and the new version replaces the old one atomically, so nobody ever lands on a half-built page. If the build fails, the previous version stays in place. Simple, but it has to work reliably, or the whole idea is pointless.

That's the core of it: two representations of the same post. As a status, it lives in the fediverse, interactive, part of the conversation, subject to replies and boosts like anything else. As a static page, it lives on the web, durable, indexable, with a permalink, something an RSS reader can hold onto. You don't have to decide in advance which posts deserve to last. You write normally, and if something turns out to be worth keeping, you flag it, and it gets its own page.

One detail I cared about while thinking this through: the generated site has to be self-contained. When littleFedi builds it, media gets copied or hard-linked into the generated directory - images, audio, video. If it's stored on S3, it keeps its public URL directly. Either way, the point is that the site on disk doesn't depend on the instance staying up. If the server goes down tomorrow, the blog files are still a complete, working website. That wasn't an afterthought, it was one of the requirements from the start.

Not every account gets a blog, and that's intentional. The instance admin has to enable the feature globally ([blog] enabled = true), and then grant it per account. It's not meant to be a CMS, and I didn't want it to become one. Blog posts can't be replies, can't be boosts, have to be public and top-level. These are constraints, not missing features: the blog is for your own writing, not for threads or reshared content.

There's no JavaScript anywhere in the generated site. That was deliberate too. It loads fast, it works offline if you cache it, and it will still render correctly in ten years without anyone having to update a dependency.

In the end, the blog option doesn't ask you to choose between writing socially and writing something permanent. You keep writing the way you always do, on littleFedi, and if a post is worth keeping, you check a box. No separate platform, no migration, no vendor lock-in. Just your own posts, some of them rendered into a small static site you can host anywhere, built out of something that already existed on the open web.

Remember: all this is being currently served by a Raspberry PI Zero W powered by NetBSD

Here's the result: https://rpi0w.stefanomarinelli.it/@stefano/blog/691cb62e-e7a1-434b-ba65-d059ee58ac41/

#littleFedi #SSG #BSSG #OwnYourData #Blogging #Fediverse #NetBSD

I was a 911 dispatcher for a decade.

To really understand how absolutely terrible an idea it is to have AI answer 911 calls, I'll present you with a single real-life call:

Upon answer, the caller calmly began ordering a pizza. Large, pepperoni. Side order of chicken wings. To be delivered promptly.

The only sign the caller gave that things were amiss? She rather ignored the first few questions from the calltaker.

Because she was being physically abused, had already been beaten, and her abuser was *IN THE ROOM* listening to her order pizza.

Tell me how your AI is going to read between those lines.

@catavz@mastodon.social that would be nice

Simulator games have really jumped the shark. Here's a liquor store simulator. Really!

https://store.steampowered.com/app/3124550/Liquor_Store_Simulator/

Dev accidentally commits Copilot binary to FreeBSD ports repo

https://www.theregister.com/os-platforms/2026/07/24/dev-accidentally-commits-copilot-binary-to-freebsd-ports-repo/5278458

Git is aptly named: it isn’t easy – but there are alternatives

<- by me on #TheRegister

I’m sleepy but I don’t want to sleep, so that this day won’t end.

New episode of my uneven fight with Asus Meteor Lake based laptop on #freebsd :)

I did not surrender :)

I found new way to make my OLED display work after loading i915kms. And it doesn't bork console forever. Meaning I can switch back and forth X11 --> console --> X11.

These three lines made things work (actually two):

hw.i915kms.enable_guc="3" <--- this is old
efi_max_resolution="2880x1800"
kern.vt.fb.default_mode="2880x1800"

After having console problem out of the way, the only "small" problem left were GPU hangs. Ugh...

Guess what... The same person that was helping me on github with display problems said "here is a patch for i915, try it". It consists of three small changes.

Aaaaand - it works ! I'm using this laptop on #freebsd for three consecutive days and I had no GPU hang. Not even one !

Now a blatant word to #freebsd devs :) Maybe it would be worth reading those github issues from time to time ? There are a lot of skilled people around the world.

And BIG thank you to anonymous person that helped me. I do appreciate your time and effort.

Situations like that make me be believe in people again.