About the Giggles Project and Current Status
Updated Notice – March 2026
Notice to the There.com Community
Giggles development is currently paused.
When this project began, it was in response to multiple community members who asked if we would consider bringing Giggles back. The intent was to revive something nostalgic and meaningful in a modern, stable way while preserving the spirit people remembered.
As we moved through the process, several important realities became clear.
An unrelated party had already filed for a software mark under the same classification. This means the name Giggles would have required a change before any release regardless of public discussion. That issue was procedural and would have been addressed appropriately.
At the same time, it became clear that the project had generated strong reactions and division within parts of the community. That was never the goal.
Because of these factors, development is paused while we determine the most responsible path forward.
Current Status
• There is no active new client being released.
• There is no rollout in progress.
• The legacy Giggles files have been removed in light of the controversy and community concerns surrounding this project. We understand this may be disappointing to some users, and we apologize for that.
Trademark Clarification
The trademark filing was not about control. It was about stewardship.
When you invest time and money into building a new piece of software, protecting the name is standard and responsible practice. It ensures the brand cannot be misused, misrepresented, or fragmented in ways that create confusion or harm users.
A trademark protects a brand identifier. It does not grant ownership of someone else’s copyrighted source code. It does not rewrite history. It simply protects the name attached to a new build.
That distinction matters.
Good Faith Efforts
Before moving forward, we conducted research into prior use, public filings, and known contacts associated with Giggles. The goal was never to take something from anyone. The goal was to preserve and modernize a small but memorable part of the There.com experience.
However, given the classification conflict and the level of public concern expressed, continuing development without broader input would not be appropriate.
Opening the Conversation
Rather than quietly discontinue the project or move forward without community input, we are preparing to open a structured opportunity for constructive discussion.
Details on how to participate will be announced in the coming days.
This conversation will address real questions, including:
• Should the project move forward at all
• Should it operate under a completely new name
• What should it be called if it continues
• What expectations the community would have for a modern rebuild
• Whether it should remain paused indefinitely
This will be an opportunity for thoughtful questions and meaningful suggestions. It will not be a space for hostility or personal attacks.
Until a clear direction is determined, development remains paused.
Commitment to the Community
Thumdar operates under a Free for All, Always commitment. Everything built under the platform has been created to contribute positively to the There.com community.
We met on There.com. This platform has always meant something to us. Any decision regarding Giggles will be made carefully, transparently, and with respect for both the original creator and the broader community.
If the project moves forward, it will do so in a way that reflects community input and responsible stewardship. If it does not, that decision will also be made openly.
This notice replaces the August 13, 2025 statement to reflect the current status and facts.
Previous versions of this statement are archived below for transparency and reference.
Archived Giggle stewardship and legal status (Agust 13, 2025)
About Our Giggles™ Trademark and Future Plans
Effective Date: 8/13/2025
Notice to the There.com Community – What This Means for You
We’re excited to announce that Thumdar is officially taking stewardship of the Giggles™ name so we can give it a future, not let it fade into history. For years, Giggles was a small but unforgettable part of the There.com experience. Many of you used it to make events more fun, express yourself, and add personality to your avatar. But for a long time, it’s been frozen in time, no updates, no fixes, no support.
This change is about bringing Giggles back, modernized and upgraded, while keeping the charm you remember. We’re building a brand-new Giggles application from scratch, our code, our design that stays true to the classic experience but introduces exciting new features, improved stability, and integrated updates.
The legacy Giggles you know and remember will remain downloadable from Thumdar.com during this transition, but we’re starting fresh under the hood. We’re not taking anyone’s old code; the original creator’s work remains theirs. We’re simply ensuring the Giggles name and concept stay alive, relevant, and accessible for everyone.
Legal Status & Abandonment
After exhaustive research — including USPTO TESS records, state filings, common-law searches, forum archives, and outreach to every known contact — we found:
No active website or valid contact emails for Giggles.- No trademark registrations or oppositions in over five years.
- No evidence of copyright enforcement or commercial use since the original business closed.
Under the Lanham Act, non-use for three consecutive years creates a presumption of abandonment. This inactivity also supports the conclusion that any rights in the legacy code have lapsed or gone unenforced.
Why We Registered the Trademark
We filed USPTO Intent-to-Use Application No. 99329307 (International Class 009: Windows application software) to protect the Giggles™ name and prevent unauthorized “look-alikes” or forks that could fragment the experience.
Owning the mark means:
Consistent branding across all future releases.- Centralized updates and technical support.
- A clear licensing path for anyone wishing to use the Giggles name.
Our Development Path Forward
We are not pausing development. The new Giggles™ client is already in progress, with:
A clean, modern interface.
Server-based script updates for fresh routines without manual installs.
Bug fixes and compatibility improvements for the latest There.com environment.
We’re calling the old program “Legacy Giggles,” and it will stay downloadable for now, “as-is,” while the new version is built and tested.
Approximate Timeline (6 Months)
Day 1 (Today) – This notice is published, and the 90-day window for any verified rights holder to come forward begins.- 90 Days (Deadline: Tuesday, November 11, 2025) – If no valid claim is received by this date, we will continue facilitating access to the legacy builds until the new Giggles client is released.
- Months 4–6 – Testing and rollout of the new Giggles™ client; legacy builds will remain available during this period.
- Post-Release – Once the new Giggles™ is stable and widely adopted, the legacy builds may be phased out for security and compatibility reasons, with advance notice given.
Notice: Conditions for Facilitating Access to Legacy Giggles
The legacy Giggles application and its binary code remain the intellectual property of its original creator or their estate. Thumdar does not claim ownership of that code. We are facilitating access to the legacy files solely for preservation purposes because:
- There has been no copyright enforcement or legal correspondence regarding Giggles for many years.
The software has been widely and openly distributed by the community since the original company closed.
No active rights holder, trademark owner, or successor entity has engaged in any enforcement action whatsoever during this time.
We are facilitating access to these files on an “as is” basis for the There.com community’s continued enjoyment, with the express condition that if a verified and lawful request is made by a rights holder or their authorized agent, access will be promptly withdrawn.
By continuing to facilitate access to these files, we are not asserting any legal claim over the underlying code; we are simply preserving a piece of There.com history until such time as the rightful owner instructs otherwise.
90-Day Response Window for the Original Creator
From the date of this notice, we are offering the original creator (or a verified rights holder) 90 days to step forward with proof of ownership or licensing requests.
If they do:
We’ll open good-faith discussions about code assignment or collaboration.
We’ll honor valid legal requests to remove the legacy files.
If they don’t:
We will continue development of the new Giggles™ unimpeded.
The legacy version will eventually be phased out once the new client is widely adopted.
Code Ownership & Reimplementation
Rights Acquisition: If a verified rights holder contacts us, we will discuss possible code transfer or licensing.- Clean-Room Rewrite: If no agreement is reached, the new Giggles will remain a clean-room build — fully original, Thumdar-owned code.
Copyright Registration: Once complete, our code will be registered with the U.S. Copyright Office.
Respecting the Original Creator & the Community
We want to be clear: we are not stealing anyone’s work. The original creator’s legacy is respected and preserved. Our goal is to carry the spirit of Giggles forward in a way that’s compatible, stable, and exciting for a new generation of There.com users.
Our Commitment
Thumdar will:
- Preserve the Giggles™ name and legacy.
- Keep the community informed every step of the way.
- Defend the trademark against misuse.
Deliver a new version that honors the old while moving it forward.
Disclaimer: Giggles legacy software is made available strictly for community preservation; Thumdar does not claim ownership of the original binary code. These files are provided “as is.” If you hold legitimate rights to the Giggles™ name or legacy code, please contact us at legal@thumdar.com with verified proof, and we will engage in good-faith discussions regarding your request.
This notice was published on August 13, 2025, and will remain publicly available for reference.