Closed cosark closed 8 months ago
Thanks for offering this @cosark.
I'm not going to reject this out-right, but I'm going to let it sit for a while since there are a few amber flags here that make me wary of linking to the service from out docs, and I don't want to risk leading users to something potentially sketchy. The flags include:
I think the community would appreciate you being objective. And you're at liberty to close this if you feel like your community is better served by your censorship to protect them, as a benevolent big brother of sorts. I respect whatever decision you make.
If you google "one-click deploy [app name in question]" you'll see this is a common practice.
I'm not questioning that, but I get wary of applications listed under the heading of being "open source" when they are not, especially by hosting providers where those differences can matter.
Do you have any logic that would connect AI generated content with the negative characterization you're making? Or is this something emergent from your own personal emotions?
Both I guess. There is an obvious recent trend of AI being used for grifts, and that has emotionally made me wary of projects heavily leaning on AI. Again, not saying your service is a grift, but I'd be in a default wary position until other factors can provide confidence.
I think the community would appreciate you being objective.
I think they'd also appreciate not being led into potentially sketchy services by us accepting any link added via PR.
The apps you referenced have 100s of contributors. You're suggesting the public doesn't have the right to self host them? That's demonstrably false.
I don't know what you think a grift would entail here. It's a straightforward hosting service.
The apps you referenced have 100s of contributors. You're suggesting the public doesn't have the right to self host them? That's demonstrably false.
I never stated that. I said they're not open source, which is the heading they're put under on your website. Both projects set additional limitations via their licenses which moves them outside the common definition (OSD) of open source. These conditions could have implications on you providing them as a hosting provider.
You seem to have some confusion. If what you think is true were actually true, then other repos would agree with you. But nobody agrees with you. Those licenses apply to users of the app. For example, if a user (at RepoCloud or AWS or anywhere) decided to white label one of those into a private SaaS - that might violate certain terms. This is a hosting service, no different than any other.
Added a link to 1-click deploy template at repocloud.io efficient cloud hosting service