I guess #Servo is now the only serious browser engine taking a stand against slop, even mentioning ethical issues?

[lumi@snug.moe]

@valpackett thank you @servo ​​

this policy was a big reason why i decided to contribute (and hopefully will contribute more in the future)

[darkling@mstdn.social]

@valpackett Isn't servo written mostly in rust, which uses LLVM, which is accepting LLM contributions?

It's tainted all the way down at this point. Even the tools to make the tools have gone.

[jackwilliambell@rustedneuron.com]

@valpackett

Waterfox.

> https://www.waterfox.com/blog/no-ai-here-response-to-mozilla/

[zbrown@floss.social]

@darkling @valpackett the GCC ecosystem isn't tainted yet that I've heard of, and there are several efforts to support rust in various ways through that, rustc itself also has non-LLVM-backend projects I believe, so there may yet be a future, perhaps

[zbrown@floss.social]

@jackwilliambell @valpackett …is not slop free

[jackwilliambell@rustedneuron.com]

@zbrown

Source?

[zbrown@floss.social]

@jackwilliambell https://github.com/BrowserWorks/waterfox/blob/current/CONTRIBUTING.md#managing-upstream-changes

[jackwilliambell@rustedneuron.com]

@zbrown

I wouldn't call that authoritative. But I'll concede they could be picking up slop from the Mozilla codebase. Do we know which Moz files contain slop and if they have been included in WF builds?

(Not asking you to look or trying to put you on the spot, just asking if you already know.)

In any case, I'm mostly happy WF are not including AI tech in the browser. I don't want slop code either, but Servo isn't ready for prime time yet.

[zbrown@floss.social]

@jackwilliambell Mozilla has specifically gone for a policy of not tagging slop commits as slop, thus I don't think we can plausible know what is or isn't tainted, so short of Waterfox becoming a hard fork and dropping every Mozilla commit from the last idk year or so there's really no reason to believe it's not made it in.

Which isn't to say Waterfox isn't preferable for the reasons you say, and servo certainly isn't ready yet, but unfortunately ‘slop free’ it isn't.

[usul@piaille.fr]

@valpackett would be nice if servo would compile on BSDs.

#runbsd

[moses_izumi@fe.disroot.org]

@valpackett @angelastella
Hit me up when someone does a Servo-powered fork/replica of the Seamonkey suite.
Every "anti-Google" web browser ought to ship a HTML editor and website publishing wizard, along with a built-in RSS reader (the USENET and IRC clients are also neat, but I never used them).

The Firefox OS experiment would probably have worked if Mozilla was still playing the "full-fat internet suite" game.