Well, he is 66, and I hear average life expectancy is decreasing…

/s

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!

I like them both. Mastodon is great when I follow hashtags and the occasional person. I also like that I can follow Lemmy posters there. It means I can pay attention to individuals when I want.

Lemmy is great for threaded conversation. Mastodon can do this to a point, but it’s not a clean and navigable as Lemmy.

Imagine if I could subscribe to Mastodon hashtags within Lemmy!

A lot of folks are going to be sharing their device with others. How does that work?

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

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?

Google successfully did this to XMPP.

https://ploum.net/2023-06-23-how-to-kill-decentralised-networks.html

This is an interesting alternative to TCP/IP. I’ll need to dig into it a bit to have any real opinions.

It was a constant part of my Saturday mornings. It was stupid, but there was just enough lore to keep us all waiting for the next episode.

https://youtu.be/UagxpOQlSVM

I liked the small cameos in the maze battle scene. The characters from the 1980’s cartoon show made an appearance, even if they didn’t say anything.

Twitter’s super power was in being a public commons. Now that all tweets are effectively locked behind a login, it’s lost that power.

Same. I’ve seen lots of duplicate/repeat posts. Comments don’t seem to haves that problem for me. I’m using both Memmy and Mlem.

So when I login to an instance, am I sending my credentials through the wefwef.app server? Because that makes me nervous.

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.