informapirata

@Jaye_xP

> @Jaye_xP said: > > is there a age limit for this site?

The Website is available only to individuals who are at least 13 years old.

PS: I’m adding a small, colorful note I added to an Italian Mastodon instance I manage. The age policy is explained like this:

> Age Policy: The Fediverse is anonymous, and we don't want to know your age, but YOU CANNOT JOIN THIS SERVER IF YOU ARE UNDER 16, and if, in our sole discretion, you appear under 16, we will suspend your account.

I can afford to do this because the rules of my instance already prohibit all content that might be problematic for a child, but the point is that if you’re a smart child, then you can pretend to be an adult and no one will notice. But if, as soon as you interact with others, you show off your age, then I’ll kick you out.

Similarly, if you’re in your sixties and display the maturity of a child, I’ll kick you out even more willingly! :grin:

julian great!

Hi julian , and sorry for trying to resurrect this (somewhat old) thread I happened to read. When you said to hamiller@forum.wedistribute.org

> “I should probably allow categories to track hashtag usage, even if it’s local, given how hashtags work.”

I thought this was now possible. In fact, I thought this was exactly what happens to your “General Discussion” category on Activitypub.space.

But then I looked in the settings of my federated NodeBB instance, and maybe it’s not as I thought. So, I wonder (and ask you): how do you manage to aggregate “general discussion” threads? Is there an automatic way, or do you do it manually with “move thread”?

This is an excellent idea, as demonstrated by the fact that many self-created communities (≈categories) on Lemmy have achieved significant global success. However, Lemmy’s implementation is unsatisfactory and needs to be adjusted. I am the administrator of a Lemmy instance as well as a NodeBB instance, and I must admit that at the height of Lemmy’s development, we never allowed autonomous community creation. This was due to some issues that arose with mastodon when homonymous communities and users existed. It was also because it was impossible to implement an approval process or ensure that the quality of the communities met the instance’s standards. For this reason, the process for creating communities by users consisted of a request from the registered user and a creation reserved for administrators.

What I would like to see in NodeBB is the ability to create communities, but keep them in a sort of “limbo,” a “section” where new communities remain until they reach acceptable quality levels for the instance’s standards.

This is in addition to the entire user credit system, which I imagine could also be set up to achieve a suitable score for building a community.

Perhaps I’m asking too much, but NodeBB’s development has been so impressive so far that I wouldn’t be surprised if you could implement a feature like this.