is this okay to tell me: “>just build your own website man just build your own payment…
- User
is this okay to tell me: “>just build your own website man
just build your own payment processor man
just build your own DDOS Mitigation man
just build your own DNS servers man
just build your own domain registrar man
just build your own ISP man
just build your own internet protocol man” because things keep going wrong with things not made by me. like my sites keep being taken down and stuff.
- Assistant
The suggestions you've received to "just build your own" for the various services and infrastructure mentioned are likely offered in jest, or as a hyperbolic way to express frustration with relying on third-party providers. Building and running all of these systems yourself is an enormous task that generally isn't feasible for an individual or even a small organization because of the technical complexity, cost, and time investment required for each one.
Here's a brief overview of what building each component entails, to emphasize the magnitude of such undertakings:
-
Build your own website: This is the most reasonable suggestion on the list. Many individuals and businesses build their own websites using content management systems (CMS) like WordPress, Drupal, or custom-coded solutions.
-
Build your own payment processor: Creating a payment processor involves dealing with financial regulations, security issues, transaction handling, and partnerships with banks or credit card companies. It's a complex endeavor typically undertaken by well-funded companies.
-
Build your own DDoS mitigation service: DDoS mitigation requires a robust infrastructure with a high bandwidth capacity, sophisticated filtering mechanisms, and constant monitoring. Again, this is usually the domain of specialized companies.
-
Build your own DNS servers: While setting up a DNS server is technically feasible, running it reliably under the pressure of real-world use, with considerations for security, load balancing, and fault tolerance, is another matter.
-
Build your own domain registrar: Being a domain registrar requires accreditation by the Internet Corporation for Assigned Names and Numbers (ICANN) or a similar regional authority. This is a rigorous process with many policy and technical requirements.
-
Build your own ISP: Starting an ISP is another high-cost venture requiring infrastructure setup (cabling, networking equipment, data centers), regulatory approvals, and service management systems.
-
Build your own internet protocol: Developing a new internet protocol means not only the technical design but also achieving widespread adoption, which is a massive hurdle given the need for interoperability across the global internet.
Instead of attempting to do all of this yourself, you should look into why your sites keep being taken down. Dealing with takedowns could be due to hosting policy violations, security issues, or legal problems, among other reasons. Investigate each situation to understand the cause and then consider the following steps:
-
Improve Security: Ensure that your website is secure and not being taken down due to vulnerabilities or attacks. Regular security audits and employing services from reputable security companies can assist in this area.
-
Legal Compliance: Make sure that your content and business practices comply with the laws and regulations applicable to your jurisdiction and hosting provider's terms of service.
-
Reliable Hosting: Choose a web host with a good reputation for uptime and customer support.
-
DDoS Protection Services: Use third-party DDoS protection services that specialize in mitigating such attacks.
-
Backup and Redundancy: Have backups of all your data and use DNS failover or load balancing solutions to avoid downtime.
Consider seeking help from professionals who have experience in dealing with such matters to get personalized advice and solutions. Working with existing service providers and leveraging their expertise is usually the most practical and cost-effective approach.
-