cross-posted from: https://discuss.online/post/47378103

• Streams can be watched at https://seagl.org/watch starting 9AM PST
• Schedule of talks and presentations at https://pretalx.seagl.org/2026/talk/
• Matrix conference chat available: https://seagl.org/attend/existing

Maybe the only conference in the USA that uniquely is made by, and for, the FOSS community. Completely open for anyone attending and offering presentations. Maybe the only tech event where, instead of Microsoft or Amazon, you'll see the Free Software Foundation and PostmarketOS in the expo hall.

cross-posted from: https://discuss.online/post/47378103

• Streams can be watched at https://seagl.org/watch starting 9AM PST
• Schedule of talks and presentations at https://pretalx.seagl.org/2026/talk/
• Matrix conference chat available: https://seagl.org/attend/existing

This might be the only conference in the USA that uniquely is made by, and for, the FOSS community. Completely open for anyone attending and offering presentations. Maybe the only tech event where, instead of Microsoft or Amazon, you'll only see the Free Software Foundation and PostmarketOS in the expo hall.

Wow, this is so awesome! You learn real skills, starting at the transistor level. Add the coding and run real applications: chess, doom, minecraft clones, java, etc. GIthub repos

TINY-32 is a full 32-bit RISC-V computer made of 93,338 transistors. It passes the official RISC-V test suite and runs real DOOM at full speed.  Fully open source.

• NES simulator in C
• Tiny Logic Doom

Goatcounter is so minimal that it takes a minute to wrap the brain around, but the good news is that it tracks all access anonymously, which is all I ever wanted (and why I simply have never made real use of Matomo over the years). It is the digital equivalent of a step counter, and acts like those counting clickers they use at concerts to track number of attendants.

It is good to confirm people are actually able to access tooling. That is all I need.

Fully migrated: learning about policy, config files, defining groups, autogroup settings, preauthkey registration, using tags in place of users and now working through MagicDNS.

Here is my post to their forum, because AI-assisted development is progressing much faster than the current scaffolding and contribution guidelines can keep up with. How can code review be improved for third party developers, especially when it comes to ephemeral AI reference?

See my post on their forum, which I hope is well received.

Here is my post to their forum, because AI-assisted development is progressing much faster than the current scaffolding and contribution guidelines can keep up with.

See my post on their forum, which I hope is well received.

Password is lemmy

• I find it funny that Vikunja has no ability to be customized visually.
• I also think it is funny that links shared when creating posts on Lemmy seem to be very difficult for users to find.

Over the last year I've been customizing my applications like Castopod and Dokuwiki, in order to make them easier to navigate by my users. I'm trying to build a sustainable setup where upgrades don't break things I've manually customized in a text editor and I don't waste hours reapplying changes. I'd rather invest time in doing it right this time.

This is my first time managing a self-hosted wiki long-term, so I want to establish good practices early... before I start telling everyone to join up. I also intend to share my findings with the larger Dokuwiki and Castopod projects, because I can see where I could submit some pull requests eventually.

Services are being run out of systemctl --user, so there are no containers involved.

Thanks for any advice!

I'd like to extend API access to a designated domain for listeners of Linux Prepper podcast, and others interested in experimenting as a decentralized community. Current wiki page of ideas is at https://wiki.livingcartoon.org/resources/xyz

Looking for suggestions and other input in making this an experimental success.