Cool, thanks!

Is there a Github link?

“One of the biggest functions of blocking is giving women the ability to stop weird men from constantly making them uncomfortable and scared,” one user wrote. “So of course Elon had to change that.”

They buried the lede a bit there, but that’s pretty much it.

Lol I didn’t either.

MythTV?

That’s what I was thinking, but wasn’t sure enough to say beyond “give it a shot and see”.

There might be some savings to be had by enabling compression, though it would depend on what format the images are in to start with. If they’re already in a compressed format, it would probably just be a waste of CPU to try compressing them further at the filesystem level.

Not sure if a de-duplicating filesystem would help with that or not. Depends, I guess, on if there are similarities between the similar images at the block level.

Maybe try setting up a small, test ZFS pool, enabling de-dup, adding some similar images, and then checking the de-dupe rate? If that works, then you can plan a more permanent ZFS (or other filesystem that supports de-duplication) setup to hold your images.

Thanks! Wish I had more time to work on it lately, but life has been getting in the way.

Tesseract was originally kind-of a cross between Photon and Alexandrite, though it’s evolved separately from both since then. May still be close enough for your taste?

Github

!meshtastic@mander.xyz

If it ever happens, absolutely :)

Oh, yeah, I just like the T-Deck form factor. Was going to use Meshtastic as the base but the ESP32 itself would be the messenger (e.g. wouldn’t need the phone).

As long as it’ll still accept a charge and isn’t a spicy pillow, yeah, absolutely. I’ve never had great luck soldering onto those little pads but it’s certainly doable (though I’ll admit my soldering skills aren’t the greatest).

I’ve been wanting to play with Meshtastic for a while and was looking at using something like the LilyGo T-Deck with its blackberry-like keyboard to make cool little off-grid messengers for camping/hiking trips.

Is this for your Meshtastic board (from your other post)? If so, that’s a great up-cycle and should work well with the onboard charging.

I have a few I’ve saved for similar purpose, but I’m not sure about shipping them.

Like someone else said maybe check with vape shops / dispensaries in your area to see if they collect them for recycling.

I almost went with OPNsense (having previously used pfSense), but everything else was already on OpenWRT so I decided to keep things consistent. OPNsense is a solid choice, too.

The barracuda I have is basically an x64 board in a 1U half-depth case with two extra network adapters (3 total including the onboard one). I have two of them: one’s running OpenWRT (my router) and the other vanilla Debian.

So if my router one dies, I can just either pull the drive from it or restore a config backup to another suitable PC that has two NICs (or promote the second unit I have).

The config in openwrt is abstracted. So if the hardware and NICs are totally different, you might need to reconfigure the device names in the config so they’re referencing the right NICs, but everything else should “just work” (e.g. WAN and LAN are just arbitrary labels).

If going the route of a backup solution, is it feasible to install OpenWRT on all of my devices, with the expectation that I can do some sort of automated backups of all settings and configurations, and restore in case of a router dying?

That’s what I do. Every device runs OpenWRT except my ONT. Backing up is just a cron script that calls each one and pulls the config.

For my router, I ended up buying an old Barracuda LoadBalancer 340 and installing OpenWRT (it’s an x86 device so it was super easy). It’s a little over-powered for a router, but the price was right. It’s got more than enough spare resources to run some extra stuff, including Docker, so I’m probably going to throw my PiHole container on there since I haven’t been impressed with AdGuard Home (which is available in the repos).

And if you go for an old Barracuda unit like I did, the default BIOS password is bcndk1

Pretty much my thoughts (and experience) as well.

I was thinking it could be used as a kind of exposure therapy to help with that aversion. At least, I’d be willing to try it out for that purpose.