Yes, particularly the variant distributed on a business-card sized CD rom. To be carried in your wallet for emergency use.

This coverage provides an example of what is sent, and it includes neither MACs nor HDD serial numbers.

https://ostechnix.com/manjaro-data-donor/

Immich has a whole set of end-to-end automated tests to ensure they don’t accidentally make public any URLs they went to be private:

https://github.com/immich-app/immich/tree/main/e2e/src/api/specs

As a popular open source project, that would be e glaring security hole.

Using this proxy puts the trust in a far less popular project with fewer eyeballs on it, and introduces new risks that the author’s Github account is hacked or there’s vulnerability in he supply chain of this docker container.

It’s also not true that you “never need to touch it again” . It’s based on Node whose security update expire every two years. New image should be built at least every two years to keep to update with the latest Node security updates, which have often been in their HTTP/HTTPS protocol implementations, so they affect a range of Node apps directly exposed to the internet.

Yes, there are broken uses of the HTTP protocol verbs where filtering to GET won’t work.

A simpler way to protect a private service with a reverse proxy is to only forward HTTP GET requests and only for specific paths.

It’s extremely difficult to attack a service with only GET requests.

The security of which URLS are accessible without authentication would be up to immich.

Although, If I have my own Amazon referral link in my blog post and they replace the referral code in their feed, I would not be happy about that.

They could be injecting their own ads or affiliate links into the content.

For example, if a post links to Amazon.

I have not looked at the source code.

Look at how Dynamic DNS supported. Does it require full access to the account-- dangerous-- by using your login credentials or an API token with full read/write access? Or does it over a very limited scope access that gives the Dynamic DNS tool precisely the access it needs to update a single DNS record-- much safer! The latter is what CloudDNS does.

There are two services involved. Domain registration and DNS. Most domain registrars now provide some free DNS service, with basic features. I monitor dozens of domains, and I can tell you that these free DNS services with registrars are most likely to have short DNS outages as well.

ClouDNS is a professional, high-quality DNS service and that does one thing well. As far as I can tell, they don’t do domain registration, so that will always be a separate service. One of the things that ClouDNS does well is making Dynamic DNS easier.

Domain.com sounds like a domain registrar. You would keep that service and point your name servers for the domain to the ClouDNS name servers.

ClouDNS makes DDNS easy for a low cost for 1-5 domains.

Fuzzel and Rofi are picker/launcher utilities.

More alternatives are compared here: https://mark.stosberg.com/fuzzel-a-great-dmenu-and-rofi-altenrative-for-wayland/

I built a console-only laptop once for financial reasons. I wanted something to travel with on a trip and was donated a laptop that, I think 20 MB of RAM after I upgraded it. I was able to run vim, perl and mutt was very tolerable performance.

I don’t think there’s really special tips. Pick a goal of some tasks to accomplish. Work towards them, discover the rough edges and find solutions for them. If you install everyone else’s favorite CLI apps, you can end up more than you need.

All that said, if I had the memory to run a GUI, I probably would have do so. But I wasn’t going to have a lot of time for web browsing and other laptop on that trip anyway.

A lot of the bindings are the same, because Helix was inspired in part by Vim.

Helix overall tries to make more consistent vocabulary and “nouns” and “verbs” in the keybindings, so there are some breaking changes.

Someone published a more “vim-like” set of keybindings for Helix: https://github.com/LGUG2Z/helix-vim

I started with that and then have slowly disabled a number of them as I come to appreciate the Helix defaults, and have realized that some of these vim-bindings are overriding other Helix bindings that I wanted.

A better out of the box experience-- fewer plugins required. More discussion here: https://urbanists.social/@markstos/112586854536602496

Anyone care to compare this with Helix?

I also switched to a trackball, The Kensington Expert.

I have also heard good things about the L-Trac.

https://www.amazon.com/X-keys-L-Trac-Red-Trackball-Mouse/dp/B06XWLCLGB?ref_=ast_sto_dp

Right. I’m glad there are options. Despite their flaws, web UIs for email are massively popular.

Despite all the other answers, I suspect Web Browser is the most popular. As web apps for email got better, development of desktop clients stalled.

Fast search through a lot mail takes some considerable resources to build, store and search an index, and web-based systems do that really well.

I’ve used about all of them over the years: Pine, Mutt, Thunderbird, Evolution, K-Mail and some others.

I eventually threw in the towel and use web UIs now. Fast, available everywhere and good keyboard support, especially when paired with a browser extension like Vimium.

ChromeOS. It’s relatively simple, secure and runs on older hardware.