So your app is for people who aren’t willing to pay other companies for their private hosting feature… and your plan is to charge those people money?
And your app is for people not technical enough to build or move or even iframe these pages themselves, and your plan is for those people to be messing with DNS records?
What is the point of posting on here if you are going to be so passive aggressive in most of your responses. I just picked this one to reply to, but it could have been any of them.
You built something that will obviously raise questions around pricing and copyright, but you are dismissive of any feedback.
If you want people to invest money and time in your product and risk availability of their content, you should at least have some ready answers to these obvious questions.
Bubble, Webflow and Notion will not be happy that your service takes their custom domain revenue.
How much are you prepared to deal with the legal and technical roadblocks they might try to throw at you? (have you talked to a lawyer? which country? botnets?)
I have mixed feelings about this. It seems wrong to strip the branding and has obvious copyright issues. However, there really is a use case for using web services to build content that you want to host elsewhere. APIs and iframes help but you can only take that so far. For me the bundled hosting in a service is cheap and not particularly valuable. The user experience the author gets is what makes it valuable. Having domains that work across services in a supported way would be super useful.
> You have your web pages and forms built on other platforms like Bubble, Webflow, Notion, etc. And want to move those webpages under your own "domain name" without using their "custom domain" pricing plans.
Don’t use their pricing plan, use ours instead? Seems unethical even if technically possible.
Physical analogies are never great for digital, but they’re selling movie tickets at the back door of someone else’s theater.
Will definitely be interesting to see how these services react to having their lunch stolen out from under them. Maybe they’ll be small enough to slip through.
Website of the friend of mine got copied this way. Weird traffic was detected with some analytics tools and then we thought:
1. Why would anybody do anything like that?
2. How do we report it to all the hosters / domain providers we can reach?
With (2) the whole thing might be too problematic to maintain, especially isolating good users from bad guys. Really curious how you're going to solve it, please write more.
I see an ethical aspect of this in data portability: it should be possible to create your web site in one service and then migrate it to another one for hosting (it's your content) whenever you like. I wouldn't proxy all requests through though, so at least add a cache, use the original service as a static-site generator, or do an honest import of the data to your service?
If the service you are proxying offers authentication based on token within cookies, does that mean that you will have access to tokens hosted on the client side? Should you disclose a potential security risk to them (same for credentials interception)?
And your app is for people not technical enough to build or move or even iframe these pages themselves, and your plan is for those people to be messing with DNS records?
Bold strategy.