Hah, I can absolutely see myself doing this if we didnt keep our “baking” spices and related ingredients in a different cupboard.

If it were me and there was no way to have an additional drop installed from the exterior, I would still consider running a single cable through the living space to your desired location, as discreetly as possible.

It’s difficult to suggest exactly how to do so without pics or a floorplan, but I would try to match the wall or trim color and keep the cable tucked close to the floor and/or ceiling throughout the run.

Once in place, the cable will quickly disappear into your surroundings and you’ll be left with rock solid reliable networking.

I was recently one of those people. 🤦

Made the mistake of thinking French roast would be a nice and bold cuppa, so I bought a couple bags of beans at Costco… absolutely terrible coffee.

Classic theme ftw, and arguably the best version of the classic theme too.

Nice tin. We grind a 1L Mason jar’s worth at a time and use a French press. One jar lasts about 2 weeks and honestly, I can’t tell the difference between a fresh grind and a 2-week grind, regardless of bean used. I’m sure some would disagree :)

Depends on your power needs. My home server is an Intel NUC, so I’m able to keep it, the modem, router, and main switches running through most power outages with an APC 600VA UPS for about $80 USD.

I try to keep things simple and just use Markdown files for everything. I have a doc for each physical device, and another doc for each service/container running on the LAN.

I generally track hardware specs, upgrade paths, and software changelogs/todos as unsorted lists within these docs. It’s super portable and easily synced across devices via Syncthing.

You’re very welcome. For Markor, I wasn’t a fan of the default viewer theme, which is how I view most notes when on mobile, so I made some tweaks to improve its appearance…below is a screenshot:

If you want something similar, add the following under Settings > View mode:

• Open existing files in view mode: on (this may be default)
• Link color: #71aaff

And replace the <style>...</style> block under the inject -> head pop-up with the following CSS:

<style> 
html, body { 
  font-family: sans-serif-condensed;
  font-size: 110%;
  background: #0d1117; 
  color: #c9d1d9;
  margin: 0;
  padding: 0.5em;
}

a {
  color: 58a6ff;
  text-decoration: none;
}

h1, h2, h3, h4 {
  padding-bottom: 0.25em;
  border-bottom: 2px solid #222934;
}

hr {
  border: 2px solid #222934;
}

pre, code {
  color: #b5a5ee;
}
</style>

I write nearly everything in markdown. Like you, I don’t want databases, or other barriers that will complicate portability.

I just use my text editor of choice, usually VSCodium or vim on the desktop, and Syncthing to keep the notes synced across all of our devices.

On Android, I’ve been happily using the Markor markdown editor for years. I’ve tried several others but always return to its simplicity.

All of the above editors support opening folders in a tree view, so you can easily keep your notes sorted under a traditional folder structure and find what you when you need it.

Edit: Forgot to mention that Markor does have a dedicated to-do feature too, which also uses markdown.

We use markdown notes extensively. Everything is synced to our desktops and mobile devices with Syncthing. Markor editor for Android, and VSCodium/vim on the desktop. Works great for tech notes, medical info, shopping lists, recipes, etc.

I would love to see an ostree-based (immutable) Debian for both stable and unstable.

Aside from that, my nitpicks aren’t distro-oriented.

Perhaps more importantly, websites can determine which fonts are installed on your system (regardless of which you’re enforcing), making fingerprinting much easier.

A better alternative would be to separate the core open source app from any premium, proprietary add-on features, as the developer hinted at here.

As someone else pointed out, it’s difficult to agree that this app follows an open source model when the open source portion of it is essentially non-functional and requires the closed source components to be of any practical use. Until that separation occurs, this isn’t really open source; you’re trusting a stranger on the internet with your (or your client’s) network credentials.

Barring any similar apps, I’ll stick to my password manager and terminal.

The deal breaker for me is that it seems the low-level component that would interface with the shells (presumably managing credentials in some way) is closed source and off-repo. That’s a big red flag for me, no matter how benign the intention.

I appreciate the writeup and that you’ve taken the time to post about it here, however I am 100% leery of managing remote access or credentials using closed source software. I’ll definitely keep an eye on the project, but it’s a hard pass for me until the app is fully open source.

I hear Anna’s Archives is great for ebooks. I don’t do audiobooks, and can’t stand podcasts, but it sounds like a lot of good suggestions were made for those already.

Simple SMS, obtained from F-Droid, is probably the best universal option until the Fossify project adds the fork to their suite (assuming they do).

If you have the ability to toggle network access for your apps (GrapheneOS, etc.), Google Messages is a very solid SMS app that receives regular updates. I would normally only recommend FOSS apps, but many of those options are limited and/or dangerously outdated for SMS.

Relevant topics also missing from the survey:

• Choice of desktop operating system
• Choice of mobile platform and OS
• Use of email encryption
• Use of cloud storage
• Use and method of disk encryption

I too like to review changes between images, but I’m just as content to run rpm-ostree status and/or rpm-ostree db diff to see what exactly has changed.

You should be forced to reboot though? And if you don’t want to reboot, can’t you just do an --apply-live?

I’m hoping to eliminate the extra reboot each day that is usually necessary to activate the latest image. I know that a lot of this will depend on exactly when the image drops from the repos (versus when I shutdown a host), which is why I was looking for some general feedback from others who might have done the same thing…I didn’t know if it’d be worthwhile in the long run, but I guess there’s only one way to find out. As for the --apply-live, I use it on occasion but I don’t want to rely on it for system updates (if that’s even possible).

Thanks, yeah I’ve found a few articles already on running scripts at shutdown…something like this should do it (using Tony Walker’s update script), though I’ve not tested it yet:

/etc/systemd/system/silverblue-update-at-shutdown.service:

[Unit]
Description=Fedora Silverblue Update at Shutdown 
ConditionPathExists=/run/ostree-booted
DefaultDependencies=no
Before=shutdown.target

[Service]
Type=oneshot
ExecStart=/usr/local/bin/silverblue-update
TimeoutStartSec=0

[Install]
WantedBy=shutdown.target