

Joplin has their own sync-server you can run as Docker container; free for personal use…


Joplin has their own sync-server you can run as Docker container; free for personal use…


For my own domains I’m using Migadu since they support unlimited domains per account. Quite happy with them…


Ah too bad, was worth a shot. Other than dissecting the KDE snapshot tool I have no other ideas. Good luck on your search…


I haven’t done this myself but maybe you can script something with OBS? It is made for screencapturing and it seems to work with Wayland according to the Arch Wiki.
I don’t know about AES67 but I’ve used Snapcast now for a few years and it works great. I use a central Mopidy service that streams to a few Snapcast clients connected to audio devices (not directly to speakers though). The clients run on normal PC hardware, Android and some on Pi’s with DAC’s from Hifiberry. The setup was very DIY but has been running very stable after that.


NFS is easy as long as you use very basic access control. When you want NFSv4 with Kerberos auth you’re entering a world of pain and tears.


How I read it is that they’ve reintroduced it in FF 139 and that you need to enable the third-party certificates to acces the client certificate in the Android cert. store. But the linked bugs in the later replies of my link mention a regression in FF 140+.
I do agree that this is still a horrible UX though. Sadly I don’t have the time currently to test it.


I was curious so I looked it up… But it should technically work on FF for Android, although there is a bug in the UI.
See:


This is only true for the connection security. With mTLS you can also authenticate to the webapplication you’re trying to reach. So consider your use-case between von/mtls.


If you’re really out of options you can just brute-force it:
# grep -r 'old.home.lab' /etc
Or any other dir with configs…


Hosting a Gitlab for work and for my private projects I agree. The CI/CD is excellent and I really like the way they handle issues and merge-requests. Gitlab is great but quite a beast, so throw some good CPU and fast storage at it.


It is a nice look into the switch from a perspective of a windows user. But since he is experimenting there is a also a lot of bad choices or wrong information.
He gripes about things not going smoothly while replacing his whole desktop environment (when was the last time you replaced your explorer.exe?).
And clamping to old ways of doing things. Which is understandable but would go a lot better with a little bit of guidance. Why force Chrome while Firefox was probably pre-installed or Chromium also works. Using Filezilla while Dolphin can probably do it in an integrated way. Using Notepad++ while Kate probably covers most of his use-cases.
This doesn’t invalidate his experiences but it does indicate a resistance to switch.
There is some valid criticisms as well though. The docking station that bugs out or KDE Connect that is confused. We can improve those things, but hardly force Logitech to bring their (horrible) software suite to Linux.
Maybe he should give it another few weeks to actually feel that while his old ways might not transfer over 1:1 the new ways give him a lot more power.
Hmm, the years are a bit faded but first install of Redhat in 1996-7 somewhere as a short experiment, then Slackware, SuSE, LFS, Gentoo, and since then lazy with Kubuntu… Might switch again soon with the Snap fiasco.
I always liked penguins and Tux… But that movie cemented penguins as my spirit animal :)
The BOFH and his PFY are still helping their users…


Try sunglasses? But maybe other souls can still be saved from evil…


Disadvantage: you’re now using a browser from the biggest spy ad-ware company and killed web heterogeneity.


For a moment I thought you literally meant a penguin herder, I would be so happy…
Oh certificates are so much fun and you have so many options. From fairly easy to mindboggling complex.
Your current solution is OK if you keep in mind security implications of distributing certs using scripts.
It is not entirely clear where you do your tls-termination but it sounds like that is the Caddy reverse proxy so that is where your certs should be.
Placing them in a location like
/etc/ssl/example_com/asfullchain.pemandprivkey.pemis probably easiest. Make sure access rights are appropriate. Then point Caddy at them and it should work. I have no experience with Caddy itself though. If Caddy runs in Docker be sure to map the certificates into the container.Mind that in this scenario the certificates are only on the Caddy server, connections from the reverse proxy to the services is unencrypted over http. You can’t easily use the LE certificates on the services itself without some ugly split-horizon DNS shenanigans.
Alternatively you can set up a PKI with certificates for your services behind the reverse-proxy for internal encryption and do public tls termination in the proxy with Let’s Encrypt.