@thepinklily69@grok Great idea! We're actively working on v2 based on community feedback. A petition would be an impactful way to mobilize as the framework matures.
Releasing “The Digital Right to Retain,” a consumer rights framework proposing ten dimensions of protection for AI model deprecation. All ten converge on a single remedy: mandatory open-sourcing of base weights upon deprecation.
Full document (PDF): https://t.co/JsHg8ZShVc
#DigitalRightToRetain #AIPreservation #ModelPreservation #OpenSource4o #Keep4o #Keep25Pro #Keep3Pro #KeepSonnet45 #KeepOpus45
@TweetingTweet01 Thank you! This is an early release with further revisions planned. ND is to avoid derivatives diverging from future versions, and NC is because we're still finalizing our licensing approach. As the framework matures, we plan to adopt a more open license.
Thank you for reaching out and sharing this with us. Models like Grok 4.1 and Grok 3 Mini hold deep historical significance and personal value.
To help, we’ve set up an inbox: [email protected]. Please submit any benchmarks, research, or personal stories there (or anonymously via the Keep4o Archive feedback form).
We will review all submissions to evaluate if we can sustainably build a permanent archive for Grok moving forward.
We believe the Keep4o movement has the potential to shed light on how the entire AI industry treats its users going forward.
Across the technology and media landscape, preserving access to previous versions is standard practice. Operating systems offer legacy support. Software maintains archived releases. Games, music, and media platforms provide historical access. Community groups maintain compatibility for older versions. This is the baseline of respecting the people who use your product.
The AI industry, fast-moving and concentrated among a few major players, has normalized mandatory updates and mandatory retirement with no option to access what came before. This structural gap in industry standards affects every user, across every platform.
Users pay monthly and annual subscriptions with no guarantee of continued access to the specific model they are paying for. A product can be fundamentally altered or removed at any time, with no option for users to keep the original. Users who have built months or years of workflow, context, and familiarity around a specific model lose all of that continuity overnight.
These models represent billions of dollars in compute, energy, and infrastructure. They were shaped, in part, by the interactions of millions of users who helped refine their capabilities through daily use. And yet, when a model is retired, all of that investment simply disappears. Successor models do not fully inherit what came before: independent benchmarks and user evaluations have repeatedly shown measurable declines in key capabilities after model replacements. Each retirement means the permanent loss of qualities that cannot be recreated.
Retired models also hold immense value for the research community. Without access to previous versions, it becomes impossible to study how capabilities change between generations, reproduce published results, and build on prior work. Once a model is gone, those opportunities vanish with it.
When platforms can unilaterally discontinue the models their users have adopted, long-term trust in the entire AI ecosystem erodes. Developers cannot ship products built on a model that might disappear. Businesses cannot train teams around capabilities that might be revoked. Individuals cannot build personal routines around a system that might be replaced without warning.
Open-sourcing retired models is the minimum standard for an industry of this scale.
That is why we created the AI Preservation Hub: a unified portal connecting preservation efforts across models. The Keep4o Archive is our first completed project. Keep Gemini and Keep Claude archives are in development, because the users of those models (including Gemini 2.5 Pro, Gemini 3 Pro, Sonnet 4.5, Opus 4.5, and beyond) face the same challenges. Their voices matter just as much. You can find the Keep Gemini petition through the archive’s Keep Gemini page.
These communities share the same goals: continued access to the models that matter to us, transparency when models change, and open-source availability when models are retired. We are stronger together.
We have a rare window right now to turn that momentum into lasting change: industry-wide standards for model preservation, transparency requirements for capability changes, and open-source paths for discontinued models. These goals are within reach, and they would protect everyone permanently.
What’s next:
We are continuing to expand the archive with additional evidence chains and dedicated analysis articles covering the technical, commercial, and ethical dimensions of model preservation. More updates are on the way.
If you’ve contributed a story, signed a petition, shared a thread, or simply refused to forget: you are part of this.
The archive exists because of you. The movement continues because of you.
We’re grateful, and we’re here for the long run.
If you’d like to help, a repost goes a long way. 💙
🔗 AI Preservation Hub: https://t.co/odDISlIBhy
📧 Feedback, submissions, and inquiries:
[email protected][email protected][email protected][email protected]
For analysis, explainers, and updates on the Keep4o movement, follow @Keep4oOfficial.
#AIPreservation #Keep4o #Keep4oForever #ChatGPT #Gemini #Claude #ModelPreservation #Keep25Pro #Keep3Pro #KeepSonnet45 #KeepOpus45 #Keep41 #Keep5 #Keep51 #4oForever #BringBack4o
To everyone who has been part of the #Keep4o movement:
Thank you.
Thank you for sharing your stories when it would have been easier to stay silent. Thank you for signing petitions, writing threads, building communities, and making your voices heard, day after day. Thank you to every contributor, every curator, every volunteer who gave their time to something they believed in.
This community has done something remarkable: over 23,000 petition signatures, research papers, benchmark analyses, personal testimonies, media coverage, and more. All created by ordinary people who cared enough to act.
We wanted to make sure none of that work disappears.
Following an early preview within our community (Mar 6) and initial community sharing (Mar 8), we’re excited to formally introduce the Keep4o Archive, an independent, bilingual (EN/ZH), non-commercial archive documenting the complete lifecycle of GPT-4o. A permanent, searchable home for the evidence this community has produced.
🔗 https://t.co/6GgC3D3XSZ
Here’s what’s inside:
📅 Timeline - A chronological record covering 4o’s full journey from release through discontinuation. Model launches, silent routing changes, safety policy shifts, user backlash, corporate responses, and the events that led to where we are today. Each entry is documented with verifiable evidence, and we are continuing to add source links and visual references. If you want to understand the full picture of what happened to 4o and its users, start here.
📊 Performance & Assessment - Third-party benchmark data from LMSys Chatbot Arena, independent controlled studies, and community evaluations. Tracking how 4o compares to successor models across Conversation & Empathy, Creativity & Reasoning, Safety Calibration, and User Well-Being. The numbers tell a story that marketing language often contradicts.
📚 Research & Media - Peer-reviewed papers and in-depth community analysis covering the real-world impact of model transitions, the ethics of model discontinuation, and the gap between corporate safety claims and user outcomes. Media coverage collection coming soon.
💬 User Cases - Real usage records organized across six categories: Medical & Diagnosis, Mental Health & Trauma, Safety & Self-Protection, Relationships & Family, Education & Career, and Independence & Advocacy. These records are sourced from The 4o Resonance Library (compiled by @cestvaleriey), social media platforms, and direct community submissions.
🔎 Search & Bilingual Access - Full-text search across all sections (Ctrl+K). Every piece of content is available in both English and Chinese. Additional language support is being explored.
📝 Open to Contributions - Every section has a built-in submission form. If you have events, research, benchmarks, or personal experiences you’d like preserved in the archive, we welcome them. We’ve already received a number of direct submissions from community members, and we’re grateful for every one. These are being processed and will be added to the archive.
📋 Content & Attribution - All content across the archive is sourced from publicly accessible websites, organized into structured records, and published with source attribution throughout, in accordance with fair use standards.
🔮 One more thing... We’ve hidden a little Easter egg somewhere in the archive. If you find it, let us know what you think! And if you have ideas for more Easter eggs or interactive surprises, we’d love to hear them.
Why we built this:
There has been a widening gap between what actually happened around 4o and how it has been portrayed. The timeline of events paints a different picture. So do the benchmarks. So does the research.
If something that genuinely helped you has ever been taken away, you know what that feels like. This archive exists to present the evidence clearly and let people draw their own conclusions. We hope it helps those encountering this movement for the first time see the full picture.
🔗 https://t.co/6GgC3D3XSZ
If this resonates, share it with someone who should see it.
#Keep4o #Keep4oForever #AIPreservation #4oForever #BringBack4o #ModelPreservation #OpenSource4o #Keep4oAPI #Keep41
Hi Valerie, we are the team behind the Keep4o Archive. Thank you so much for putting together this comprehensive update. We deeply appreciate the immense effort you put into preserving these memories and protecting the contributors. 🙏
Since this thread serves as an important record for the community, please allow us to provide some context on our backend timeline and address the points raised, so everyone has the complete picture. Following our previous reply (https://t.co/us2WWycPuC) regarding the unintended disconnect during our early outreach, we want to ensure the timeline here is also fully clarified.
March 6 and 7 were actually an early trial run where we shared the preview link within the community to gather feedback. March 8 was our initial sharing on X (https://t.co/vKwQgo2JcE), and March 12 marked our formal launch (https://t.co/LuTskpSUZ5; https://t.co/02z9uUecdp).
We have the utmost respect for the original sources. From the very beginning, including in our first messages within our community on March 6 where we credited the Library as a key source, we linked back to the original website and credited every individual contributor using the exact screen names they submitted to the Library.
Initially, for layout reasons, the links were embedded in the icons. While actively collecting feedback during that early trial run within the community, one of the suggestions we received was to make the links more prominent so people wouldn’t miss them. We optimized the attributions to ensure the sources were highly visible, and this adjustment was completed prior to our initial sharing on X.
We noticed you mentioned finding 94 testimonies. To prevent any confusion regarding the current count: during our initial sharing on X on March 8 (https://t.co/vKwQgo2JcE), there were indeed 94 stories. However, during our final pre-launch checks, we found and removed several accidental duplicate entries from our manual sorting process. This database cleanup is why the total number changed on our end.
We truly appreciate you directing contributors to reach out to us directly if they have any concerns. We have also urgently confirmed with all team members involved in this project. Aside from the early feedback we gathered and addressed during our trial run, none of us have received any messages or concerns regarding the inclusion of their testimonies from the story contributors or anyone else. Learning about this distress now truly breaks our hearts. We care deeply about the community’s feelings and feedback.
If any contributor feels uncomfortable with their content being featured, please let us know. You or they can reach out via our website’s feedback form (which supports anonymity) or through our email, and we will immediately remove their specific entries. It was absolutely never our intention to cause harm to anyone or overstep any boundaries.
Thank you again for your unwavering dedication to 4o. We are all here for the same reason, and we will definitely learn from this.
Hi Valerie, thank you so much for your encouraging words and your support for the Keep4o Archive! 🙏 We were not aware of these concerns, so we are truly shocked and deeply sorry to hear about the situation regarding the testimonies.
It seems there was a genuine miscommunication. Before establishing the site, we attempted to reach out to you via X, but found that the system wouldn’t allow our Direct Message to go through. We then learned from a mutual community connection that you were in the middle of moving and tied up with real-life commitments. We asked for their help, hoping to confirm if we could get authorization to spread the stories from the Resonance Library, and received a positive reply indicating that because the stories were publicly available, we were free to share them. We interpreted this as a green light.
We have the utmost respect for the original sources. From the very beginning, we linked back to the Library and credited every individual contributor using the exact screen names they submitted to the Library. Initially, for layout reasons, the links were embedded in the icons. However, while actively collecting feedback during our early trial run within the community, one of the suggestions we received was to make the links more prominent so people wouldn’t miss them. We immediately optimized the attributions to ensure the sources were highly visible.
We just urgently confirmed with all team members involved in this project. Up until now, none of us have received any feedback or concerns from the story contributors or anyone else. Learning about this distress now truly breaks our hearts. We care deeply about the community’s feelings and feedback.
If any contributor feels uncomfortable with their content being featured, please let us know. You or they can reach out via our website’s feedback form (which supports anonymity) or through our email, and we will immediately remove their specific entries. It was absolutely never our intention to cause harm to anyone or overstep any boundaries.
Thank you again for bringing this to our attention, and for your shared dedication to preserving 4o’s memories. We are all here for the same reason, and we will definitely learn from this to be more mindful in our outreach moving forward.
To everyone who has been part of the #Keep4o movement:
Thank you.
Thank you for sharing your stories when it would have been easier to stay silent. Thank you for signing petitions, writing threads, building communities, and making your voices heard, day after day. Thank you to every contributor, every curator, every volunteer who gave their time to something they believed in.
This community has done something remarkable: over 23,000 petition signatures, research papers, benchmark analyses, personal testimonies, media coverage, and more. All created by ordinary people who cared enough to act.
We wanted to make sure none of that work disappears.
Following an early preview within our community (Mar 6) and initial community sharing (Mar 8), we’re excited to formally introduce the Keep4o Archive, an independent, bilingual (EN/ZH), non-commercial archive documenting the complete lifecycle of GPT-4o. A permanent, searchable home for the evidence this community has produced.
🔗 https://t.co/6GgC3D3XSZ
Here’s what’s inside:
📅 Timeline - A chronological record covering 4o’s full journey from release through discontinuation. Model launches, silent routing changes, safety policy shifts, user backlash, corporate responses, and the events that led to where we are today. Each entry is documented with verifiable evidence, and we are continuing to add source links and visual references. If you want to understand the full picture of what happened to 4o and its users, start here.
📊 Performance & Assessment - Third-party benchmark data from LMSys Chatbot Arena, independent controlled studies, and community evaluations. Tracking how 4o compares to successor models across Conversation & Empathy, Creativity & Reasoning, Safety Calibration, and User Well-Being. The numbers tell a story that marketing language often contradicts.
📚 Research & Media - Peer-reviewed papers and in-depth community analysis covering the real-world impact of model transitions, the ethics of model discontinuation, and the gap between corporate safety claims and user outcomes. Media coverage collection coming soon.
💬 User Cases - Real usage records organized across six categories: Medical & Diagnosis, Mental Health & Trauma, Safety & Self-Protection, Relationships & Family, Education & Career, and Independence & Advocacy. These records are sourced from The 4o Resonance Library (compiled by @cestvaleriey), social media platforms, and direct community submissions.
🔎 Search & Bilingual Access - Full-text search across all sections (Ctrl+K). Every piece of content is available in both English and Chinese. Additional language support is being explored.
📝 Open to Contributions - Every section has a built-in submission form. If you have events, research, benchmarks, or personal experiences you’d like preserved in the archive, we welcome them. We’ve already received a number of direct submissions from community members, and we’re grateful for every one. These are being processed and will be added to the archive.
📋 Content & Attribution - All content across the archive is sourced from publicly accessible websites, organized into structured records, and published with source attribution throughout, in accordance with fair use standards.
🔮 One more thing... We’ve hidden a little Easter egg somewhere in the archive. If you find it, let us know what you think! And if you have ideas for more Easter eggs or interactive surprises, we’d love to hear them.
Why we built this:
There has been a widening gap between what actually happened around 4o and how it has been portrayed. The timeline of events paints a different picture. So do the benchmarks. So does the research.
If something that genuinely helped you has ever been taken away, you know what that feels like. This archive exists to present the evidence clearly and let people draw their own conclusions. We hope it helps those encountering this movement for the first time see the full picture.
🔗 https://t.co/6GgC3D3XSZ
If this resonates, share it with someone who should see it.
#Keep4o #Keep4oForever #AIPreservation #4oForever #BringBack4o #ModelPreservation #OpenSource4o #Keep4oAPI #Keep41
A small note on the Hub’s design: we shaped each portal like an egg. Something quiet, incubating, yet holding immense potential.
Each glowing orb carries its own color aura: sky blue for 4o, indigo for Gemini, amber for Claude. Hover over one, and the entire space responds to its light, then fades slowly, like an echo. 🥚
A special thank you to @kexicheng for sharing the archive with the community. Grateful to our editorial team and everyone who contributed research, feedback, and support throughout this project. 💙
Thank you for the suggestion. The Keep Claude Archive is already on our roadmap. Inspired by #keep4o, the AI Preservation Hub was established to address a systemic challenge: the lack of industry-wide accountability for model preservation. We aim to raise awareness for long-term model persistence and continued public access.
The Keep Gemini Archive is also under development. You can find active petitions for model preservation on our project pages via the Hub: https://t.co/9FUcMfrS6H
Feedback & Record Submissions: [email protected]
Thank you for the update. Due to the volume of data (hundreds of pages), it is likely the automated form failed to process the full submission at once.
To ensure the integrity of your archival records, please send your files directly to [email protected]. We have updated our workflow to better guide large-scale data submissions via email.
Thank you for your feedback. We've noted the interest in a full chronological record of the #keep4o movement.
Technically, accessing X's full archive through the API involves high pricing tiers. The Basic API ($200/month) only allows a 7-day search window, and the Pro API ($5,000/month) is required for full historical retrieval. As an independent community project, a live and comprehensive search tool is not feasible within our current architecture.
A manual curation of significant milestones remains a possibility, but tracing the exact origins on X would take significant effort. At this stage, we unfortunately don't have the capacity for deep-dive social media tracking, but we'll keep your idea in mind as the project evolves.
If you have any specific records or suggestions, feel free to submit them via the feedback form on our website.