details:not([open]) > :not(summary) {
  display: none;
}

Additionally, I added name=snac-note attributes to the details element of all "Reply..." sections, and name=snac-top-controls to the top control elements. Only one of the details elements that share the same name is allowed to be open at any time, and thus, if I open the "Reply..." drawer on one post, and then open it on a second post, the first one would automatically close itself. This helped me with the "All details unfolding due to search" issue before, but setting display: none using CSS seems to be a better solution for this problem. Still, I think I'm liking the "only one open at a time" rule, but not sure if it's worth the patch.

The CSS change I proposed at the top may be somehow annoying in one case I can think of: someone has their settings set to start with all posts folded closed, and wants to search all folded entries for a specific term (like their own name, or something). In this case, their search would come empty, because all content is not actually added to the DOM.

Anyway, if you think either of those changes is worth adding to snac, feel free to. I think I can strongly recommend the first CSS change, as it fits with snac's aim to be fast and light-weight.

I’m trying some apps. Ice Cubes is nice, but doesn’t work with #snac and it’s open source, which is a great plus

Tusker is nice and works perfectly with snac, but doesn’t allow to quote post (which is ok, for snac, a bit less for Mastodn)

Toot! Is nice and funny. Worth investigating more.

Mona is clear and seems to be working with #snac too

Ivory looks interesting, but I should consider if I want to pay a monthly fee.

…I’ll have some fun…

Exactly one year ago, on 30th December 2024, I laid the foundation of FediMeteo.

I took a VM, installed FreeBSD, and set up the first jail to support Italy. The goal was to create a tool for my own use, support a few countries, and announce it.

Unexpectedly, the enthusiasm was incredible. That pushed me to keep going, support more countries and cities, and turn it into what it is today.

FediMeteo now supports 38 countries and 2,937 cities, with more than 7,700 followers in the Fediverse alone, not counting the many people who follow via RSS feeds or visit the web pages.

If you are curious to read the story and some technical details, you can find it here:
https://it-notes.dragas.net/2025/02/26/fedimeteo-how-a-tiny-freebsd-vps-became-a-global-weather-service-for-thousands/

Today is also Tuesday, a #ThankYouTuesday, so I want to say thanks to:

* OpenMeteo - @openmeteo - for providing accurate, high quality data, without which FediMeteo would be far less useful

* @grunfink - creator of snac, who made all of this possible using very few resources, on a 4 euro per month VM

* FreeBSD, which thanks to the efficiency of the OS and its jail implementation made it possible to run this service in a stable and efficient way with minimal effort

* FediFollows - @FediFollows - that periodically spreads the word about cities, countries, and the enthusiasm around the project

*All of you*, who suggested, encouraged, corrected, and celebrated this project

And forward toward supporting more countries and other interesting features already in the works.

Happy birthday, FediMeteo! 🎉

#FediMeteo #HappyBirthday #Meteo #Weather #FreeBSD #snac #snac2 #OpenMeteo #Fediverse

#Pixelfed, #Pleroma, #Snac and all the others .. can I please have a "local users only" visibility mode for posts? For server announcements and such?

Or does that already exist, and I'm just blind or st00pid or both?

Because I like torturing my Pentium Pro, I'm mentioning this one here. Just in case it should be of interest to anyone. Beware of the slightly nsfw second post in the thread. It's late, my boss is visiting, I had a few beers. It seemed like a good idea at the time. ;)

#RetroComputing #NetBSD #Fediverse #Snac #Snac2

1 ★ 0 ↺

Ltning » 🌐 2025-10-22
@ltning@weirdr.net

Been asked to post pics of this PPro/PIIOverDrive rig. Couple of shitty pics here; let me know if anyone wants actual details. :) Too tipsy to provide much right now..

Alt...

Picture of the CPU board, with two Pentium II OverDrive CPUs with retrofitted Noctua fans (for the noise..). Some cabling for the CF card, and more spaghetti for power, fans, etc.

Alt...

Picture of the other side of the CPU board, showing half of the system RAM (512MB in total), a SCSI controller, NIC, USB, VGA, SATA and Gravis Ultrasound and Sound Blaster AWE64 Gold cards.

Only when a post is boosted or replied to do I run the risk of my hot-babe CPU monitor turning nsfw. So better keep it boring, I guess.

And if it wasn't for crypto being too slow to actually work I'd be doing the same on the 386SX-class machine that I also have running NetBSD. But with a hyper-optimized SSH handshake taking over a minute, I have no hopes for 2k RSA signatures or any kind of TLS handshakes with remote instances happening in anywhere near the timeframe they would need to..

(In other news, the #snac instance on this poor Pentium Pro server is sweating hard whenever I post something. So let me know at @ltning@anduin.net if you have problems receiving/reading my posts. I've made some tweaks but it will be unavoidably detained for a while following each post, my apologies for that..)

#BIOS #POST #Retrocomputing

Alt...

Picture of BIOS during boot. It's a 1990 American Megatrends BIOS, for the TD60C board, BIOS version 2.42B. It shows a 20MHz CPU clock and 15872 KB RAM tested OK.

Until #snac starts doing work of course. Then I just sit back and wait.
#RunBSD #Patience

So..TLS aside, what is the most lightweight reverse proxy I can use instead of nginx in front of this thing? You know, in case I would like to move the instance from this beefy PPro to, say, a #486 or a #Nintendo Wii running #NetBSD? :)

#retrocomputing #BSD #stupididea

See also my main fediverse presence: @ltning@anduin.net

About this instance, at the time of writing:
- OS: #NetBSD 10
- Reverse proxy: nginx
- CPU: Dual Pentium Pro Overdrive, 333MHz
- RAM: 512MB EDO
- NIC: 3Com 100Mbit PCI NIC
- Storage: SATA 1.0 (CF and SSD)

#retrocomputing #butwhy