• 1 Post
  • 112 Comments
Joined 1 year ago
cake
Cake day: July 2nd, 2023

help-circle
  • Remember when China told Google to censor web search results and Google said, “No. How about we show those search results with notes that they were censored and why since the sites will be blocked anyway?”, and China was like, “You can’t show them at all.”, and Google said, “Fuck you. We’d rather lose access to the Chinese market than violate our principles.”, and instantly shut down any service in China that would require censorship or disclosing private data and closed all Chinese offices working on any of those technologies?

    What a time we’re living in.











  • Google used to allow third party payments. It turned out to be expensive.

    This is like forcing Walmart to let companies take up space in their stores rent free and process their own payments. When it turns out a bunch of those little stores are stealing personal information and credit card info and money, those customers go to the Walmart service desk and when Walmart employees shrug and say, “I don’t know what the fuck those guys are doing. You see, we give you the big store, but once you step into that smaller store hey are you falling asleep?” it’s national news and it’s Walmart’s fault and they’re called to testify in front of congress to get yelled at for not protecting customers. This is a weird precedent.

    I don’t agree with Google’s decision to force payments through Google. Since congress and courts and media expect Google to police the safety of all apps downloaded from the Play Store, I can’t think of a better solution that also respects privacy, isn’t, “We’ll monitor everything every app does, but pinky swear it’s just so we can make sure they’re being nice to you.”








  • I agree for inline code comments, like, “# Save the sprocket”, right above the line that saves the sprocket. Does this include documentation? Because when I see a prepareForSave function that references 10 other functions and I just want to know, “Is this mutating and how is it preparing for save and when should I call it?”, having the author spend 15 seconds telling me is less time consuming than me spending 5 minutes reading code to find out. Anyone who has read API docs has benefited from documentation.


  • Last I checked, Firefox had also been switching to Manifest v3 because they’re also combating the tide of add-ons that pretend to do something useful, but actually steal your information. They asked uBlock at least a few times how they could build Manifest v3 in a way that’d be compatible. Instead of the browser asking about each URL, thereby giving the add-on access to personal information, uBlock could tell the browser what to block. uBlock’s answer was always, “No. That’s not good enough. Give the add-on access to URLs.” It seemed to me like every time uBlock was approached, they turned to news sites to complain and IIR, the feature that would have given uBlock some functionality was removed from v3 because if nobody’s going to use it, why build it?

    I wonder, now that uBlock has conflated the discussion of, “How much should extensions be able to see and modify URLs you’re visiting?”, with, “v3 is a war on ad blockers!”, how quickly Firefox will move forward with v3, if at all.