I say “easily” because it wouldn’t require a major effort on the scale of coreutils. It could just be a series of fancy automation scripts. It’ll take effort, but not the most intense of exercises.

I made a handful of them at an old job because we had a few specific tasks that we would regularly do, but not enough to commit it to memory. I just spent an afternoon here and there slapping together python scripts with just the options we would need and tossed it into /bin

The great thing about the core philosophy of unix is that you could easily do what you suggest and maintain compatibility with applications that rely on the traditional coreutils (Which is the major reason why no one will really suggest changing the traditional syntax. It’ll break way too much.).

Just build a series of applications that actively translates your “less ambiguous” commands into traditional syntax. I’ve done it for a number of things where the syntax is long and hard to remember.

In fact I think a “nuutilus” would actually be fairly well received for distributions that are more new user focused and a pretty worthwhile endeavor.

It’s definitely more intuitive but It would drive me insane having to type that all out.

My criticism is that it largely ignores the primary advantage of Fediverse services (Decentralizing services that are designed to operate Centrally), while mostly explaining what I’ve always considered to be the most pointless feature (Cross Service posting).

It’s a mildly neat feature if you want to centralize your entire social profile under one account (which is my security nightmare but you do you), but its not really fundamental to using federated services and its implementation can be inconsistent and confusing.

Maybe have a bunch of “Lemmy” (or whatever) nodes arranged in a circle, the same color, with the same icon, and connected to each other through the middle of the circle (not connecting to the “fediverse”, although I guess you could have a transparent “Lemmy” super imposed over it) Then have the users connected to each node. Or something…I’m on a bench and just broadly visualizing it.

The next trick is explaining the fault of centralized services in a graph.

Requiring someone to have an account on a federated instance would mitigate a fair amount of spam and ease moderation.

What would that solve that mandating accounts for a standard wiki wouldn’t?

Can you elaborate on “discoverability”? Finding individual subject wikis has never been a particular problem for me. Even ones that don’t use Fandom, provided they are at least active. Just googling “<insert subject> wikia” (I know. I can’t let it go) always gets me what I need.

Can’t say I see an advantage to universal accounts (I see more disadvantages), but if that’s the big selling point and people really want it. I’m not opposed to having it, i’ve just always treated it as a mild novelty I never use.

As for decentralization, it has already been solved by MediaWiki. Which is GPL and (can be) self-hosted.

What benefit would federating it bring?

The ability to self-host your own FOSS wiki already exists and has for over two decades. It’s called MediaWiki.

You could have federated accounts I guess but do editors on the Doctor Who wiki really need the ability to see posts on Mastadon or edit pages on the That 70’s Wiki?

I feel like in the future we’re gonna start seeing fediverse servers differentiate on feature sets.

Like one requires a subscription fee but pays for yearly audits by a respected auditor, or another offers spam-filtering, etc.

Well, sure I’d like to give it a look

Message Boards are fundamentally different and I don’t see a lot of value in federating them considering the big message board platform (phpBB) has 25 years of development and is GPL.

Message Boards are more elaborate versions of subreddits/communities. In all of those instances there is still a single entity that has “all the power in the forum”. You can join another lemmy server, but the admin of that community is still the admin, and the entity controlling the server that community is on likewise, controls the community.

I guess you could have a universal account that could be used across different message boards, but Personally I’d hate that.

I will spend an entire weekend ricing my desktop in just the right way.

Then I’ll notice that one of my main apps doesn’t adhere to the theming i’ve designed, or that <insert random condition here> will completely break my theming because <insert weird OS quirk here>, or If I change my wallpaper it will make my entire theme look like shit, or that my cool theme makes font unreadable on one app because it renders shit weird, or that I completely overlooked this one aspect of my workflow that my cool design fucks with.

Then I’ll just say fuck it and go back to using standard Gnome.

There’s an extension that lets me close and open windows with the Matrix Code Rain so I can pretend I’m cool n shit.

I respect the effort he’s put into right to repair, and agree (in general) with most of the points he makes about it.

But I also think he’s an asshole and we need a better voice for the RtR movement. I’ve seen him get into fights and strawman people on reddit as corporate shills just for calling his attitude abrasive.