Path: news.eternal-september.org!eternal-september.org!feeder3.eternal-september.org!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: Bingo3331 <invalid@invalid.com>
Newsgroups: news.admin.hierarchies
Subject: Re: Proposal for the New Top-Level Hierarchy ai.* - Artificial  
 Intelligence
Date: 1 Apr 2025 17:26:09 GMT
Lines: 97
Message-ID: <m52lthFi9c9U1@mid.individual.net>
References: <m4u2dvFq8dlU1@mid.individual.net>
 <20250331194208.156dae62@ryz.dorfdsl.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Trace: individual.net uDTDFfhLbg3e7rCgNI3rmQIlZTs3aBS8bfTjFmMhrNuF9EqwRR
Cancel-Lock: sha1:CAISf0WOvZ3ATTZyrQ3TX0CoIjQ= sha256:FdlpPw7JfNzmMfAyy+88NsQeuqYdSLb3Z45d/t3warM=
User-Agent: PhoNews/3.13.3 (Android/14)
In-Reply-To: <20250331194208.156dae62@ryz.dorfdsl.de>

On 31/03/25 19:42, Marco Moock wrote:

>Are there reasons for not using comp.ai for English and maybe creating
>a group in it.* for Italian?
>
>I think creating a lot of groups isn't a good way to handle that.


Dear Marco Moock,

Thank you for your feedback on our `ai.*` proposal! We appreciate your
 thoughtful questions, and Corrado Roberto and I are happy to address them.
 Your points about leveraging existing hierarchies and avoiding
 over-proliferation of groups are well-taken, and we’d like to explain why
 we believe `ai.*` is the right path forward—while remaining open to your
 suggestions.

---

### **Why Not Just Use comp.ai.* for English and it.* for Italian?**
You’re right that `comp.ai.*` and `it.*` are established hierarchies that
 could host AI discussions, and we’ve considered them carefully. However,
 there are a few reasons we’re proposing `ai.*` instead:

1. **comp.ai.* is Stagnant**: While `comp.ai.*` exists for English-language
 AI topics, most of its groups—like `comp.ai.neural-nets` or
 `comp.ai.philosophy`—are virtually inactive. From what we’ve seen, they
 haven’t kept up with modern AI developments (e.g., ChatGPT, generative
 models). We’re not convinced that adding English posts there would revive
 them; it might just get lost in the noise. `ai.*` offers a fresh, focused
 space to capture today’s AI enthusiasm, starting with `ai.ita.*` and
 potentially expanding (e.g., `ai.eng.*`).

2. **it.* Limits Scalability**: Creating an Italian AI group like `it.ai` or
 `it.comp.ai` is a solid idea, and `it.*` is indeed active thanks to the
 Italian community. But nesting AI under `it.*` ties it to a national
 hierarchy, which works great for local topics but less so for a global
 field like AI. `ai.*` lets us start with `ai.ita.*` for Italians while
 leaving room for other languages (e.g., `ai.fr.*`, `ai.de.*`) without
 needing separate proposals for each. It’s a more unified, future-proof
 approach.

That said, we’re not ruling out synergy with `comp.ai.*` or `it.*`. We could
 crosspost between `ai.ita.general` and `it.comp` to kickstart activity, or
 even revive `comp.ai.*` as a parallel effort. What do you think about that
 as a bridge?

---

### **On Creating Many Groups**
We hear your concern about creating too many groups—fragmentation is a real
 risk, especially with Usenet’s declining traffic. Our goal isn’t to flood
 the network with empty spaces but to start with a manageable, targeted set
 under `ai.ita.*`. Here’s our reasoning:

- **Focused Scope**: The seven proposed groups (`ai.ita.general`,
 `ai.ita.chatgpt`, etc.) cover distinct, popular AI topics—general
 discussion, specific tools (ChatGPT, Grok, DeepSeek), and applications
 (image/video generation)—plus `ai.ita.stats` to monitor usage. They’re not
 arbitrary; they reflect what’s trending in AI today, which we hope will
 draw users.
- **Controlled Growth**: We’re not launching dozens of groups at once. These
 seven are a pilot to test demand. `ai.ita.stats` will track activity,
 letting us prune inactive ones or add new ones only if there’s real
 interest. It’s a data-driven approach to avoid sprawl.
- **Critical Mass**: A single group (e.g., `it.ai`) might struggle to build
 momentum, whereas a small cluster under `ai.ita.*` creates a visible “hub”
 that’s easier to promote and populate.

We’d love your take on this—would fewer groups (say, three or four) feel
 more sustainable to you? We’re flexible on the number if it helps win your
 support.

---

### **Why ai.* is Worth a Shot**
Marco, we share your desire to see Usenet thrive. AI is buzzing
 everywhere—X, Reddit, conferences—and Usenet risks missing out without a
 modern, dedicated space. `comp.ai.*` feels like a relic; `it.*` is great
 but narrow. `ai.*` is a bold move to signal that Usenet can evolve,
 starting with the Italian community and growing from there. Corrado’s ready
 to handle the tech side (server, peering, PGP controls), so it’s low-effort
 for other admins.

Could we convince you to back this as an experiment? Propagate `ai.ita.*`,
 watch the stats, and see if it takes off. If it does, Usenet wins; if not,
 we pivot. Your support could make the difference—any tweaks you’d suggest
 to feel good about it?

Looking forward to your thoughts!


-- 
*Posted from
  PhoNews Pro for Android V.3.13.3
  News.individual.net*