• 12 Posts
  • 77 Comments
Joined 1 year ago
cake
Cake day: July 23rd, 2023

help-circle


  • It basically is saying that if you have more money then you have more “votes”.

    That’s simply true. It doesn’t do anyone any good to disregard the facts.

    Or to put it in another way: If you have more money you matter more.

    That abstraction doesn’t help much. And first of all, it’s more accurate to derive the statement “If you have more money then you have more influence”.

    It’s still a shitty status quo, but it is what it is. The worse thing you can do is tell people not to boycott shit products on the basis of rejecting reality. It’d be like telling people not to vote in elections because their vote is a drop in the ocean.

    Some people vote for democrats, then they cancel their own vote by getting their internet service from Spectrum, buying fuel from Chevron for their car, shipping their packages using FedEx, getting their phone service from AT&T, banking at PNC Bank, flying on Boeing planes, shopping on Amazon, doing their web searches on a Microsoft syndicate’s site (e.g. DDG), buying Sony devices… etc. They either have no clue that most of their voting is actually for the republicans, or they think that drop-in-the-ocean vote that comes once in 4 years somehow carries more weight than the daily votes they cast with reckless disregard.

    Greg Abbott’s war chest is mostly fed by oil companies. If you buy fuel for a car, you help Greg Abbott and other republicans. And if you buy from Chevron, you give the greatest support to republicans (Chevron is an ALEC member).




  • Ending capitalism is not the /only/ way. Within a capitalistic system, you can boycott shit. Most consumers are pushovers but it doesn’t have to be that way. I’m boycotting hundreds of shitty companies. Off the top of my head:

    • Amazon
    • Cloudflare
    • Microsoft
    • Facebook
    • Google
    • Apple
    • (surveillance advertisers in general)
    • (all closed-source s/w)
    • HP
    • Proctor & Gamble
    • Unilever
    • all ALEC members (American Express, Anheuser Busch, Boeing, CenturyLink, Charter Communications, Chevron, FedEx, Motorola, PNC bank, Sony, TimeWarner)
    • many shitty banks
    • Paypal
    • AT&T
    • GMA members (Coke, Pepsi, Kraft - Heinz, Kellogg’s, General Mills, McCormick, Hormel, Smucker)
    • BetterThanCashAlliance.org members (visa, mastercard, unilever) – war on cash
    • Bayar-Monsanto
    • Dupont
    • Hershey
    • Nestlé
    • Exxon/Mobil
    • Comcast
    • Koch
    • Home Depot
    • Lowes
    • …etc

    Those are all shitty companies that significantly worsen the world. Giving money or data to any of them contributes to enshitification of the world.

    Of course it’s an option to stop supporting assholes. Become ethical. Be the change you want to see.





  • Better or worse depends on who you ask.

    I boycott Cloudflare and I avoid it. Some CF hosts are configured to whitelist Tor so we don’t encounter a block screen or captcha. For me that is actually worse because I could inadvertently interact with a CF website without knowing about the CF MitM. I want to be blocked by Cloudflare because it helps me avoid those sites.

    The CF onion (IIUC) cuts out the exit node which is good. But CF is still a MitM so for me that’s useless.

    Some users might not care that CF has a view on all their packets - they just don’t want to be blocked. So for them the onion is a bonus.


  • W.r.t CSAM, CF is pro-CSAM. When a CF customer was hosting CSAM, a whistleblower informed Cloudflare. Instead of taking action against the CSAM host, CF doxxed the ID of the whistleblower to the CSAM host admin, who then published the ID details so the users would retaliate against the whistleblower. (more details)

    There is no way to “disable” cloudflare if an instance has chosen to use it. It will sit between you and the server for all traffic.

    Some people use CF DNS and keep the CF proxy disabled by default. They set it to only switch on the CF proxy if the load reaches an unmanageable level. This keeps the mitm off most of the time. But users who are wise to CF will still avoid the site because it still carries the risk of a spontaneous & unpredictable mitm.















  • I think this project has some tools that might automate that:

    https://0xacab.org/dCF/deCloudflare

    They ID and track every website that joins #Cloudflare. It’s a huge effort but those guys are on top of it. A script could check the list of domains against their list. There is also this service (from the same devs) which does some checks:

    https://karma.crimeflare.eu.org:1984/api/is/cloudflare/html/

    but caveat: if a non-CF domain (e.g. example.tld) has a CF host (e.g. somehost.example.tld), that tool will return YES for the whole domain.

    Manually adjusting availability is a can of worms that I don’t want to open

    I would suggest not bothering with any complex math, and simply do the calculation as you normally do but then if a site is Cloudflare cap whatever the calculated figure is to 98%. Probably most (if not all) CF sites would be 100% anyway, so they would just be reduced by 2%. Though it would need to be explained somewhere – the beauty of which would be to help inform people that the CF walled garden is excluding people. Cloudflare’s harm perpetuates to a large extent because people are unaware that it’s an exclusive walled garden that marginalizes people.


  • If the message is edited for typos/grammatical errors, then there’s really no need for a notification as the message displays the posted time in italics (e.g., ✏ 9 hours ago).

    I’m not sure why the relevance of the posted time in this scenario, but indeed I agree simply that typos need not generate an update notice, in principle.

    If the message is so reworked as to say something else, “Bob” (your example) should do the right thing and post a new, separate reply to “Alice” in the same thread, donchathink?

    This requires Bob to care whether Alice gets the update. Bob might care more about the aesthetics, readability, and the risk that misinfo could be taken out of context if not corrected in the very same msg where the misinfo occurred. If I discover something I posted contained some misinfo, my top concern is propagation of the misinfo. If I post a reply below it saying “actually, i was wrong, … etc”, there are readers who would stop reading just short of the correction msg. Someone could also screenshot the misinfo & either deliberately or accidentally omit Bob’s correction. So it’s only sensible to correct misinfo directly where it occurred.

    I get what you’re saying though, that there should be some real integrity toward post/reply history, like diff maybe.

    It would be interesting to see exactly what Mastodon does… whether it has an algorithm that tries to separate typos/grammer from more substantive edits. I don’t frequently get notices on Mastodon when someone updates a status that mentions me, so I somewhat suspect it’s only for significant edits.

    (update) one simple approach would be to detect when a strikethrough is added. Though it wouldn’t catch all cases.