Happy for them to be developing an app (which already appears to exist), but at ~20‰ with 16 days left… wouldn’t it be “better” to collaborate with existing apps like Pipepipe / Newpipe and direct those funds into the platform instead?

It’s a shame, because I tried to support them as long as I could, but I guess I out grew their content over time and stopped subscribing when I had a pile of unread magazines.

But thanks guys, it was a good mag

Yeah, but it’s hard work to make it look easy.

I made a video for work once, it was basically a recorded Teams call, but, good god, I was awful 🤭

Hadn’t thought about all the locale, etc… good point, thanks

Yeah… notes… they started about 50% of the way through building the system.

Now, my notes are great, but some of these devices are ~10 years old.

But, yep, I totally agree, notes are a damn good thing to have.

Not thought about bash history though, interesting point, but I think that only goes back a short duration?

Yeah, at least others are confirming what I had assumed, rather than everyone pointing me to a blindingly obvious tool that did it all for me!

Good point, not thought of that - thanks

Lucky you.

Yep, I’d seen some other videos of his, he does seem genuinely interested in passing on his knowledge

Ok, good point on not writing from scratch - which is what I had been doing for the first few… whixh is rewarding to learn how it works, but it is slow.

Thanks

Hmm, that’s not a bad shout actually…

I can fire up VMs to replicate the real system and maybe (depending on space) keep them as a testbed for future mods.

Thanks, good idea.

A combination of Logseq (what, why, how) and KeePass for IPs and passwords (obviously)… I use the heirarchy in Keepass to show a device and then the services on it and then their configs, ie

• Hypervisor1
  • VM1
    • root user details
    • that webUI details
  • VM2 (Etc)

I used to do Visio drawings, but they were always out of date.

Firstly, I agree with your main point.

Just an open thought: I wonder if zscalar are using settings in a heirarchy, ie if no env var is set, then check Gnome - just in case the user’s only making changes there…? Dunno…

Have a look at Vivaldi

According to their help page it’ll do what you want.

It’s just another calendar…

So, we have:

• Me
• Them
• Us
• House Stuff (ie bin day reminders)
  • I use this for Home Assistant
• Birthdays
  • I don’t recall at the moment, but an app used this for contact’s birthdays…

I then setup DavX to sync to Me and Us on my phone and Them and Us on their phone.

In Fossify Calendar it’s really easy to show /hide separate calendars as well as selecting the correct calendar when adding / editing events.

Definitely Radicale

We have separate calendars (ie we individually sync between our phones and other devices) plus joint calendars that we also sync…

On Android I use davx to sync and Fossify Calendar which allows me to see multiple calendars but only sounds reminders for my personal & joint appointments, not others.

On my laptops I’m currently usong Vivaldi’s built-in calendar and that’s working well for me.

Ah, ok if Tom Lawrence has made a video then I know it’ll work!

Thanks

Just a friendly reminder that RAID is not a backup…

Just consider if something accidentally overwrites some / all your files. This is a perfectly legit action and the checksums will happily match that new data, but your file(s) are gone…

This is exactly what I’m about to do (later this week when I visit their house)

I’ve been using syncthing for years, but any tips for the encryption?

I was going to use SendOnly at my end to ensure that the data at the other end is an exact mirror, but in that case, how would the restore work if it’s all encrypted?

Crowdsec will block external, public, IPs

Fail2Ban will block login attempts (ie from anywhere)

I have a similar setup with pfSense, pfBlockerNG, HAProxy, etc, but I keep F2B running on my DMZ server in case something is ever compromised as it’ll block / slow down anyone trying to move around the network.

Whatever you end up with

• test a restore
• consider how to deal with the source data being corrupted / ransomed / etc, ie multiple versions