#Stackexchange just became a Cloudflare site, which means it’s now an exclusive resource and also everyone’s data including usernames & passwords are exposed to Cloudflare.

This is antithetical to the pro-privacy philosophies of the #Monero community. Please consider removing it from the sidebar or caution people about CF. Thanks.

  • soloActivist@links.hackliberty.orgOP
    2·
    10 months ago

    Some sites use CF DNS just to have the ability to spontaneously switch on the proxy at will. They tend to keep the proxy turned off but then when traffic peaks a bandwidth detection mechanism switches on CF proxying. The problem with that is users don’t know from one click to the next whether their traffic will be intercepted. It can happen at any moment. So the deCloudflare project treats CF DNS cases no different than always-proxying sites.

    So if you have no intention of using CF’s proxy, using a non-CF service would make more sense so your domains don’t get treated as CF. CF is not a good company to support anyway.

      • soloActivist@links.hackliberty.orgOP
        2·
        9 months ago

        i’m not the best person to ask since I’m not maintaining and domains myself right now. I thought porkbun.com looked like a good choice at one point. They announced that they were going to move to cloudflare (just for the management portal), which was quite off-putting nonetheless, but it looks like they did not follow through with that.

        EDIT-- I recently heard they are using CF for DNS and some people are avoiding #Porkbun for that reason.