Look into Single Sign-On services (SSO) like Authelia, Authentik, or KeyCloak. Most SSO tools do the sorts of things you’re looking for. Some will talk to the native UNIX user store. I do agree with the others, though: if you’re this far along, then it’s time to spin up LDAP and SSO, but this might be the same tool in your case.

Right now, I’m using Obsidian. I think I’d like to transition to keeping docs in a wiki, but I worry that it’s part of the self-hosted infrastructure. In other words, if the wiki’s down, I no longer have the docs that I need to repair the wiki.

Watch just the first minute of McCain’s concession speech. (Watch the whole thing if you like. It’s pretty good.)

I watched him shut down the boos about Obama at the beginning. He took this very seriously and wouldn’t allow the crowd to get out of line. It was well done, and a great example of statesmanship and fair play.

For just a moment then, I wondered if I had voted for the wrong man in voting for Obama, who was more of an unknown for me at the time. McCain acted very differently in the middle of good campaign, compared to the beginning and the end. I couldn’t support the policies, the attitude, or the man that I saw during the national campaign. Listening to John McCain’s concession speech that night, I remember thinking, "where was this person—this attitude—for the last few months? I might have voted for this person.” The party and the campaign forced him to become something that he wasn’t. If he had been allowed to be more authentic, I think that Obama would have had a narrower victory, if he had won at all.

You’re a poet, and you didn’t realize.

Synology has the best systems of their kind. I’d go with them for pre-made solutions. Their UI is simple enough for most folks to understand.

Backups. Backups. Backups. Focus on what you can reliably do. If you can’t make a service bulletproof, then maybe it’s not ready for everyday use.

Keep good notes. Notes tell both what you did and why you did it. Keep track of what problem you’re solving or what goal you’re working toward. All of this will help when you do look for a new IT provider. Use your notes to help the business define requirements for them.

30 years with Linux myself. Glad you’re here! Keep loving forward!

Local communities have a purpose. I live in Northwest Arkansas, a vibrant, slightly more liberal region of the state. I can envision a hyper local instance for all things NWA. For example, a community on trails and trail riding/hiking would focus on the area’s trail system instead of the general topic.

Now, I might want to subscribe to both the NWA trails community as well as the mote general purpose “global” trails community. So, having them distinct in some way is helpful.

Maybe it makes sense to have local communities that function as “satellites” of the global community of the same name. In this model, I could post to NWA trails and optionally choose to have my post broadcasted or cross-posted to the global community.

In the USENET era, we solved the problem with a hierarchical name space. Hierarchies are great, as long as everyone agrees on the structure. The problem is that most hierarchies are completely arbitrary. We would need a consensus group, like the Big-8, ICANN, or IETF that could manage the global community name space. This shouldn’t stop a competing group from standing up a separate, independent global namespace, though.

Maybe the ETA of the global namespace is past. Maybe there are better ways to achieve these goals today.