BigBear Is Stealing My Work

Again, yes, I understand that we’re all here to contribute to the community. But you’re still missing my entire point.

If one person keeps adding apps that other people have already discovered, configured, tested and maintained, obviously their AppStore will eventually become the biggest. But what happens to everyone else who is putting in the same effort?

Why would other developers continue spending their time and resources maintaining their own AppStores if someone can simply take their work, add it to theirs, and benefit from all that effort?

Who ultimately suffers? The ZimaOS community itself.

People will lose motivation to contribute if they feel their work is being copied without proper credit or recognition. Eventually, fewer people will bother discovering new projects, testing apps, fixing issues and maintaining their own stores.

And then what? Everyone is expected to contribute freely while one store keeps collecting the benefits?

Also, someone else contacted me about experiencing the same issue. They don’t want to come forward publicly, so I’m not going to mention their case as evidence. But it does show that I’m not the only person raising these concerns.

I’m not trying to start a fight with anyone. I’m asking for some basic respect for the people who put in the time and effort to build this ecosystem.

If we genuinely care about the ZimaOS community, we should care about keeping contributors motivated to continue building it.

Hey mate, I understand what you’re saying now, and you do raise some fair points.

When I mentioned ZimaBrain, I was looking at it from my own perspective as a developer. I’m happy for anyone to distribute my app because I want people to use it.

But I can see your point is different. You’re talking about the countless hours spent finding projects, configuring them, testing everything and maintaining an entire App Store, only to see the same apps appearing elsewhere without recognition for that effort.

And I agree, that work deserves respect and proper credit.

At the same time, having the same apps in different stores doesn’t necessarily mean someone’s work has been copied. That’s why I think the GitHub history and actual configurations need to be reviewed properly.

I also think IceWhale should give independent App Stores more visibility. Having multiple developers maintaining their own collections is a good thing for ZimaOS, and we certainly don’t want to discourage that.

You’ve obviously put a lot of effort into your store, mate, and I’d hate to see you walk away from something you’ve worked so hard to build.

Hopefully something positive comes out of this discussion, because the community needs developers like you contributing.

I just realised something else.

About a month ago, my AppStore had only around 25ish apps. Now, looking at BigBear’s Git commit history, I can see that 22 apps were added all at once. And Those were the exact apps I already had in my store at the time.

In short technically he Cloned my whole repo.

Seriously, What more am I supposed to prove?

Hope this will clear up. There is no need for app duplication on different stores, it would be better to focus that all of the apps working and being updated regularly. I enjoyed discovering new apps on your store especially anything I installed worked straight away. Hope you won’t pull out supporting from ZimaOS and IceWhale will give you all the support and allow BigBear and IceStore coexist on ZimaOS.

I genuinely enjoyed developing these apps. I’ve been spending my own time and money discovering projects, configuring them, testing them and making sure they actually work.

But people like BigBear ruin that whole culture. They make you question why you should keep putting in the effort when someone else can seemingly take your work and add it to their own store.

And the frustrating part is that many of his apps don’t even work properly. From what I’ve seen, it looks like they’re being added without proper testing or verification. What’s the point of having hundreds of apps if users can’t even get them working?

To make matters worse, he BANNED MY SECOND DISCORD ACCOUNT TOO I raised concerns and wanted answers. Instead of having a proper discussion, I’m now locked out.

Honestly, it makes the whole situation look even worse. If there is nothing wrong with the way the apps were added, why not address the evidence and explain things openly?

I’m also disappointed with IceWhale. They made him a moderator here and actively promote his work, so I think it’s fair to ask what standards they expect from someone in that position.

I want to keep contributing to ZimaOS and IceWhale, but contributors need to feel that their work is respected and that concerns about copying, attribution and app quality will be taken seriously.

Right now, I’m genuinely questioning whether it’s worth continuing.

I hope IceWhale steps in and addresses this properly. The community deserves better.

For me it is frustrating when more than 1 store has the same app. It is also frustrating when I have to essentially choose custom install on every app. It’s great to do that and find everything with proper variables set, with minimal changes needed if any. Some apps from some app stores basically make me hunt for the github repo to see what variables are availble to make it work right. I love the app stores that have everything essentially right. So I have mixed feelings on having apps in multiple stores. But the fact that if an app has identical variables on 2 stores, and those variable default values are Zimaos specific, and or don’t match the default variables values supplied by the original repo out there and they match 100% to another zimaos repo that is an obvious copy.

Hey mate, I can understand your frustration, and I certainly respect the amount of time and effort you’ve put into developing and testing your apps.

I’ve actually spent quite a bit of time investigating this myself, going through both GitHub repositories, checking commit histories and comparing the actual Docker Compose files.

Here’s what I found.

I checked the GitHub history for all 22 applications added in BigBear’s PR #3851, and you’re absolutely correct that your versions were published first. There’s no argument there.

I also compared 10 pairs of Docker Compose files side by side. While there were similarities in environment variables, images and configurations, none of the files I compared were identical. I also checked some of the original upstream configurations and found settings that were common to those projects.

Now, SirWill makes a good point. If someone has copied unique ZimaOS-specific configurations, including custom values that aren’t found in the original project’s documentation, then that’s definitely worth investigating. But we need to identify those exact settings and compare the original files before calling it plagiarism.

I also found that BigBear has responded directly to your GitHub issue #6566. He explained his development process and offered to investigate any specific examples of copied work.

From everything I’ve examined so far, I can confirm you published those applications earlier, but I haven’t found conclusive evidence that BigBear copied your original configurations.

And mate, I wouldn’t let this discourage you from continuing your work. You’ve clearly put a lot of effort into your App Store, and people here appreciate that.

Personally, I think there’s room for multiple App Stores in the ZimaOS community. What matters most is that applications work properly, are maintained and give credit where it’s genuinely due.

I’d much rather see both of you continuing to develop great applications than spending your time arguing over them.

Life’s too short, mate. We’ve all got better things to be doing! :joy::+1:

Not sure about life being too short, mate, but my time is definitely valuable.

I appreciate you taking the time to investigate the repositories and compare the files. However, I think you’re missing some important points here.

First, this isn’t just about whether two Docker Compose files are identical. It’s about accountability, especially when BigBear is a member of staff and IceWhale actively promotes his work by pre-adding his AppStore to fresh ZimaOS installations.

Think about it from a regular user’s perspective. Why would someone bother adding my AppStore or @Lintux’s AppStore when the same apps are already available in BigBear’s store? As @SirWill pointed out, users don’t want the same app duplicated across three different stores. Naturally, they’ll stick with the store that’s already available to them.

This directly affects the motivation of people who spend their time discovering, configuring, testing and maintaining apps for the community.

Now, regarding your comparison of the Docker Compose files.

My AI Skill file is different from his. When I use AI to create an app, it generates the description, developer information, GitHub links, website, release notes and other relevant details. I put effort into these things because I care about quality and want users to have a proper experience.

From what I’ve seen, his approach appears to focus on adding the application itself while leaving much of that additional information out.

That’s the difference between focusing on quality and focusing on quantity.

Different code does not automatically mean the work was independently created. Two files can have different structures while still sharing the same underlying configuration choices, services and custom values.

Second, variables and services can tell us a lot.

Take Stoat Chat as an example. The original developer provides a basic Compose configuration, leaving decisions about storage, databases and other supporting services to whoever deploys it.

BigBear’s version includes the exact same supporting services as mine. That’s worth investigating.

Third, look at the variables.

A service like MinIO can support dozens of environment variables, but developers generally include only the essential ones in a simple deployment file, such as the application URL, timezone, username and password. The remaining options can go into the documentation. My apps (previously) had JWT and/or Session Tokens hardcoded as variables. I didn’t knew that we did not have to hard code then because the service generate unique onces if not added. In this store, for apps same mine also have same hard codes variables.

That’s the approach I follow because I want ordinary users to be able to deploy apps without having to understand every technical detail.

When another store uses the same selection of variables and supporting services, particularly where those choices aren’t specified by the upstream developer, I think it’s reasonable to ask how those configurations were developed.

I’m not claiming that a matching variable alone proves copying. I’m saying that these details need to be examined alongside the commit history, timing and other similarities I’ve already raised.

Now, let me ask you something as a developer.

Do you genuinely believe one person can independently discover, configure and add 22 applications in a single batch, especially when those exact applications were already available in my store?

Yes, AI has made writing code much easier. I use it myself. But the work doesn’t end when AI generates a Compose file.

You still need to find worthwhile projects, understand their requirements, configure their services, test whether the frontend and backend work, troubleshoot problems, find suitable logos and screenshots, and document everything properly.

Sometimes projects don’t even provide screenshots, so I take my own and add them. If you look at my app screenshots, you’ll often find my name because I created those screenshots myself.

All of this takes time. That’s why I generally add one app at a time.

I have a full-time job and a nine-month-old child, yet I still make time to contribute because I enjoy developing these apps and helping the community.

I’m not replying to every comment on his GitHub because I don’t want this argument spread across five different platforms. He has also banned me from his Discord, so having a productive discussion there is no longer an option.

But here’s another question. I raised these concerns four days ago, NZST. Why hasn’t he responded directly to the specific evidence I’ve presented? Why hasn’t IceWhale addressed the concerns either?

I’m not asking you or other community members to speak on his behalf. I want him and IceWhale to come forward and provide answers themselves.

Finally, before someone tells me that this is open-source work and I shouldn’t make an issue out of it, let me make something clear.

I believe in sharing. That’s exactly why I published my Claude Skill for creating ZimaOS and CasaOS apps and shared it with this community.

I want people to be able to create apps themselves when they can’t find them in an existing store. I’m happy to share knowledge, tools and working solutions.

But sharing knowledge is different from copying someone else’s work without proper attribution.

And why is he adding “BigBear” everywhere, including AppData folders, variables and even service names such as “bigbear-postgres”? He is so self obsessed and childish.

My concern isn’t that someone else is building an AppStore. I’m questioning the pattern of duplication, the lack of proper attribution and the apparent lack of testing.

I have invested my own time and money into this work. So yes, I take it seriously when I believe that effort is being copied without proper recognition. I consider that disrespectful.

I want this addressed properly, not brushed aside with comments about life being too short or everyone getting along.

The questions are straightforward. How were these apps and configurations developed? Where did the matching choices come from? Why are the original sources not consistently credited? And what standards does IceWhale expect from someone whose store receives this level of official visibility?

I’d like BigBear and IceWhale to answer those questions directly.

This is exactly the kind of issue I’m talking about.

In my initial AppStore, I hardcoded token variables, meaning everyone would use the same token, and that token was publicly visible in the Compose file. BigBear’s version also had the same hardcoded token.

I later realised this wasn’t a good approach and changed it in my updated store.

Here’s one example. Compare these two files:

BigBear’s BookOrbit:

My BookOrbit:
https://github.com/HSingHira/ZimaAppStore/blob/main/Apps/BookOrbit/docker-compose.yml

There are other apps with similar issues too.

For example, SETUP_BOOTSTRAP_TOKEN wasn’t actually required because the application generates its own token. I didn’t know that initially, so I hardcoded it in my first version. I corrected this in my updated store, but BigBear’s version retained the hardcoded configuration.

My point is that the same questionable configuration choices appear in both stores, including choices I later identified as mistakes and corrected.

I’m not claiming that one matching variable automatically proves copying. I’m asking why these same mistakes and configurations appear in his versions, particularly when they aren’t required by the original applications.

Now, here’s the bigger concern.

My AppStore is a third-party store. IceWhale doesn’t officially endorse it or pre-add it to fresh installations. BigBear’s store, however, comes pre-added to ZimaOS.

A user has already raised an issue on GitHub about this kind of problem.

When publicly exposed tokens or credentials are included in app configurations, users may unknowingly deploy services with predictable credentials. Depending on the application and how those credentials are used, this could expose their data or allow unauthorised access.

That’s a serious concern, especially when ordinary users trust the default AppStore provided with their OS.

I believe IceWhale needs to investigate this properly. They should review the affected Compose files, check whether any exposed credentials create a real security risk, and ensure that apps distributed through the pre-added store follow basic security and quality standards.

This goes beyond a disagreement between two AppStore maintainers. It’s about protecting users, maintaining trust and ensuring that the apps people install actually work securely.

I hope IceWhale takes these concerns seriously and addresses them directly.

Hi HSinghHira, after reading what you’ve shared over the past few days, I can see how much time and care you’ve put into your store. Discovering interesting projects, adapting them for ZimaOS, troubleshooting deployment problems, writing instructions and keeping everything updated takes patience. Users may only see a “one-click install” button, but behind it are many hours of work. That effort deserves to be seen and recognized.

I understand that you care about more than how many apps your store has. You also want the work you’ve done to be respected. When you spend your own time contributing to a community and feel that your efforts are going unnoticed, it can be discouraging. Thank you for explaining that so openly. It has made us reflect on whether we’ve given independent contributors enough attention and support.

I also want to thank BigBear. Over the years, you’ve put considerable time into maintaining your store, creating tutorials and helping users. Those are valuable contributions too. HSingh, BigBear, Lintux and other maintainers each bring different interests, experience and strengths. Together, those contributions give ZimaOS more possibilities.

This discussion has also helped me recognize that, as more developers join us, the way we support contributors needs to grow with the community. Our current default recommendation gives one store greater visibility, while other independent stores have fewer opportunities to be discovered. That is something we haven’t thought through carefully enough in our product design.

We appreciate everyone who chooses to spend their time building for ZimaOS and sharing what they know. We want their work to reach users, and we need to turn that appreciation into clearer ways to participate, more open developer support, and fairer opportunities for visibility and community incentives.

People sharing their time, knowledge and creativity are the heart of ZimaOS. Whether someone discovers a useful project, solves a difficult deployment problem or maintains a small, carefully curated store, we want them to feel that their contribution has a meaningful place here.

I’ll raise these issues directly at our next weekly team meeting: how to make contributing clearer and easier, which APIs we can open up, how to give independent stores more visibility, and how community incentive funding should be allocated fairly and transparently. I hope we can turn these discussions into a concrete plan soon, so contributors have a clearer understanding of the support available to them.

Thank you both for everything you’ve already shared with the community. I hope we can keep building a place where current contributors—and the developers who join us in the future—feel recognized, supported and encouraged to create.

Thank you for taking the time to respond. I genuinely appreciate your acknowledgment of the work independent contributors put into the ZimaOS community. I’m glad this discussion has encouraged IceWhale to reflect on how independent developers can receive better support and fairer visibility.

I also appreciate your willingness to raise these issues at the next team meeting. I hope this leads to practical changes, not just for me, but for @Lintux and other independent contributors who invest their time and resources into this ecosystem.

However, I would also like to bring the discussion back to the original concerns I raised, because I don’t believe they have been adequately addressed yet.

I understand and respect that BigBear has contributed to the community over the years. I’m not denying that he has done useful work. My concerns are specifically about the similarities between our app configurations, the timing of his additions, the lack of proper attribution, and the quality and security of some applications in his store.

As I’ve explained throughout this discussion, I found that 22 applications were added to his store in one batch, and those applications were already available in mine. I’ve also highlighted matching variable values, supporting services and configurations, including some mistakes that I later corrected in my own store. I understand that similarities alone don’t automatically prove copying, which is why I have provided specific examples for comparison.

There are also concerns about publicly exposed tokens and credentials. I believe these deserve a proper technical review, particularly because BigBear’s store is pre-added to ZimaOS installations and receives official visibility from IceWhale.

I would appreciate direct answers to these concerns rather than having the discussion focus only on how we can support contributors in the future.

Could you please ask BigBear to come forward and respond to the specific allegations and examples I’ve raised? I would like him to explain how these configurations were developed, address the matching values and services, and clarify why the original sources and contributors are not consistently credited.

If any of my work has been copied without appropriate acknowledgment, I would also expect the affected apps to be removed from his store until the matter is resolved, or for the copied configurations to be replaced with independently developed versions that properly credit their sources and meet the required standards.

I also believe IceWhale needs to review this situation impartially. Since BigBear is a member of staff and his store receives privileged visibility through the default installation, there should be clear accountability. If the investigation establishes that he has deliberately copied other contributors’ work without proper attribution, or failed to meet the standards expected of a staff member, then I believe IceWhale should reconsider his staff position and withdraw its official endorsement and preferential promotion of his store.

I’m not asking IceWhale to take my word for everything. I’m asking for a fair investigation based on the commit histories, file comparisons, configuration details and the specific concerns raised by the community.

I also want to be clear that I have no problem with multiple AppStores existing. I support open-source development and sharing. I’ve even shared my own Claude Skill publicly so others can create applications and contribute to the community. My concern is that sharing should not come at the expense of the people doing the original work.

I have a full-time job and a young child, and I still spend my personal time and money testing, documenting and maintaining these apps. I do this because I enjoy it and want to help make ZimaOS better. I would like other contributors to feel that their efforts are equally respected.

Thank you again for acknowledging the need for fairer support. I hope IceWhale will also address the existing allegations directly, ask BigBear to respond publicly, and provide a clear outcome so that everyone involved understands what happens next.

I believe that would be a meaningful step towards rebuilding trust and ensuring that independent contributors feel safe and motivated to keep supporting ZimaOS.

Thanks, Spider. I’ve decided to step back from the Big Bear app store, and this is my last post about it.

I’ve spent thousands upon thousands of hours building, maintaining, testing, troubleshooting, and contributing to open-source projects. I’ve been part of the GitHub community since 2011, long before AI coding assistants existed. I’ve worked on Big Bear every day, sometimes 6 to 12 hours a day, just maintaining it. I even kept it maintained while I was on vacation. My GitHub shows 16,790 contributions across my projects in the last year, with work on almost every single day:

And do you know what I’ve received for most of that work? A thank you.

I’ve received countless thank-yous over the years, and I appreciate every single one. If I had received money for every thank-you or acknowledgment, I might have made a decent living from the time I’ve invested. But making money or collecting recognition was never why I started doing this.

I built Big Bear because I wanted to support an incredible community and help people install and use self-hosted applications more easily.

I spent years writing Dockerfiles, scripts, and configurations by hand. I manually updated Docker images one version at a time, tested deployments, fixed problems, and repeated that process over and over.

I even took things further by creating a YouTube channel to help people learn how to install and use these applications.

I didn’t need AI to do any of this. I learned how to do it myself, and I have years of GitHub history and public YouTube videos documenting that work. Today, I use AI because it saves time, not because I don’t know how to develop software.

You seem to be overlooking the years of work that went into Big Bear before your app store existed.

Discovering applications

How exactly do you expect app-store maintainers to discover new projects?

Are we supposed to magically know every open-source application that exists?

We discover projects through Reddit, GitHub, other app stores, community discussions, user requests, and upstream developers. That’s how I’ve discovered software for years, and you’ve openly acknowledged doing the same thing.

The applications you’ve mentioned are publicly discoverable through their upstream projects or other community resources.

If someone sees an application in another store, visits its upstream repository, and creates their own deployment configuration, why would discovering that application automatically entitle the other store’s maintainer to credit?

I’ve never encountered a general requirement in open-source licensing or copyright law that someone must receive attribution simply for introducing another developer to a publicly available application.

Original code, documentation, and other protected contributions are different. I respect those contributions and their licenses.

But discovering an application doesn’t make you its owner.

Think about what you’re proposing. Would IceWhale need to acknowledge every person or website that helped it discover a project? Would every software developer have to document the entire chain of people who introduced them to an idea?

Where would that end?

I also want to be clear about the October applications. That batch involved a Zima catalog-gap comparison to identify applications missing from Big Bear. I’ve never had an issue discovering applications through other stores, and I don’t consider that something to hide.

The question is whether anyone’s original implementation was improperly copied, not where an application was first discovered.

Here’s something else I find troubling about your accusations. Since this dispute began, I’ve examined how many other projects and app stores use Big Bear’s work. I’ve found numerous examples of our configurations, scripts, and generated files being reused elsewhere.

Some developers credit Big Bear. Others don’t.

I’ve never felt the need to track those developers down and publicly accuse them of stealing from me merely because they benefited from my work. That’s part of what makes the open-source community valuable.

The personal attacks

You’ve questioned my abilities, accused me of lying, mocked my work, and called me names: “What a loser” and “self obsessed and childish.” You also brought this dispute to me on Discord. In this thread, you said you’d sent one short message. Later that same day, after posting that, you posted this in my Discord:

The sender’s Discord profile, username hsinghhira, linking to your site:

You then publicly criticized me for banning you.

Big Bear Discord is a community I’ve built and maintain. I’m happy to receive constructive criticism, discuss technical issues, and help people resolve problems. But I’m not obligated to host someone who is publicly calling me a thief and insulting me.

Disagreeing with my work is one thing. Making repeated personal attacks is another.

If I were acting as a moderator here and any member spoke to another the way you’ve spoken to me, I would have stepped in. Personal attacks don’t belong in any community. I’ve held back because I’m a party to this dispute.

But someone should have stepped in. “Stop lying,” “What a loser” and “self obsessed and childish” are still up in this thread, and no moderator has addressed any of them. When personal attacks go unchecked, they escalate, and that’s a big part of how this thread got where it is.

What has hurt the most

And now I want to address something that has bothered me even more than the accusations themselves.

I’ve spent years helping hundreds, if not thousands, of people throughout the open-source, CasaOS, and ZimaOS communities.

I’ve answered questions, troubleshot problems, helped people install software, created Docker images, written scripts, developed applications, maintained repositories, and published tutorials. I’ve also spent my own time moderating and helping people right here in this community.

I’ve invested thousands of hours of my own time and considerable personal resources into helping people, asking for very little in return. I’ve always tried to be professional while doing it.

I’ve helped people I didn’t know, people who were just getting started, and people who needed assistance getting their systems working. I’ve never kept score or expected anyone to repay me.

I did those things because I enjoy helping people and because I believe that’s what a community should be about.

And what has genuinely hurt me throughout this situation is how few people from that same community have spoken up while I’ve been repeatedly accused of stealing and personally insulted.

It hurts that so many people I’ve helped over the years haven’t spoken up. People I’ve spent my own time helping, sometimes for hours, without ever asking for anything in return.

That hurts, and I would be lying if I said otherwise.

I’m not asking anyone to blindly defend me, take my side without evidence, or give me special treatment because I’ve been around longer.

I’m asking people to stand up for fairness, respectful treatment, and the principle that serious accusations should be backed by actual evidence.

If someone were publicly treating another contributor this way, I would hope the community would insist on those same standards.

I understand that not everyone wants to get involved in a disagreement. Some people may not have seen the discussion, and others may have been waiting for IceWhale to respond. I respect that. But understanding why someone might remain silent doesn’t mean that silence isn’t disappointing.

When you’ve spent years helping others without expecting anything back, and then find yourself in a situation where you could use a little support, the silence is difficult to understand.

Why I’m stepping away

This entire experience has made me seriously reevaluate where I’m investing my time and energy.

I didn’t make this decision lightly, and I didn’t make it until IceWhale responded. I waited for that response before deciding anything. I’ve supported the CasaOS and ZimaOS platforms with a huge amount of my time for years, and after reading it, I don’t feel that support has been appreciated.

I’ve spent years giving my time, knowledge, and resources to people and communities because I believed in what we were building together.

I still believe in open source, and I still enjoy helping people. That hasn’t changed.

But I don’t feel that same consideration, appreciation, and respect in this community anymore. There’s a difference between contributing freely because you love what you do and feeling like your contributions have simply become something everyone expects.

I’ve never required anyone to pay for my open-source or community work. Big Bear’s app stores and scripts have been free to use, and I’ve never expected recognition or special treatment.

But I don’t think expecting a little fairness and support when your integrity is being publicly questioned is asking too much.

Working on this 365 days a year has become a burden, and the stress of all this hasn’t been healthy for me. So I’m taking a much-needed break from open source and putting my time into other projects, where the work is appreciated.

To be clear, you didn’t run me off. This thread opened my eyes to how much of my life this work has been taking, and to how little that has counted when it mattered.

That doesn’t mean I’m turning my back on open source or the people who have supported Big Bear. It means I’ve thought seriously about how I’m spending my time, and I’m putting it where it’s valued.

I don’t believe contributing for years makes me more important than a newcomer. Everyone deserves respect, regardless of how long they’ve been involved. But I do believe that the time, effort, and contributions people have freely given to a community should count for something when their integrity is publicly questioned.

And I think communities need to consider something else. What happens when established contributors who have spent years giving their time freely become discouraged because personal attacks and unsupported accusations are allowed to dominate discussions? Doesn’t that also risk driving contributors away?

You repeatedly talk about the motivation of smaller app-store maintainers. I understand that concern. But what about the people who have already spent years contributing? Don’t their time, effort, and willingness to continue helping the community matter too?

Respect has to work both ways.

I have nothing against you maintaining your own app store. I genuinely encourage people to build their own projects, contribute to open source, and share their work with others. Big Bear offering the same upstream applications never erased your work.

You say you want respect for your time and effort.

So do I.

Stepping back isn’t an admission of anything. The record below shows what happened.

The technical record

You’ve asked me to answer publicly, so here it is, point by point. Big Bear’s repositories are private now, so links to them won’t open. Instead I’ve attached ente-signed-proof.zip. It holds the two commits GitHub created and signed on July 7, plus the Ente file from each. A short script checks GitHub’s signature and the file hashes, so anyone can confirm the dates and contents without access to my repositories and without trusting me.

Short version: Ente was requested, built and published by Big Bear on July 7, six weeks before your ZimaAppStore repository was created, and our passwords, converter output and description later showed up in yours. Our Stoat follows upstream and ran when I tested it. The October apps were found through a catalog gap check and other sources and built from upstream, with every developer credited.

I’ve also noticed that your own Ente configuration contains distinctive values and metadata conventions that were publicly documented in Big Bear before they appeared in your published repository.

Here is what happened, in order.

What the record shows

It started with a request. On June 30, 2026, a Big Bear user asked us to add Ente Photos (issue #2416):

A week later, we built it. On July 7, the Ente pull request (#2469) was opened at 21:21 UTC and merged at 21:41 UTC. GitHub created and signed the merge commit, b5be2ec3, at 21:41:30 UTC, so the time doesn’t depend on anyone’s clock. Our tooling then synced the app out to the CasaOS store, and GitHub signed that commit, 3ce769d1, at 21:48:44 UTC.

Both signed files already set the database password to one beginning change-me-qE7Y and the MinIO password to one beginning change-me-minio-vH3p. They’re on lines 21 to 26 of the merged file in the zip.

When Big Bear publishes an app for CasaOS, our converter script, convert-to-platforms.sh, writes a description for every environment variable in a set format: Container Variable: ENTE_DB_HOST, Container Variable: ENTE_DB_PORT, and so on. Nobody types those by hand. The script generates them, and they start on line 40 of the signed CasaOS file.

Six weeks later, your store appeared. GitHub records your ZimaAppStore repository as created at 05:23 UTC on August 20, and Ente is in its very first commit: First · HSinghHira/ZimaAppStore@b6bfca4 · GitHub

That Ente has the same two passwords from our July 7 merge, word for word. It also has our converter’s output: Container Variable: ENTE_DB_HOST and the lines after it, the same text our script writes. Ente is the only app in your store that ever had those lines. On September 15, they were removed.

But not everything was removed. Your Ente also carried our app description, word for word: “Ente is a self-hosted, end-to-end encrypted platform to store, share, and rediscover your photos and videos across all your devices.” We published that sentence on July 7. It’s on line 212 of the signed CasaOS file.

On September 15 it stayed, and it went into your new EnteGarage and EnteSeaweedFS apps as well. It’s still in your ZimaAppStore today: ZimaAppStore/Apps/Ente/docker-compose.yml at f188681795ed58b96ab66923722445d1d612342c · HSinghHira/ZimaAppStore · GitHub

The encryption keys and image digests match too, but I’m not counting them. The keys are Ente’s own published defaults, and anyone pinning those images that week would get the same digests. The passwords, the converter text and the full wording of that description are different. They’re specific to Big Bear, and Big Bear published them first. Before Big Bear’s repositories went private, a GitHub code search for that full sentence found it only in Big Bear’s own repositories. The copy in your file is linked above.

Then came your explanation. You’ve said you built Ente in May or June in a repository called CasaOSApps, which you later deleted. I’m not saying that repository never existed. But GitHub returns a 404 for it, and I can’t verify what was in it or when. The earliest record of those values is Big Bear’s July 7 merge, signed by GitHub.

Then came Stoat. You said both of our Stoat apps fail the same way, so I tested both on November 2 and again on November 3 with Docker 29.8.2 and Compose v5.5.0. I used our apps/stoat/docker-compose.yml at commit 6a77f10 and your Apps/StoatChat/docker-compose.yml at commit 9e4685a. The only changes were local ports, no host ports for LiveKit, local data folders on yours, and running our web image as linux/amd64 because it has no arm64 build.

Ours came up cleanly: all 17 services, with 15 running and 2 one-time setup jobs finished. The API answered through Caddy, account creation and login worked, and the WebSocket connected with the login token. Yours never got that far. Every Stoat backend service (api, events, autumn, january, gifbox, crond, pushd and voice-ingress) crash-looped on startup with missing field url, an error that comes from your own Revolt.toml. They behave differently because they are different configurations.

So here is where the record stands. Ente was requested from Big Bear, built by Big Bear, and published by Big Bear on July 7. Six weeks later it showed up in your first commit with our passwords, our script’s output, and our description, and that description is still in your store today. And your claim that both Stoats fail the same way doesn’t hold up: yours crash-looped, and mine started and worked when I tested it.

So the claim that I copied your Ente is wrong, and the files show it.

Your latest questions

You’ve asked how Big Bear’s apps were developed, so here are direct answers.

You asked why I haven’t responded. I did, right here. On November 1, the day you opened this thread, I answered in posts 4 and 7 with the Git history and the Ente pull request, and I answered your GitHub issue the same day. Those repositories are private now, so the signed proof is attached instead.

The 22 apps. The list came from an AI-assisted Zima catalog gap comparison, plus Reddit, GitHub, blog posts and AI-assisted web searches, as I said above. Each Big Bear configuration was then written against the project’s own upstream Compose files and documentation. Finding apps in a batch isn’t the same as copying configurations.

Stoat. You said the original developer only provides a basic Compose file and leaves the supporting services to whoever deploys it. That isn’t the case. Stoat’s official self-hosted repository ships the full stack: api, autumn, caddy, createbuckets, crond, database, events, gifbox, january, livekit, minio, pushd, rabbit, redis, voice-ingress and web: self-hosted/compose.yml at 4394499561b05142872d80562daaa3ecf489e49b · stoatchat/self-hosted · GitHub

Big Bear’s Stoat uses those services, plus one config helper for LiveKit, because it follows upstream.

Variables and secrets. The variables in Big Bear’s apps follow each project’s own documentation and .env examples.

Default secrets. CasaOS and ZimaOS install the values written in an app’s Compose file, and there’s no way to require users to enter their own credentials before installing. WisdomSky documented this in July 2023: “The current implementation in CasaOS is that everything must be hard-coded into the docker-compose.yml and there’s no way for the user to provide these required information beforehand.” [Feature Request] Allow requiring user to fill-up custom environment variables before install · Issue #1248 · IceWhaleTech/CasaOS · GitHub

That request was merged into an older one that is still open today: [Feature Request] Variable input in Before Install Tips · Issue #1101 · IceWhaleTech/CasaOS · GitHub

That’s why community stores ship default values that users are expected to review and change. BookOrbit’s own documentation requires POSTGRES_PASSWORD, JWT_SECRET and SETUP_BOOTSTRAP_TOKEN and tells users to set their own long random values. You said SETUP_BOOTSTRAP_TOKEN isn’t needed because the app generates its own. BookOrbit’s code says otherwise. In production it refuses to start without one: “SETUP_BOOTSTRAP_TOKEN is required in production.” Its Compose file marks JWT_SECRET and SETUP_BOOTSTRAP_TOKEN as required too: bookorbit/server/src/config/env.validation.ts at 76450d6ddd2e2b94481695ce069cac1f6a5a59f3 · bookorbit/bookorbit · GitHub bookorbit/docker-compose.yml at 76450d6ddd2e2b94481695ce069cac1f6a5a59f3 · bookorbit/bookorbit · GitHub

Those variables are in Big Bear’s BookOrbit because upstream requires them. And the values were never the same. You said Big Bear’s version had the same hardcoded token as your first one, but none of Big Bear’s BookOrbit values have ever appeared in your BookOrbit. Big Bear’s JWT_SECRET begins cd94b64e, and yours never did.

Shipped defaults are meant to be replaced, and making that easier for users is worth doing. The goal is for every install to end up with its own credentials, without hiding them from the person who installed it. When an app refuses to start on a placeholder, shipping one makes users set their own value. That’s how Big Bear updated Yuvomi when its maintainer raised this on October 25, within two days.

What maintaining Big Bear involved. Big Bear has never been just one app store. It has been a catalog of more than 490 apps, maintained since 2023, that I converted and published for six platforms: CasaOS and ZimaOS, Portainer, Dockge, Runtipi, Cosmos and Umbrel. It came pre-added to ZimaOS, so it ran on a very large number of systems, most of them owned by people who just wanted their apps to keep working.

At that scale, every decision was a tradeoff. I didn’t get to ask only whether a change was better in theory. I had to ask what it would do to everyone already running that app, and how many people it would leave confused or locked out. That’s the part of this work that doesn’t show up in a Compose file.

If something broke, I heard about it. You’ve suggested Big Bear’s apps don’t work and aren’t tested. With a store that came pre-added to ZimaOS, a broken app doesn’t go unnoticed. When something doesn’t work, people come straight to me on GitHub, Discord and YouTube. If Big Bear’s apps were as broken as you claim, I’d have had a flood of community members telling me so. The next point shows how quickly that happens: a change that only delayed updates brought hundreds of support requests. That’s the side of this work you aren’t seeing.

Why changes take care. Every change has to work for existing installs, not just new ones. Changing a shipped secret can break an install or lock someone out of their own data, which is why the Yuvomi update tells people with existing installs to keep their current database key when they update, because a changed key stops the database from opening. I’ve learned this the hard way. I once set Big Bear to wait three days before taking a new app release, so broken updates would get caught before they reached anyone’s server. It was a sensible safety measure. But users noticed their apps weren’t updating right away, and I got hundreds of support requests asking why. I removed the delay. A change that’s safer on paper doesn’t help if thousands of people experience it as something broken.

The same goes for credentials. When a password wasn’t easy to find, the first support request I got was “where is my password?” That’s why Big Bear kept defaults visible in the app settings, with install notes telling users to change them, so people can find and change their credentials without opening a support request.

Screenshots. None of the October apps includes screenshots, so none uses anyone else’s.

Credit to original sources. Every one of those apps names its upstream developer in its metadata, for example trackie-nz, Harsh Shah, useindelible and stoatchat.

The “bigbear-” names. Prefixing app IDs, service names and AppData folders is namespacing. It keeps Big Bear apps from colliding with other stores’ apps and containers on the same machine. It’s a practical convention, not vanity.

Staff, pre-installation and visibility. I’m speaking here as Big Bear’s developer, not for IceWhale. Questions about which stores come pre-installed and what standards IceWhale expects are theirs to answer, and I won’t answer for them. But IceWhale already gives independent stores visibility. Its Awesome Third-party Stores page lists community stores for anyone to import, including Play AppStore, Lintuxer’s store and Big Bear, and describes itself as “a community discovery page, not a formal endorsement list”: Community App Stores for ZimaOS: Third-Party App Collections | Zimaspace Docs

These lists are open source, and anyone can propose a store. The CasaOS list has received pull requests from ten different community members since 2023: Pull requests · IceWhaleTech/Awesome-CasaOS · GitHub

Big Bear started out the same way. It was seven weeks old when IceWhale added it to that list in September 2023, next to the other community stores: History for content/3rd-party-app-stores/list.md - IceWhaleTech/Awesome-CasaOS · GitHub

Your requests

A technical review. The evidence is attached. The Ente record above is backed by commits GitHub signed, and the attached file lets anyone check them without access to my repositories or having to trust me.

Removing the apps. I’ve stepped back from the store for the reasons I gave above, not because of this request. Nothing posted here shows that any of those apps were copied, and they were built from their own upstream projects.

My staff role. That’s IceWhale’s decision, not mine.

This is my last word on it

I won’t be reviewing any more material from you, and I won’t be continuing this conversation. The record is here for anyone who wants to check it. I’ve saved copies of this thread, your posts, your repositories, and everything referenced here, so if anything is edited or deleted, I still have it. If the accusations can’t be backed up, I think they should be corrected wherever they’ve been repeated.

Evidence

Because I’m also a community moderator, I’m speaking here as the developer of Big Bear, not on behalf of IceWhale. Any moderation decisions about this dispute should be handled without me.

Oh, well, you finally came out of your cupboard. Glad to see you’ve decided to respond. It’s certainly a long reply. Let’s address the actual points without going around in circles.

  1. The Discord ban

You’ve conveniently shown a screenshot of my second account, but you’ve left out the fact that you banned my first account when I was asking questions without insulting you. I have screenshots of that conversation too, and I’ll share them here.

You’re presenting this as though I was banned purely for personal attacks. That leaves out the earlier context and the fact that I initially tried to discuss my concerns with you directly.

  1. Ente Photos

You keep repeating that Ente was your work because your repository has the earliest verifiable public commit. I’ve already explained that I previously worked on Ente in my old CasaOSStore repository around May or June. Unfortunately, I deleted that repository, so I cannot use it to establish the timeline.

However, there is another detail worth examining. Your original Ente configuration used MinIO, which was also the S3 service I used in my earlier implementation. MiniO is no longer available. You updated your configuration only two days ago, when I pointed that in this very thread. That timing deserves clarification.

  1. Stoat Chat

You claim your Stoat installation worked and mine did not. I tested your version too, and it did not work for me.

  1. BookOrbit and SETUP_BOOTSTRAP_TOKEN

You say BookOrbit requires SETUP_BOOTSTRAP_TOKEN in production and use that to dismiss my explanation. I disagree with your conclusion about how the application handles this token.

  1. The 22 applications

You say the October batch came from a catalog-gap comparison, Reddit, GitHub and other sources. I understand that developers discover projects through many sources. I have never claimed that discovering an upstream application gives me ownership over it.

My concern is about the configurations, specific values, supporting services and other details that appeared across multiple applications. You added 22 applications in one batch, and those applications were already available in my store.

That coincidence alone does not prove copying. However, it is reasonable to ask for a closer comparison when multiple specific similarities appear together. Saying that you used AI-assisted searches and a catalog comparison explains how you selected the applications. It does not, on its own, explain every similarity I raised. There is no way you found Trackie on your own.

You have now provided a detailed explanation of your process. I still believe the individual examples deserve an independent technical review.

  1. Your GitHub contributions and years of work

I am not denying that you have contributed thousands of hours to open source. I am not saying you lack development experience, and I have never claimed that building Big Bear from scratch was a small task.

But years of contributions do not automatically answer questions about a specific configuration. Your GitHub activity is evidence of your work across projects. It does not independently establish who created every disputed line of code or configuration.

When someone questions a particular piece of work, the most useful response is to address the evidence for that work. Listing contributions and years of service does not settle the technical question.

This is one reason I called your earlier responses self-focused. You repeatedly brought the discussion back to how much you have done and how little appreciation you feel you have received. That may explain how you feel, but it does not resolve the allegations.

  1. The community and people who did not defend you

You say you are hurt that more people did not stand up for you. That is your feeling, and you are entitled to it.

However, community members are not obligated to publicly support either side of a dispute. Some people may not have enough information to reach a conclusion. Others may prefer to stay out of it.

Gelbuilding did engage with the discussion and acknowledged your contributions. So the suggestion that nobody stood up for you is not entirely accurate.

Asking people to defend you while accusing me of seeking sympathy creates the same issue you are criticising. The discussion should be about the evidence, not about how many people support either of us.

  1. Your decision to step away from Big Bear

You say you are stepping away because you no longer feel your contributions are appreciated. That is your decision, and I will not tell you how to manage your time or projects.

But your decision to step away does not prove or disprove the allegations. Neither does it make the original questions disappear.

I also find it difficult to understand why the repositories became private during this dispute, particularly when you are asking everyone to examine the technical record. You may have your reasons, but making the repositories private limits what the community can independently review. The signed files you attached may help with the Ente timeline, but they do not replace access to the broader history of the disputed applications.

  1. Why I contacted you in the first place

I initially tried to contact you directly because I wanted to discuss my concerns with you. You banned my account, and the discussion moved into the public forum.

You now say you will not review any more material or continue the conversation. That is your choice. But please do not present the entire situation as though I immediately launched a public attack without first trying to contact you.

I accept that some of my later comments were personal and unnecessarily insulting. I could have expressed my frustration more constructively. However, that does not mean the technical concerns should be ignored or dismissed.

  1. What I am actually asking for

I have never said you should not maintain an app store. I have never said that you cannot use upstream projects, discover applications through other stores, or create your own deployment configurations.

I am asking for the disputed configurations to be examined independently, for the specific similarities to be addressed, and for IceWhale to make a clear decision about the standards expected of someone whose store receives official visibility and whose role includes community moderation.

If the evidence establishes that my work was copied without appropriate acknowledgment, I expect that to be addressed. If the evidence establishes that I was mistaken about particular examples, I am prepared to acknowledge that too.

That is what a fair review should look like.

You have said this is your last word on the matter. Fine. I will not force you to continue the conversation. But saying the discussion is over does not make every question answered, and publishing a long response does not automatically make every claim conclusive.

I am willing to have my claims examined against the evidence. I expect the same standard to apply to yours.

Let IceWhale review the facts and provide an outcome. That would be far more useful than turning this into a discussion about who has made more contributions, who has received more thanks, or who has more people supporting them.

Truth be told I don’t use any of either stores apps and after this public exhibition of petty name-calling and rants I don’t see doing so in the future.

I wish you guy just could bury the hatchet, but most likely the line has been crossed already, both of your work is very valuable for ZimaOS and whatever the output of this argument will be I want to say thank you for your work.

HSingh, mate, I think enough is enough now.

I’m speaking as a community moderator here, and I think this discussion has gone on far longer than it should have.

You’ve raised your concerns, presented your evidence, and BigBear has responded in considerable detail. Both sides have had plenty of opportunities to explain their positions.

Nobody is dismissing the time and effort you’ve put into your App Store, and nobody is saying your concerns shouldn’t be taken seriously.

But this constant back-and-forth isn’t helping anyone anymore. It’s becoming exhausting for the community, and we’ve already seen the damage it’s causing.

BigBear has now announced he’s stepping back from his work, which is disappointing for everyone who relies on his contributions.

You’ve also acknowledged that some of your comments became personal and unnecessarily insulting. I appreciate you recognising that, but personal attacks have no place in this community, regardless of who they’re directed at.

If there are still technical concerns or evidence that needs reviewing, then let IceWhale handle that through the appropriate channels. There’s no need to keep repeating the same arguments publicly.

And this applies to everyone, not just you.

We’re here to help ZimaOS grow, support users and encourage developers to contribute. We’re not here to watch two valuable contributors tear each other apart.

I think other community members have made it pretty clear that they’re tired of this situation too.

So I’m asking everyone involved to please stop the personal arguments and allow IceWhale to deal with any outstanding concerns.

Let’s get back to what this community is supposed to be about: helping each other and making ZimaOS better.

Enough is enough, guys. Let’s move forward.

One quick answer from me:

I requested on both stores bookorbit in the same time I also requested more on big bear.
And there added it!

I just see today that discussion and must say pls be kind to each other I love both stores and I use both.
So thank you to you two for maintaining and adding cool stuff and to take requests.

Its sad that big bear closes now but its you dessision.
So on that point thank you for years of effort and work.
I will spoke for every community user. You work make that whats open souce for, let the peaple use nice other open souce apps and let discover them. BIG Thank you for you time and effort.

If I had money what I bearly have to live I would give it to you and I saw them on the Big Bear repo an thoght when I have a better Job I give some to that guy to appreciate that work. Now its to late.
I must deal with it.

Final words pls be nice and pls not assulting each other we are an nice open souce community and it is that open. We use reuse other work and compose files are often identical and thats the hole point of them so the app works on every container the same.

Thanks and have a hopefully nice day.
Sorry I cant be silent I must resonse on them.

Wow, I just read through this thread. How embarrassing! I generally don’t use the app stores. I write my own compose files and manage them myself. Given this embarrassing show I can’t see that changing anytime soon either. However, I do recognize the value these app stores provide, especially, for people who are not qualified Linux server administrators. I spend a good portion of my time helping inexperienced users to get their home servers up and running, and advocating for privacy / data sovereignty. Going forward, I know which app store I will NOT be recommending to those users.

After reading through this entire thread I cannot understand what @HSinghHira is thinking here. You don’t have some kind of exclusivity over a Docker configuration by adding it to your store. These are independent projects, and other curators are allowed to add those apps to their stores too. It is not “Stealing” your work in the slightest. I am genuinely at a loss reading through your comments that are oozing entitlement.

I cannot 100% endorse @dragonfire1119 response, but I also can’t say for certain I would have acted any differently had I been levied with the same baseless accusations. Overall, I just hope the community does better moving forward. This was not it.

Edit: I will also mention that it makes me sad to see BigBear stepping back from his app store. I have recommended it to a lot of people who have gotten lots of use from it, and it think it is a genuine benefit to the whole community. I do completely understand, however, the sentiment after what has happened here.

Wow, really sad to see this. I ended up moving on from CasaOS/ZimaOS a while back because I personally didn’t like the direction it was taking, but back when it launched, it was my gateway into Docker and I learned so much from @dragonfire1119 along the way.

I have to agree with @benhaube here. I really don’t get the drama. If someone were monetizing proprietary code, that’d be one thing. But sharing Docker compose files across community app stores? That’s literally how open source homelab setups work. Most of us pull configs from everywhere to build our own setups.

Huge thanks for all the help and work you put in over the years, @dragonfire1119 Enjoy some well-deserved time away from the keyboard!

I’ll be honest: I’ve followed BigBear’s work for years, and when I saw the title of this thread my blood boiled. I nearly closed it without reading any further. I’m glad I didn’t, because underneath the title there is a real issue worth discussing. It just isn’t theft.

Nothing here was stolen. The applications belong to their upstream developers and are published under open-source licences precisely so they can be packaged and redistributed. A Compose file is largely functional configuration dictated by upstream documentation, so similar files across stores are to be expected. Spotting an app in another catalogue and building it from upstream is discovery, not ownership. And neither store charges anyone anything.

So I’d respectfully ask that the thread title, and any remaining references to theft, be edited. That word damages everyone involved and the community as a whole, and it has already cost us a long-standing contributor.

The real issue is attribution and curation. Credit to upstream developers should be consistent, and a nod to fellow curators when their catalogue is used for discovery is a courtesy that costs nothing. More importantly, this thread exposed flaws in both stores that come from moving too quickly: secrets shipped as fixed public values (including encryption keys), and apps that don’t start cleanly. That isn’t a character flaw in anyone. It’s what happens when one or two volunteers carry hundreds of apps on their own.

That’s why I think the answer sits with IceWhale. I see two coherent options:

  1. Curate. IceWhale runs its own store, accepts contributions from community maintainers, and publishes only after review against a simple checklist: no shared secrets, pinned images, upstream credit, a tested install.
  2. Open up. No store gets privileged placement. Users can add any GitHub store they like, with a clear notice that third-party stores are unvetted.

Given that ZimaOS is built around making things as easy as possible, I believe option 1 is the natural fit. One-click installs only stay easy if someone stands behind what’s being clicked. Progress on CasaOS issue #1101 (letting users fill in variables before install) would also remove most of the hardcoded-secret problem at its source.

Thank you to both BigBear and HSingh for the work you’ve put in. I hope we can keep this conversation on the standards rather than on each other.