• 6 Posts
  • 1.9K Comments
Joined 8 months ago
cake
Cake day: November 8th, 2023

help-circle
  • But the alt text generation already leverages a self-hosted LLM. So either Mozilla is going to cook in hundreds of extra megabytes of data for their installs, or people with accessibility issues are going to have to download something extra anyway. (IIRC it’s the latter).

    We could talk all day about things that Mozilla could add out of the box that would make the user experience better. How about an ad blocker? They can be like Opera, Brave, Vivaldi, even the most ambitious Firefox fork LibreWolf.

    But for some reason they went with injecting something into Firefox that nobody was asking for, and I don’t think it aligns at all with the average Firefox users needs or wants. Normies don’t use Firefox. They use a browser that doesn’t raise “switch to Chrome or Edge” messages. And if there was some subset of Firefox users who were begging Mozilla for AI, I never saw them. Where were they?





  • If it was truly opt-in, it could be an extension. They should not be bundling this with the browser, bloating it more in the process.

    AI already has ethical issues, and environmental issues, and privacy issues, and centralization issues. You technically can run your own local AI, but they hook up to the big data-hungry ones out of the box.

    Look at the Firefox subreddit. One month ago, people were criticizing the thought of adding AI to Firefox. Two months ago, same thing. Look at the Firefox community. See how many times people requested AI.








  • The trouble with “wait and see” is that people will often forget what we were waiting for.

    Speaking of which, do you remember FakeSpot? That was Mozilla’s first foray into directly selling private data to ad companies. At the time, a lot of people said, “they might allow it now, but let’s wait and see.”

    And today, Mozilla FakeSpot continues selling data to ad companies.








  • You assumed and misinterpreted everything you could assume and misinterpret in order to paint standard notes in the best possible light.

    the old approach wasn’t very secure or scalable?

    No, the older approach was more scalable, and they made it more difficult to do

    95-99% of the Javascript that has ever run in your browser is open source frameworks or packages

    No, I was not talking about frameworks.

    Your response was so offbase and full of assumptions that I simply edited my original post.

    All FOSS projects have a team of dictators

    And the Standard Notes team makes a lot of bad choices that make self-hosting harder.

    “Just fork it and make your own” is a Hail Mary response… Because most people cannot.



  • I don’t like to speculate, but I think it was mental illness, which may have started during the CopperheadOS days (the predecessor to Graphene).

    Unfortunately, that does call into question the recommendations on that page, which I already had a little worry about because Vanadium is their thing, of course they’re going to recommend it.

    But I do genuinely want to know how significant of a risk this lack of isolation and sandboxing causes.