https://discord.cloudflare.com logo
Join Discord
Powered by
# workers-discussions
  • h
    You can choose not to use it, but it will still be there
  • h
    If you are going to self host in the name of privacy, don’t use an external DNS resolver
  • c
    it does increase privacy by a lot.
  • c
    imagine if 10 people are requesting DNS queries from self-hosted server that will fetch them from external one.
  • c
    external one would never know those 10 people
  • c
    basically a proxy
  • h
    I mean, if you go through the effort of setting up a DNS server, might as well do it right
  • c
    I mean you always need to start somewhere, the same for a meta search engine, now just using BIng API in the future once and if I get more funding can also make own indexing, spider and at the end become our own search engine
  • c
    the same as Brave search
  • d
    with the biggest respect, you can't rebuild the internet and build an equivalent service of everything from the ground up oh and expect users to switch to it (other than if you force them in a corporate environment), maintain all of them, and make the service(s) profitable too...
  • c
    I know I can't compete with internet, but I can make something "similar" and kinda useful.
  • c
    For example Rabbit Net
  • c
    user can write their own config and you can access his "website" thru terminal example: rabbitnet hisdomain.com and you will get his "website"
  • d
    to actually innovate and not recreate, you need to put in a lot of engineering effort - entire teams work on a single product for years and years
  • c
    so you can navigate thru terminal like he made it
  • c
    and execute the commands that he wrote inside terminal
  • c
    and you can also hide some ester-eggs and it can be fun
  • c
    Everything I made is open source, so I can build only a small house and community would start building the city.
  • c
    I still didn't officially completed the college, so I have time building random projects 15 hours per day.
  • d
    Why is my Worker still responding on 
    http://example.com:2086
    even after I set the route to be 
    https://*.example.com/*
    ?
  • c
    Like why is it running when the port is defined?
  • d
    like why is it serving requests to that when I've clearly only binded my route to https?
  • c
  • d
    mind if I give you the domain to try?
  • d
    Copy code
    Published email-worker (1.51 sec)
  https://*.email.example.com/* (zone name: example.com)
Current Deployment ID: asdf-asdf-asdf-asdf-asdf
  • c
    Sure but I don't know what I have to offer. What does it show in the dashboard under the route for the worker?
  • d
  • d
    okay I see your hi
  • d
    I saw it on 
    https://test.email.ai.moda/hi
  • c
    Oh that wasn't me
1...228722882289...2509Latest