Conversation

Notices

1. Embed this notice
   Servo (servo@floss.social)'s status on Tuesday, 08-Apr-2025 00:42:56 JST Servo

   Servo is considering:

   - allowing some AI tools for non-code contributions

   - allowing maintainers to use GitHub Copilot for some code contributions over the next 12 months

   These changes are planned to take effect in June 2025, but we want your feedback. More details:

   https://github.com/servo/servo/discussions/36379

   • Rich Felker and Haelwenn /элвэн/ :triskell: repeated this.
   • Embed this notice
     Rich Felker (dalias@hachyderm.io)'s status on Tuesday, 08-Apr-2025 00:42:55 JST Rich Felker

     in reply to

     @servo Very very bad idea and makes the whole project non FOSS. Rather it's an amalgamation of undocumented, undocumentable, plagiarized code of unknown provenance, attribution, and license. And likely buggy and full of vulns.

   • Embed this notice
     Ténno Seremél’ (tennoseremel@lor.sh)'s status on Tuesday, 08-Apr-2025 00:43:08 JST Ténno Seremél’

     in reply to

     @servo How are you going to handle copyright on such contributions?

   • Embed this notice
     happyborg (happyborg@fosstodon.org)'s status on Tuesday, 08-Apr-2025 00:43:33 JST happyborg

     in reply to

     @servo
     Relationally and technically IMO this is a bad move.

     It reduces the likelihood of me building with or donating to Servo for various reasons.

     Code is one of the least justifiable uses of LLMs, and then we have a plethora of ethical and potential legal problems needing to be worth any perceived benefits.

     Why risk such a great project for questionable benefits?

   • Embed this notice
     F4GRX Sébastien (f4grx@chaos.social)'s status on Tuesday, 08-Apr-2025 00:43:47 JST F4GRX Sébastien

     in reply to

     @servo boom. You're dead.

     Edit: Enshittified even before version 1. That was impressively fast.

   • Embed this notice
     Budsofstone (budsofstone@computerfairi.es)'s status on Tuesday, 08-Apr-2025 00:43:56 JST Budsofstone

     in reply to

     @servo the use of ai will piss a lot of people off myself included. This isnt a personal preference issue. Its a moral and quality control issue. If servo starts using and pushing LLM ai, I won't be using it and will tell others not to contribute or use it.

   • Embed this notice
     F4GRX Sébastien (f4grx@chaos.social)'s status on Tuesday, 08-Apr-2025 00:44:02 JST F4GRX Sébastien

     in reply to

     @servo Servo going open loop now?

     I hope all the negative feedback you're getting will drive you back to the setpoint: doing a proper alternative browser.

     Joke apart, AI suck. and you know it. So why ask?

   • Embed this notice
     emenel (emenel@post.lurk.org)'s status on Tuesday, 08-Apr-2025 00:44:21 JST emenel

     in reply to

     @servo 👎👎 this will only make the project less trustworthy, less robust, and less open. It will also make Servo far less sustainable in both technical/documentation and environmental impact. You will lose a lot of contributors and supporters, replacing them with dubious contributions.

   • Embed this notice
     silverwizard (silverwizard@convenient.email)'s status on Tuesday, 08-Apr-2025 01:11:18 JST silverwizard

     in reply to
     @servo I am hoping Servo doesn't crater its security in order to chase a trend
   • Embed this notice
     aburka 🫣 (aburka@hachyderm.io)'s status on Tuesday, 08-Apr-2025 02:16:36 JST aburka 🫣

     in reply to

     • Rich Felker

     @dalias @servo left a comment on the github proposal

   • Embed this notice
     Rich Felker (dalias@hachyderm.io)'s status on Saturday, 12-Apr-2025 01:37:10 JST Rich Felker

     in reply to

     • Erin 💽✨

     @erincandescent @servo I don't think that's a meaningful distinction. If you're letting people use this slop in working on the project, they're going to use all of its capabilities, and not going to be honest with themselves or others about where it crosses a vague line.

     Also you have to realize making this allowance radically changes who is going to participate. You're going to drive away everyone who it put off by the "AI" scams, and attract plagiarists excited about "AI".

   • Embed this notice
     Erin 💽✨ (erincandescent@akko.erincandescent.net)'s status on Saturday, 12-Apr-2025 01:37:13 JST Erin 💽✨

     in reply to

     • Rich Felker
     @dalias @servo "Use it only for things like auto-complete, small snippets and refactors; but not for full code generation."
     
     i.e. only for things which are so small as to be de minimis or for things which would be derivative works purely of existing Servo code
   • Embed this notice
     Rich Felker (dalias@hachyderm.io)'s status on Saturday, 12-Apr-2025 01:43:48 JST Rich Felker

     in reply to

     • Erin 💽✨

     @erincandescent @servo No, you just need to have project values that attract honest people and repel dishonest ones. What they're proposing is the reverse.

   • Embed this notice
     Erin 💽✨ (erincandescent@akko.erincandescent.net)'s status on Saturday, 12-Apr-2025 01:43:49 JST Erin 💽✨

     in reply to

     • Rich Felker
     @dalias @servo people who aren't going to be honest about it also aren't going to be honest about when they've just gone and plagiarised something.
     
     let's face it, if you want to protect against that, you've gotta run all contributions through the source code equivalent of TurnItIn