We have been left with no other choice but to temporarily set the DM's to LEVEL 5. If you need further assistance you can always DM one of the admins. Thank you for your patience in this matter

Just curious, does everyone write your md files from scratch? Or do you ask claude to help you write, by giving it information? And can I say that the recommendation is to have md files lesser than 150 lines?

Sorry you all had to put up with the annoying bot. I think I have it fixed. Bot name Action Required

For a long time I was the slowest part of my own work. Everything ran through one chat. One conversation, one me. Good ideas queued up behind whatever I happened to be typing. The model in front of me was fast. I was the line it had to wait in. So I changed the job. Instead of doing the work, I direct it. I stay in one seat and advise, and the building happens in the background, in workers I hand tasks to and check on later. It runs whether I am at the desk or asleep. That last part is the honest claim, so let me be careful with it. This is not ten times faster, and nothing builds itself. I still decide what gets made, and I review every result. What changed is that I stopped being the single point everything has to pass through. The proof: I built part of the setup using the setup. I wrote a short spec for a tool I wanted, handed it to a background worker, and went to bed. In the morning the tool existed, its tests passed, and one question was waiting for me about a naming choice. I answered it. That was my whole night shift. I packaged it and open-sourced it. It is called ARI-OS. Repo: github.com/PUSHINGSQUARES/ARI-OS Install page: aris-space.com/applications/ari-os It is one loop, six steps, and you can learn it in an afternoon: 1. Brainstorm. Talk the idea out until it is a clear outcome, not a vague wish. 2. Plan. Turn that outcome into ordered steps. 3. Dispatch. Hand a step to a background worker and let it run on its own. 4. Watch. Glance at a small dashboard. See what is running and what is stuck. 5. Review. Read what came back. Keep it, or send it back with notes. 6. Ship. Merge the work that passed. You live on steps one, five and six, the judgement steps. The worker takes three and four. Step two is shared. The parts that need your taste keep you. The parts that do not stop waiting for you. If you are just getting started with Claude Code: it is pure Python, it installs with one command, it sits on top of your existing setup, and it is reversible. It distils four habits I lean on every day. A handoff layer, so a fresh session picks up cold without losing the thread. Background-first dispatch, so focused work runs while you stay free to steer. Spec-first thinking, so the work has a target before any code exists. And a memory, so the setup recalls what past sessions decided instead of guessing every time.

There seems to be an increasing number of bad actors playing in here, with all manner of nefarious reasons for joining and posting (or rather commenting). Private messages have now been blocked for lower than level 3 (I believe), But I am wondering if a $1 paywall to join the community might be a necessary solution to try and at least slow them down? I think that it might cause friction for a number of people who genuinely want to join and get value from the community, and maybe an answer could also be that you can join and see all the free content for free, but to be able to even comment and engage in the community you need to pay a minimal fee. I don't know the full community goals that @Jake Van Clief , @Matthew Creamer and the Admins have, but I do know that it's not only getting increasingly annoying, but also creating risk for the genuine community members who are here to get value out of all the discourse that happens here. What do you think?