Languages English (en)
Users 502
Active users (last month) 70
Active users (last six months) 123
Characters per post (max) 500
Known instances 25,881
First sight Jan 1, 2024 UTC
Last successful check Aug 23, 2025 UTC
Noxious No
New No
Software Mastodon 4.3.8
Registrations Closed
Meta’s Threads moderation Threads is
suspended, according to the
Anti-Meta Fedi Pact list, but it’s currently impossible to verify it because this instance’s list of moderated instances is not accessible.
Short description
genart.social is a home on fedi for artists working in generative art and music spaces -- any kind of dynamically-created art.
Registration is currently invite-only.
Long description
genart.social
Welcome to genart.social, a space on the Fediverse for generative artists to connect and share their work. We use the term "generative" in its classic sense: not just AI, but any form of artistic expression generated from dynamic inputs. Our server is homed in Germany, and we welcome multilingual contributions from around the globe.
Let's collaborate to make fedi a more visually interesting place!
Banner art by @jesshewitt.
Please note that registration is currently by invitation only.
🏳️⚧️ 🏳️🌈 ✊🏿
Media Uploads
Media uploads should be 15MB or smaller. MP4s must be encoded with the H.264 codec, and at least one second long. Upload problems are almost always due to file size or unsupported codec.
GIFs will be mangled badly by Mastodon, and are not recommended here.
Use of captions for all posted media is strongly encouraged.
Generative AI Policy
Yes, we allow it, but: it's not popular on fedi, where there's a strong awareness of ethical lapses which occurred during AI's mass rollout.
We don't share the same "all AI is evil" zeal which is common here -- artists have been using machine learning (ML) in their work since the before times. Today being what it is, if you're using generative AI in your posts, you must say so. Consider adding the #aiart tag. Cite your models and data sources.
We encourage its use in art, but please do try go beyond the prompt.
Crypto Art Policy
Yes, we allow it, but: it's also not popular on fedi. You are welcome to share your art -- fedi just isn't a great place to "pump your bags".
We kindly request members to keep posts about crypto art low-key and consider adding the #nft tag.
Bots Policy
We welcome art bots, subject to good behavior as per our Server Rules.
Guide for Motion-Sensitive Fediverse Users
Eight Practical Steps to Address Motion Sensitivity
We recognize and respect that some users may experience sensitivity or discomfort with motion content on fedi. Our server prioritizes user safety, and our primary rule explicitly requires content warnings for stroboscopic (rapidly flashing) images that could trigger seizures or severe discomfort. While there are certainly cases where things slip through onto the timeline, not every animation is going to fall under the stroboscopic category. General motion, slight flickering, or animation, while potentially uncomfortable for some, is not classified as stroboscopic.
To assist users who are sensitive to general motion, we have compiled a list of practical steps that you can take to manage your experience effectively:
1. Disable Motion in Your Client
This is the easiest and least disruptive option. Most Mastodon clients provide accessibility settings to hide animated content. Enabling this feature can greatly enhance your browsing comfort and safety.
2. Mute or Block a User
If certain users regularly share content that affects you negatively, you have the option to mute or block their accounts, thus preventing their posts from appearing in your feed.
3. Block an Entire Server
If content from a particular server consistently causes discomfort, you can opt to block that server entirely, filtering out all its content from your experience.
If you are a server administrator or have the ability to influence moderation practices, you may consider these additional server-wide measures:
4. Mark a User’s Images as Sensitive (Server-wide)
This step ensures that posts from a specific user are always presented with a sensitivity warning, protecting your entire community from unexpected motion content.
5. Mark an Entire Server’s Images as Sensitive (Server-wide)
Applying this measure will ensure all content from the server in question is automatically flagged as sensitive, providing your community with an added layer of control.
6. Suspend a User (Server-wide)
In cases where a user repeatedly violates your community standards or significantly impacts user comfort, suspending their account is an effective administrative solution.
7. Defederate from an Entire Server
If necessary, severing federation with a particular server completely prevents all interactions and content exchanges, allowing your community to maintain its standards and safety. Hopefully it won't come to that, though.
We welcome good-faith reports against posts which genuinely should not have been published.
Not every problem needs a hammer
Instance rules
- Full-image strobing must be marked as sensitive and include a warning.
- If you use Generative AI in your art, you must say so.
- Sexually explicit or violent media must be marked as sensitive.
- Posting sexual content depicting minors is strictly prohibited.
- No racism, sexism, homophobia, transphobia, xenophobia, casteism, or any form of hate speech.
- No incitement of violence or promotion of violent ideologies.
- No harassment, dogpiling, or doxxing of other users.
- Do not share intentionally false or misleading information.
- No activity which is illegal in Germany or Colorado.
- If a violation is in question, admin provides a final call.
- Bonus rules for bots 🤖
Moderated instances [?]
Not available
Instances certainly moderating this instance [?]

Admin account Opted out of search engines indexing
Date of creation Not available
Display name Not available
Statistics
Last 12 weeks activity
Last checks (green: OK; red: KO)
8/16/25, 2:57:23 AM UTC | 8/17/25, 11:40:23 AM UTC | 8/18/25, 1:54:38 AM UTC | 8/19/25, 3:12:29 AM UTC | 8/20/25, 1:33:23 AM UTC | 8/21/25, 2:53:35 AM UTC | 8/22/25, 3:03:34 AM UTC | 8/23/25, 2:23:00 AM UTC |
Succesful checks: 600/600 (100%)