Fediverse

Objection! Hehe... No, wait. Really, I see a problem...

If registration are closed, mods would be exclusively from outside. And, since reports are not federated, this communities would be prone to difficulties for moderation. Unless reports are correctly federated, I don't think this is a good idea. And, even if you were to open registrations only for mods, we would have only moved the inconvenience to this (who wants to have so many accounts, really?)

There's also the problem with centralization of domain names under you. I don't know you, and perhaps you're well intended.. So, it's fine for the most part, let's just assume that's okay. Now, what happens if you had an accident or decided to go live in a farm? Without domain name renewals, etc. all communities would be in trouble. There's centralization in the shape of a single point of failure.

I can't see this happening even if the domain names are cool.

And, leaving disadvantages aside. What's the point on this? Can you name any advantage?? I agree that it would be more ordered and I like that. But it's quite subjective, and hardly anything huge to really break the inertia or status quo of things as they're now...

Thanks for the intentions. Let's focus on some new ideas, they'll come...

I was the only one who could create communities on them.

Typically the only one who can create magazines/communities are local users of the instance. With registration closed, that means only you (or the new instance owner) would be able to do this.

Though one can get around this with some bot magic ( lemmit.online had a magazine that was dedicated to new sub/magazine requests - once someone made the request, the bot would create and own the magazine but add the requestor as the moderator )

Do you intend to have open magazine creation on these instances or would that still be restricted to the owners of the consortium?

They are not being as used as I expected/hoped.

Have you considered it's because of this?:

My only requirement: these instances should remain closed for registrations and used only to create communities.

I wouldn't run an instance that didn't allow users to sign up as it would impede growth and uptake.

It also would have the interesting effect of pushing a lot of the load onto other instances, which doesn't seem true to the Fediverse spirit.

ITT: People who don't understand IAM or how to build a healthy federated structure. There should be identity services and instances just to host content separately. This way a spammer from a service won't de-federate content from everyone else and there could be easier moderation splitting the task between users and the comms.

lol I think you are right about this. You'll never get these lemmitors to see it i guess.

Looks more like you are interested in more influence power, and control for yourself.

What qualifies you to be in a leadership position that directly affects content control?

Your instances are not being used the way you wanted, so you propose structural and organizational changes that, suprise, benefit your administrative influence from your instances.

You're so focused on the details of your solution, you don't seem to be holding or acknowledging any objective perspectives.

Why?

That just locks communities off. Wh ich you could readily do before Lemmy, just host a forum. Discourse is a pretty damn cool software for it. Close registrations, close visibility, and allow users in on a per-user basis. That's also a lot how Tildes works, and I remember people here don't like that very much.