I gave up with boxes many years ago as it would not restore vms from snapshot reliably, something I use a lot.

I’d like to say neovim but if notepad++ is too complicated then neovim definately is. There are ‘distributions’ that give you a setup ready to go e.g. Lazyvim but you’re still going to have to fiddle with it sometimes.

https://www.lazyvim.org/

I don’t think Lazyvim has any ai features out of the box.

If you are at all curious the ‘Lazyvim for Ambitious Developers’ book is a great way in and easy to skim through. Here’s the chapter on ai which proves you have to turn it on to enable it:

https://lazyvim-ambitious-devs.phillips.codes/course/chapter-16/

I can’t say for sure if the developers of neovim are using ai themselves for the codebase, I suspect they might be as they have made positive statements on it in the past. Love to hear if someone can confirm or not.

I like the idea as BASH is available everywhere but has terrible gotchas in its syntax plus at times is unreadable.

When I did some moderately complicated amber scripts I hit bugs. Also still some important features are missing.

So I’m keeping an eye on it but it’s definately not ready for anything serious yet.

I am also watching https://oils.pub/ and hoping one or both of these projects succeed.

You’ve made a great start. How much further you go depends on your needs and threat model.

Rsync is ok as a start but there are dedicated backup tools that will give you access to your files at any point in time. This is important if you delete a file and later need it back after an rsync has already run and deleted it remotely too.

Rsync will not encrypt your backups. If a burglar takes your Pi will they have easy access to all your files too?

With rsync+ssh you are also vulnerable to either yourself (more likely) or a rogue process on your own machine deleting the files over ssh (e.g. ransomware attack).

The answer to that is append-only backups. A backup tool like restic has a backend you can host that does exactly this:

The --append-only mode allows creation of new backups but prevents deletion and modification of existing backups. This can be useful when backing up systems that have a potential of being hacked.

https://github.com/restic/rest-server

Take a look at restic to see what else you gain from switching to a dedicated tool versus rsync:

https://github.com/restic/restic#design-principles

There are others too such as borg.

Ah right, I forgot about the different editions! Been on GNOME for so long.

X11 was completely removed in Fedora 43 I believe

https://fedoraproject.org/wiki/Changes/WaylandOnlyGNOME#Wayland-only_GNOME

It could if you/future owner ever need to re-enable it:

The trouble is not your present boot; it’s your future boot. If your older PC’s firmware never gets the 2023 keys, and the rest of the world starts assuming those keys exist, you can end up stuck in a weird limbo. While your existing Linux install will still boot, a new or updated distro won’t.

Testing now will help diagnose future problems.

https://www.zdnet.com/article/aspirin-for-linuxs-microsofts-secure-boot-headache/

I’m not familiar with Pikapods but Monica v4 has trouble with notifications. First you need to ensure it’s been configured right to even send a test email, this can be triggered with a command if you have access:

php artisan monica:test-email

Various Monica environment variables must be set to configure this, it should be in the docs somewhere if not I can fish my config out for you.

Even once that’s working you’ll need Monica to run its regular jobs for sending notifications, there’s config for that too. Finally the code has bugs and will often miss reminders in my experience. There are some open bugs still on this and I guess the devs have moved onto their rewritten version (chandler):

https://github.com/monicahq/monica/issues/5681

We’re also making it possible to add alt text for profile pictures and headers now, making your profile more accessible for blind and visually impaired users.

That’s good!

Ha! I sound keen like an AI cause I was thinking about exactly this problem when I saw your post and have been continuing to research.

The GNOME keyring does not defend against rogue processes for now. However KDE wallet can prompt a user before access (I’ve not tried it):

https://docs.kde.org/stable_kf6/en/kwalletmanager/kwalletmanager/wallet-access-control.html

…this seems a fair bit safer, presuming it works.

Some hints here:

https://wiki.archlinux.org/title/GNOME/Keyring#PAM_step

• Alternatively, if using GDM and LUKS, GDM can unlock your keyring if it matches your LUKS password. For this to work, you need to use the systemd init in your mkinitcpio.conf as well as the appropriate kernel parameters, and you should make sure that your system’s real-time clock is set to UTC rather than local time (see [2]). See [3] for more details.

When using a display manager, the keyring works out of the box for most cases. GDM, LightDM, LXDM, and SDDM already have the necessary PAM configuration. For a display manager that does not automatically unlock the keyring edit the appropriate file instead of /etc/pam.d/login as mentioned below.

I think you are absolutely right to examine whether your system defaults to too much convenience versus security for your threat model. For GNOME keyring:

Any application can easily read any secret if the keyring is unlocked. And, if a user is logged in, then the login/default collection is unlocked. Available D-Bus protection mechanisms (involving the busconfig and policy XML elements) are not used by default and would be easy to bypass anyway.

The GNOME project disagrees with this vulnerability report because, according to their stated security model, untrusted applications must not be allowed to communicate with the secret service.

Applications sandboxed via Flatpak only have filtered access to the session bus.

https://wiki.archlinux.org/title/GNOME/Keyring#Security

So while flatpaks that play the game are ok everything else is on trust. For the average user perhaps this is the right balance, though your Signal example suggests it’s too lax for anyone nowadays.

I would like to see system secrets protected however they are accessed, not just for flatpaks.

F-droid themselves gave an update in April:

https://f-droid.org/en/2026/04/03/twif.html

If you’ve been holding off updating Syncthing-Fork we have two pieces of news for you. First, the original dev continues to collaborate still, we know this was a pain point back then. Second, we’ve just added BasicSync, A simple app for running Syncthing, which just controls Syncthing’s running behaviour as hands off as possible, while the original service hums in the background.

So it seems since the handover things have settled but there is also a new fork which takes a more bare-bones approach.

Thanks for that info. I did some more digging but could find no definitive statement that Disconnect the extension is completely redundant in FF. In fact with FF’s ‘enhanced tracking protection’ on I can see that the Disconnect extension STILL reports it is blocking domains that presumably FF has missed. The mystery continues.

Grateful the SFC has got users’ backs!

From the github if you were wondering:

Free, open-source, self-hosted wardrobe organizer. Catalog clothes, build outfits, PWA. Docker one-liner deploy.

I mention https://lemmy.ca/c/linuxphones in case you’ve not found it already. It’s not like an authoritive, central forum where everyone goes but maybe it’s a start.

More than one it seems:

https://forum.typst.app/t/tinymist-vs-typst-vim-vs-typst-preview-nvim/1775/7

Rick Astley’s birthday is 6th Feb 1966, just saying

Hello

Somebody developed a Home Assistant integration for monitoring and managing sourdough starters