• ciferecaNinjo@fedia.io
    link
    fedilink
    arrow-up
    5
    arrow-down
    1
    ·
    edit-2
    1 year ago

    Normal users don’t have these issues.

    That’s not true. Cloudflare marginalizes both normal users and street-wise users. In particular:

    • users whose ISP uses CGNAT to distribute a limited range of IPv4 addresses (this generally impacts poor people in impoverished regions)
    • the Tor community
    • VPN users
    • users of public libraries, and generally networks where IP addresses are shared
    • privacy enthusiasts who will not disclose ~25% of their web traffic to one single corporation in a country without privacy safeguards
    • blind people who disable images in their browsers (which triggers false positives for robots, as scripts are generally not interested in images either)
    • the permacomputing community and people on limited internet connections, who also disable browser images to reduce bandwidth which makes them appear as bots
    • people who actually run bots – Cloudflare is outspokenly anti-robot and treats beneficial bots the same as malicious bots

    There are likely more oppressed groups beyond that because there is no transparency with Cloudflare.

      • ciferecaNinjo@fedia.io
        link
        fedilink
        arrow-up
        1
        arrow-down
        2
        ·
        edit-2
        1 year ago

        Not exactly. !showerthoughts@lemmy.world was a poor choice, as is:

        • !showerthoughts@zerobytes.monster ← Cloudflare
        • !showerthoughts@sh.itjust.works ← Cloudflare
        • !showerthoughts@lemmy.ca ← Cloudflare
        • !showerthoughts@lemm.ee ← Cloudflare
        • !hotshowerthoughts@x69.org ← Cloudflare, and possibly irrelevant
        • !showerthoughts@lemmy.ml ← not CF, but copious political baggage, abusive moderation & centralized by disproportionate size

        They’re all shit & the OP’s own account is limited to creating a new community on #lemmyWorld. !showerthoughts@lemmy.ml would be the lesser of evils but the best move would be create an acct on a digital rights-respecting instance that allows community creations and then create showerthoughts community there.

        (EDIT) !showerThoughts@fedia.io should address these issues.