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.

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.

Been looking into resource constraining Kopia through systemd to prevent the Go binary from eating through too many resources. Anyone running a system like this?

All services have been migrated, now including the podcast. It was stressful, because Castopod has zero such documentation. I started with Dokuwiki (files and folders), then worked my way through migrating Flarum from MySQL to MariaDB. Spun up some new services via PostgreSQL and SQlite. Flarum at least gave me the experience of gaining some foundational understanding needed to then migrate Castopod via mysqldump, adjusting permissions, rewriting .htaccess to redirect to a simple migration.html page and eventually flip DNS after carefully adjust cron and tasks:list expected by php spark for Castopod.

Because it is always federating, with no supported method of disabling, I was terrified of it breaking. Obviously, it still could... but, it seems to be working.

I'm continuing to use an original Pi Zero and Pi Zero W, for breadboard experiments.

Got the old Samsung Galaxy A21 successfully running again as a home project. Besides pictures, wondering what else should be recovered through adb Android SDK.

Planning to test crDroid and lineageOS roms on it.

Setup listmonk and now wondering about suggestions for how to maintain a basic list and campaign. Wondering about a few things:

• Privacy. All I want to know is if people are actually able to read the posts.
• Any thoughts from others who've been managing their own lists / campaigns.
• Basic idea is to use for email and RSS to post updates on latest happenings, maybe once a month.

Just want this to be both successful and not annoying. 😄

Details at https://twtxt.dev/ and elsewhere. This has been in development since 2016. All you do is create a txt file in www or html and include info like

# nick        = username
# url         = https://example.com/posts.txt
# avatar      = https://example.com/avatar.png
# description = Describe this

to then begin posting using a command like like

echo -e "$(date -u +'%Y-%m-%dT%H:%M:%SZ')\tHello to all of you out there! >> posts.txt

There are various registries and places you can submit your user via curl to become more discoverable by others. Also tons of spin-offs that add support for fancier markdown and such, but haven't tried those yet.

Been working on building a wiki over a number of months, but realize it is a ton of work. My goals are:

• No Database, just files and folders for Dokuwiki
• Get the experience to feel accessible and fun for users.
• Make the wiki into something users can save locally and access offline.

The wiki coincides with various DIY and open source projects I'm experimenting with. Thought I'd share here, since this is about the extensions I'm actually using within Dokuwiki. Would love to add more, but just need them to work in daily use first.

Plugins in use:

• SMTP, so users receive their login credentials.
• Templator, for treating pages as templates for re-use.
• Include plugin, for using pages within pages to organize content.
• Open Document plugin - For export as odt
• Pagelist, which I'm still learning for organizing tables.
• Move plugin - for moving location of pages without breaking links.
• Wrap plugin, for centering images and code blocks.
• Tag, for adding tag browsing between page.
• Footer, for clarifying info displayed at bottom of pages.
• Catmenu, adds a clean, simple tree menu for the page being viewed.

Still in progress. Open to suggestions! Current idea is to offer a dark and light mode switch, plus get some fun icons. Want to introduce variations with visual glitches and such, for more of a cyberpunk aesthetic, that can be generated through a pipeline. This is is an excuse to learn a lot of little, technical things.

Picked up an ix500 scansnap and wondering about suggested workflows for going paperless. My intention is to scan a bunch of documents, but haven't delved deeply into how this will actually flow on the software level. I know I'll need to OCR the scanned documents, and my base setup is:

• Pi with SSD storage running compose version of Paperless-ngx to filesystem mounted folders.
  • Folders can also be accessed over Samba
• ix500 statically assigned over wifi as network scanner.
• A literal filing cabinet, for things I should keep physically.
• Ubuntu computer for browsing

I feel a bit overwhelmed, but am excited to get started. Will be scanning personal document, work docs, whatever else I need to digitize and recycle. All suggestions appreciated!

I find everyone using different services, so unsure how to best manage (and balance) concurrent access in Ubuntu/Debian to:

• Local network services
• Tailscale services from userA
• Tailscale services from userB
• Wireguard (OpenVPN also option) from userC
• Twingate from userD

Each user is wanting to share different services via VPN, and pressuring any to change their production setups to a different style of VPN is not going to happen.

• Management via software in Ubuntu
• Possibly up a routing device along the lines of OpenWrt or OpnSense.
  • Could even distribute such devices between these friends.

Thanks for all thoughts!

Didn't realize this was actually a John Cage composition.

Curious on suggestions for airtags, or similar, for tracking important things on flights or other cases where losing the specific item would be too much of a financial / sentimental loss. Anyone doing this from Linux, or from graphene? How is it?

Curious on what tools people would recommend, either from clients, locally or self-hosted.

• privatebin works nicely as a basic pastebin.
• stuffedanimalwar is just silly fun, with group drawing collaboration and chat that only exists in the active client session.

Thought I'd create a distinct thread from the previous one asking about daily use, because I really do want to hear more on people's pain points. Great to know people are generally sounding pretty positive in those posts who recently switched, but want to know your difficulties as well! This way old and new users can share their thoughts, hopefully to inspire a respectful discussion.

Curious on the experiences of those recently migrating to Linux from Windows 10, Intel-based MacOS, etc. How is it being on Linux? Anything surprise or frustrate you?