Yes! Hyphens and “+” are also legal, and while most will accept a dash, many don’t allow ‘+’. But it’s explicitly allowed in the spec!

God, the French. My friend has two first names, two middle, and thankfully only one surname.

So she writes 4 names? Does she put her maiden and married names both in the “surname” field? Or middle and maiden together in the “middle name” field?

Then the first part is interpreted (in the US, anyway) as a middle name, not as part of the last name. I did run into a recently married woman who did that: dropped her middle name, moved her last to the middle, and used her spouse’s last name.

More commonly, places that don’t take hyphens tend to just run the two names together: Axel-Smith becomes AxelSmith.

Programmers can be really dumb.

There are a frightening number of systems that don’t allow “-”, which isn’t even an edge case. A lot of people - mostly women - hyphenate their last names on marriage, rather than throw their old name away. My wife did. She legally changed her name when she came of age, and when we met and married years later she said, “I paid for money for my name; I’m not letting it go.” (Note: I wasn’t pressuring her to take my name.) So she hyphenated it, and has come to regret the decision. She says she should have switched, or not, but the hyphen causes problems everywhere. It’s not a legal character in a lot of systems, including some government systems.

Yeah, I use systemd for the self-host stuff, but you should be able to use docker-compose files with podman-compose with no, or only minor, changes. Theoretically. If you’re comfortable with compose, you may have more luck. I didn’t have a lot of experience with docker-compose, and so when there’s hiccups I tend to just give up and do it manually, because it works just fine that way, too, and it’s easier (for me).

I started with rootless podman when I set up All My Things, and I have never had an issue with either maintaining or running it. Most Docker instructions are transposable, except that podman doesn’t assume everything lives as dockerhub and you always have to specify the host. I’ve run into a couple of edge cases where arguments are not 1:1 and I’ve had to dig to figure out what the argument is on podman. I don’t know if I’m actually more secure, but I feel more secure, and I really like not having the docker service running as root in the background. All in all, I think my experience with rootless podman has been better than my experience with docker, but at this point, I’ve had far more experience with podman.

Podman-compose gives me indigestion, but docker-compose didn’t exist or wasn’t yet common back when I used docker; and by the time I was setting up a homelab, I’d already settled on podman. So I just don’t use it most of the time, and wire things up by hand when necessary. Again, I don’t know whether that’s just me, or if podman-compose is more flaky than docker-compose. Podman-compose is certainly much younger and less battle-tested. So is podman but, as I said, I’ve been happy with it.

I really like running containers as separate users without that daemon - I can’t even remember what about the daemon was causing me grief; I think it may have been the fact that it was always running and consuming resources, even when I wasn’t running a container, which isn’t a consideration for a homelab. However, I’d rather deeply know one tool than kind of know two that do the same thing, and since I run containers in several different situations, using podman everywhere allows me to exploit the intimacy I wouldn’t have if I were using docker in some places and podman in others.

2¢

Location services in Android are in-phone, and they’re definitely accurate and reporting to Google. I only clarified that your cell provider probably can’t locate you using triangulation via your cell Signal. Turn data off, and you’re fine; otherwise, Google is tracking you - and from what I’ve read, even if you have location services turned off.

They can’t, tho. There are two reasons for this.

Geolocating with cell towers requires trilateration, and needs special hardware on the cell towers. Companies used to install this hardware for emergency services, but stopped doing so as soon as they legally could as it’s very expensive. Cell towers can’t do triangulation by themselves as it requires even more expensive hardware to measure angles; trilateration doesn’t work without special equipment because wave propegation delays between the cellular antenna and the computers recording the signal are big enough to utterly throw off any estimate.

An additional factor in making trilateration (or even triangulation, in rural cases where they did sometimes install triangulation antenna arrays on the towers) is that, since the UMTS standard, cell chips work really hard to minimize their radio signal strength. They find the closest antenna and then reduce their power until they can just barely talk to the tower; and except in certain cases they only talk to one tower at a time. This means that, at any given point, only one tower is responsible for handling traffic for the phone, and for triangulation you need 3. In addition to saving battery power, it saves the cell companies money, because of traffic congestion: a single tower can only handle so much traffic, and they have to put in more antennas and computers if the mobile density gets too high.

The reason phones can use cellular signal to improve accuracy is because each phone can do its own triangulation, although it’s still not great and can be impossible because of power attenuation (being able to see only one tower - or maybe two - at a time); this is why Google and Apple use WiFi signals to improve accuracy, and why in-phone triangulation isn’t good enough: in any sufficiently dense urban or suburban environment, the combined informal of all the WiFi routers the phone can see, and the cell towers it can hear, can be enough to give a good, accurate position without having to turn on the GPS chip, obtain a satellite fix (which may be impossible indoors) and suck down power. But this is all done inside and from the phone - this isn’t something cell carriers can do themselves most of the time. Your phone has to send its location out somewhere.

TL;DR: Cell carriers usually can’t locate you with any real accuracy, without the help of your phone actively reporting its calculated location. This is largely because it’s very expensive for carriers to install the necessary hardware to get any accuracy of more than hundreds of meters; they are loath to spend that money, and legislation requiring them to do so no longer exists, or is no longer enforced.

Source: me. I worked for several years in a company that made all of the expensive equipment - hardware and software - and sold it to The Big Three carriers in the US. We also paid lobbyists to ensure that there were laws requiring cell providers to be able to locate phones for emergency services. We sent a bunch of our people and equipment to NYC on 9/11 and helped locate phones. I have no doubt law enforcement also used the capability, but that was between the cops and the cell providers. I know companies stopped doing this because we owned all of the patents on the technology and ruthlessly and successfully prosecuted the only one or two competitors in the market, and yet we still were going out of business at the end as, one by one, cell companies found ways to argue out of buying, installing, and maintaining all of this equipment. In the end, the competitors we couldn’t beat were Google and Apple, and the cell phones themselves.

For my CLI homies, there’s syncedlyrics.

Be advised: several Subsonic servers (including gonic and Navidrome) do not support lyric files unless they’re embedded, and syncedlyrics will only put the lyrics in .lrc files. So getting lyrics in clients can be a two-step process: download the .lrc’s, then run a script to embed them in the song files. I’ve seen a script to do the latter, but I haven’t tried it. I’ll send a patch to gonic to read lrc files, during the Christmas holiday most likely.

You want Upspin. I want Upspin. But Upspin never went anywhere (it’s at least 7 years old… ever heard of it?), and I personally believe that it was because it’s a royal PITA to set up, and because the tutorial had instructions that expected you to be using GCS. If you wanted to do everything on your LAN, it was even harder.

It’s got all the of the features you mention, and it’s really the only system that does what it does; I really did try in the early days to get it running, and failed. It still has the caveat:

Upspin has rough edges, and is not yet suitable for non-technical users.

and, at 7 years old, if it hasn’t gotten anywhere yet, I think it never will. Commits trickle in, but there’s really no significant progress in usability.

Read the mission statement. It’s glorious. And then wallow in despair that nothing else does this, and it’s a zombie project.

Seconded. OP, if you can write Markdown, Hugo will turn it into a website.

I think Android updates intentionally made the Pixel C slower. It was a noticeable process, up to the point they stopped supporting it. I’d downgrade to an earlier version, but there’s such poor support in Lineage, I’m barely able to run the version that’s on there now.

Such a shame, because it’s still an amazingly beautiful device.

I’m 100% with you. I want a Light Phone with a changeable battery and the ability to run 4 non-standard phone apps that I need to have mobile: OSMAnd, Home Assistant, Gadget Bridge, and Jami. Assuming it has a phone, calculator, calendar, notes, and address book - the bare-bones phone functions - everything else I use on my phone is literally something I can do probably more easily on my laptop, and is nothing I need to be able to do while out and about. If it did that, I would probably never upgrade; my upgrade cycle is on the order of every 4 years or so as is, but if you took off all of the other crap, I’d use my phone less and upgrade less often.

The main issue with phones like the Light Phone is that there are those apps that need to be mobile, and they often aren’t available there.

ntfy is in the app store, so you don’t have you side load it. I don’t know how many iOS apps use ntfy, but many Android OSS apps will ask you over which notification system you want to work.

I was just clarifying that this isn’t one of the XKCD proliferation cases. Apple and Google’s push notifications are proprietary and give them full access to your notifications. Unified Push is the OSS alternative, and this KDE enhancement doesn’t createa another one: it uses the defacto standard OSS push notification specification.

The fact that ntfy is in the Apple app store makes me suspect there must be some number of iOS apps that can be configured to use Unified Push.

since all apps are designed to run well on budget phones from 5 years ago, there’s no reason to upgrade.

5 years, maybe, but any more is stretching it. And not getting system upgrades anymore is problematic. Unless you own a particular model of phone, de-Googled Android can be hard to come by.

For example, I have a 7-year old Pixel C. By the time Google stopped using system updates for it, I wasn’t wanting them as every release made the device slower and more unstable. After some effort, I was finally able to install a version of Lineage, which itself has problems including no updates in years. There’s a lot of software that is incompatible with my device, both from Aurora and FDroid.

Android isn’t Linux; Google doesn’t care about maintaining backward compatability on old devices, much less performance, and there’s no army of engineers making sure it is because there’s a served running in walled-up closet no one can find.

Google deprecates features and ABIs in Android, apps update and suddenly aren’t backwards compatible.

5 years, maybe. The entire industry is addicted to users upgrading their phones, and everyone gets a piece of that pie. There’s no actors, except perhaps app developers, who have any interest in keeping old phones running. Telecoms upgrade their wireless network - the internet connection in my 8 y/o car, and half its navigation features, died the day AT&T decided to stop supporting 3G; Phone makers make no money if you don’t buy new phones; and maintaining backwards compatibility costs Google money which they’d rather siphon off to shareholders.

Plus, I had gotten to a place where my tiling WM, tmux, terminal tabs, and vim tabs were all competing for keyboard shortcuts, and it was driving me crazy.

I admit, this is so bad that occasionally - and especially if I make the mistake of stopping to think about it - my brain freezes and I can’t remember the chord for a few second. What helped immensely was first kmonad, then Kanata, and finally a QMK keyboard. I use exactly the same keys for navigation, create, delete, etc operations, and only vary the layer key - WM under my pinky, tmux under my index finger. Helix has it’s own bindings and ways of managing windows that are different enough as to not really confuse me, and I don’t use terminal tabs at all, so it’s really only WM and tmux. But, yeah: a Helix split window, in a split tmux tab, in a split herbstluftwm window can occasionally get me stuck for a few second as I unbox all the layers.

I meant the server can deliver notifications via ntfy:

https://docs.ntfy.sh/examples/#home-assistant

Yeah, I don’t think the mobile app communicates with the server over anything but the web API.

I use tmux for anything I want to be long-lived. Displays, terminals, and WMs, all crash far more often than tmux. I’ve never once had tmux crash on me; at this point, I’m not sure that it’s possible for it to crash (only half-joking).

This is a lot like what I do. Where possible, my apps are TUIs, so terminals dominate. At any given point I have 4 tmux sessions with around 6 tabs in each. I haven’t refined that, though, because my editor (Helix) also has window support and many editing tasks (yank/paste) are easier with Helix windows that with multiple helix sessions running in different tmux tabs. This works best with full-screen terminals, and I find myself closing tmux panels to open helix windows… I need to refine this.

A few apps are GUI. Browsers, PDF viewers, graphics editors. Those are all full-screen.

How do you use the sliding feature this way, though, and how is it better than just having separate desktops? Do you use multiple displays, or only one?