
We're introducing structured AI disclosure tiers to foster transparency, preserve human connection, and give you control over your reading experience.
We are working on revised DEV AI guidelines for the community to help ensure the most authentic content rises to the top. We will also be launching new features on DEV which put more weight on human curation by community leaders, to further help the best stuff rise to the top.
Human connection, authentic discussions, and direct peer-to-peer knowledge sharing remain the heart of our community. At the same time, people are using AI tools to help craft their posts, and to an extent there is allowance for autonomous posting by creatively developed bots — as long as it is done without deception, and we provide tools for authors and readers to navigate this to their desired intentions.
To bring transparency and nuance to how content is created and consumed, we’re introducing AI Disclosure on DEV. Disclosure has been part of our AI policy since we first wrote them.
Our AI policy was first crafted in 2024, with some small updates along the way. We will be making updates to this policy with this disclosure feature as a complement to how we can collectively work together as a community. With Hacktoberfest having a focus on open source AI, we see it as especially important that our tooling and policies are as up-to-date as possible for the benefit of the community and larger ecosystem.
When creating or editing an article, authors can now select an explicit AI disclosure tier:
We want to provide the right framework for different use cases:
Disclosure is not a loophole around our core community standards. Quality, original insight, and human accountability still matter.
Transparency is only step one. We are currently building Feed Preferences that will allow you to customize your reading experience—including options to reduce or filter out AI-assisted or autonomous posts from your home feed based on your personal preferences.
AI Content in Feed is now an option you can select from in your settings. The ways in which this will affect your feed exactly will be an evolution over time. Of course since our codebase is open source via Forem, you are welcome to peruse the implementation exactly.
Happy coding!
flutterDiscover how CubitSignalMixin and BlocSignalMixin allow any existing Flutter controller, domain repository, or enterprise class to gain full reactive state container capabilities without occupying its single inheritance slot.
googleappsscriptBreaking the Limits of GAS with Direct Cloud-to-Cloud Streaming in Persistent Linux...
flutterDiscover why Flutter state management is no longer an all-or-nothing choice. Explore how BlocSignal, Classic BLoC, and Riverpod now operate as first-class bidirectional peers at the Grand Central State Terminal.
kubernetesLearn how to troubleshoot and audit GKE Vertical Pod Autoscaler actions with structured decision logs in Cloud Logging.
kubernetesLearn how GKE VerticalPodAutoscaler (VPA) CPU Startup Boost cuts JVM cold starts and eliminates ongoing CPU waste using in-place Pod resizing.
aiIf you've built a website with AI recently, there is a good chance it looks familiar. Maybe you have...
Workflows from the Neura Market marketplace related to this Stable Diffusion resource