r/Arduino_AI rules, stats, and what to post

r/Arduino_AI is a community for makers, developers, and enthusiasts who work at the crossing point of Arduino hardware and artificial intelligence. The description says people come here to share ideas, collaborate on projects, and learn from one another. The rules give you a picture of who is actually in the room. There are people with decades of experience in embedded software and in machine learning and AI, and there are also complete beginners, because the community openly welcomes people who are just starting out and asks the experienced folks to be patient with them. So this is a learning and building space first. It is a place where someone shows a project, asks how to do something, or offers help to the person one step behind them.

There is one published rule here and it does a lot of work. It is called “Be Respectful in your Requests and Responses” and it covers both halves of any post you make. The respect half means treating people kindly, especially beginners asking basic questions, because the rule reminds everyone that we all learned this stuff through the kindness of knowledgeable strangers. The requests half is the one that matters most for a founder. The rule asks you to be realistic about the time and effort required of yourself and requested from others. The policy summary makes the consequence plain: posts and comments get removed if they are disrespectful or unrealistic about the time and effort demanded from other people. There is no published rule about promotion, links, or AI content, so the community has not stated a position on those. That means the single rule carries the full weight, and your post has to clear a respect bar and an effort bar at the same time.

The safest and best post here is a contribution that respects people's time. Show a real project that combines Arduino and AI, explain what you built, what worked, and what stumped you, and invite discussion. If you are a founder, the respectful move is to share the technical story of your product rather than the sales story. Post about the embedded challenge you solved, the model you squeezed onto the hardware, or the tradeoffs you faced, because that is exactly the kind of idea sharing the description invites. Questions are welcome too, but keep them scoped and realistic. Ask something a knowledgeable person can answer in a reasonable amount of effort, not something that asks strangers to build your product for you. And if you stick around to answer beginner questions, you earn goodwill fast, because the rule text makes patience with newcomers a core value of this place.

Two things get you removed here, and both come straight from the one rule. First, disrespect. If you are rude, dismissive, or impatient with anyone, especially a beginner asking a basic question, you are breaking the spirit of “Be Respectful in your Requests and Responses”. Second, unrealistic asks. If your post dumps a vague problem on strangers and expects them to design, debug, or build something for free, you are being unrealistic about the time and effort required of others, and the removal standard covers that directly. On the marketing side, there is no stated promotion rule, but a post that is all pitch and no contribution will read as disrespectful of everyone's time, which is the same failure in disguise. Do not treat this community as free consulting or as a billboard.

This is one of the few rule sets I have read that leads with gratitude for beginners, and it sets the whole tone of the room. The line about being glad we did not ask every question out loud made me smile, because it asks the experts to be patient rather than asking the new folks to be quiet. If your product touches tiny hardware running clever models, this could be a genuinely warm audience, as long as you show up as a builder and not a broadcaster.