• 1 Post
  • 28 Comments
Joined 1 year ago
cake
Cake day: June 15th, 2023

help-circle



  • We’re growing the Mozilla Ads product team, passionate about display advertising in Mozilla products that is privacy-respecting and values-aligned. You will be one of the lead engineers that will craft, build, and be responsible for the core systems, both front-end and back-end, that support advertising in clients (Firefox, MDN, Pocket, Fakespot, etc). You and your team will be the domain guides when it comes to advertising, providing direction and shepherding to various product teams across Mozilla.

    Ofc some reading between the lines is needed, they’re not going to just blatantly say something they know will be incredibly unpopular this early.

    And like I said, its just another on a pile of mounting evidence of a year of bad decisions


  • Not in the browser. From web pages sure, but it sure as hell sounds like they’re going to shove ads in the browser like MS has been testing in the start menu. Once that starts who knows, maybe they’ll have their own little Chrome manifest v3 rollout that breaks adblocking for webpages too.

    Based on this and the past year of “mistakes” it’s sure looking more and more like they’re trying to push ahead on the enshittification path.

    If they’re so desperate to find other sources of income why does the Mozilla CEO not take a pay cut out of that 10 million/year


  • We’re going to explore doing so in an organic method across our products using the methodology that big tech is generating money, but with a Mozilla spin.

    Hm yes, the “we’re built different so we won’t be affected by enshittification” option

    that support advertising in clients (Firefox, MDN, Pocket, Fakespot, etc)

    Ah, the “Mozilla Spin” is to put fucking ads in Firefox, got it.











  • Straw Man Fallacy: A straw man fallacy occurs when someone misrepresents an opponent’s argument to make it easier to attack or refute. Instead of addressing the actual issue, the person creates a distorted version of the argument that is easier to discredit.

    This is what you have done in every single reply you made when I have made it quite clear that this is about the migration being an urgent security issue that the cyber security community at large has been calling attention to.

    You avoid all the core points I make and distort them into trivial things that you can easily argue, like the fact that you “Don’t code C much and use Rust occasionally”. It’s irrelevant to the actual arguments and you use it to dismiss the real core issues AKA a Straw Man fallacy

    You have failed to argue in good faith and are actually a part of the problem. Good job!


  • Ah I see your default is to sprinkle in a bit of argumentum ad logicam and add a dash of straw man at the end

    Your statement comes across as the migration from C/C++ is more of an upgrade for new features and increased “ease of use” rather than an urgent security issue when it definitely is. It’s more than just a case of a couple of experts and some articles, you’ve got multiple governmental and NGOs like The NSA, The Whitehouse, CISA, DARPA all calling for the migration away from C/C++ to memory safe languages

    https://devops.com/darpa-turns-to-ai-to-help-turn-c-and-c-code-into-rust/

    “DARPA, the Defense Department’s (DOD) R&D agency, will lean on emerging AI capabilities in a new program to deal with the costly and time-consuming challenge of rewriting C and C++ code to Rust in a move designed to meet the push for federal agencies and private organizations to adopt memory-safe programming languages.

    https://www.theregister.com/2023/12/07/memory_correction_five_eyes/

    "CISA, in conjunction with the National Security Agency (NSA), FBI, and the cyber security authorities of Australia, Canada, the United Kingdom, and New Zealand, said its call for better memory safety follows from its Secure By Design recommendations – endorsed by all of these cyber authorities.

    “With this guidance, the authoring agencies urge senior executives at every software manufacturer to reduce customer risk by prioritizing design and development practices that implement MSLs [memory safe languages],” the report argues."

    ~

    "CISA suggests that developers look to C#, Go, Java, Python, Rust, and Swift for memory safe code.

    “The most promising path towards eliminating memory safety vulnerabilities is for software manufacturers to find ways to standardize on memory safe programming languages, and to migrate security critical software components to a memory safe programming language for existing codebases,” the CISA paper concludes."