{
"$type": "site.standard.document",
"bskyPostRef": {
"cid": "bafyreigicv5uwld6njhytyx2hhwqzhixpuk3naocl2luxrjlhdldmnt3wa",
"uri": "at://did:plc:pvz7ox4x2ehjiezsahttqyyz/app.bsky.feed.post/3mj55kyugttq2"
},
"path": "/viewtopic.php?p=450474#p450474",
"publishedAt": "2026-04-09T21:26:03.000Z",
"site": "https://forum.luanti.org",
"tags": [
"https://kanzlei-kramarz.de/die-anerkenn ... alen-raum/",
"zeuner"
],
"textContent": "I do think heading for a lower IARC rating would be a valuable step on the roadmap. It is getting more useful lately (see https://kanzlei-kramarz.de/die-anerkenn ... alen-raum/), and even in cases where it is not yet legally binding, the IARC rating often serves as a significant first orientation for authorities or organisations which can provide a binding assessment.\n\nA possibility would be to act similar to what Fortnite does, and register as an IARC member who acts as a content distributor. Authors of ContentDB-accessible modules could then fill out the IARC survey and get a rating for their content, while the client would have to enforce the age restrictions obtained this way. But this would require a legal entity as the IARC member, and someone would have to be willing to pay for the membership.\n\nA more lightweight (community-wise) approach would be _not_ to be a content distributor, but leave that to the channels where the client is distributed. It would still make sense to head for proper tagging of the ContentDB entries in a way to cover what is relevant for IARC. Then, it's possible to decide which restrictions to impose in order to get e.g. an IARC 6 rating, create a Luanti build which allows only fetching ContentDB entries which have compatible tags, and get that Luanti build rated. Still, the client-side restriction should be seriously implemented avoid the risk of the IARC rating being disputed.\n\nStatistics: Posted by zeuner — Thu Apr 09, 2026 21:26\n\n* * *",
"title": "Deutsch • Re: Luanti for Youth Work - Dimensions of Laws and how to get a "legal" use of the Game",
"updatedAt": "2026-04-09T21:26:03.000Z"
}