This sounds like a good solution. Can you share how you did it?

Obligatory Babylon 5 reference:

https://youtu.be/VhD0hbGEDSU?si=uPD2Ff7oOtUti8NS

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.

Donald means something like “ruler of the world,” so not far off.

That’s one heck of a shower thought!

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.

Is there any way to get rss feeds directly from AP/Reuters any more?

If the Russians can’t succeed with numbers, will they escalate?

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.

Happy birthday to you
You belong in a zoo
You look like a monkey
And you smell like one too!

Just c/LemmyTellU. That way we can have

c/LemmyTellU about this new thing

c/LemmyTellU that something is happening

Flairs would be good to have, I agree. But aren’t flairs just a special case of hashtags? Could we implement it on top of the hashtag model?

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.