[email protected] wrote: > Rodrigo Arias <[email protected]> wrote: >> >Got inspired to do a little vibecoding on @dillo to see how hard it >> >would be to get native Mac menus. >> >> I'm afraid I won't read code aided or generated by a chatbot. It is also >> a legal liability as the license of that code is not clear. >> >> They are literally destroying whatever was that remained of the Web, >> causing many sites to stop working in Dillo due to the JS-walls. > > Strongly agree. I propose a small change to the website to clarify this > position for future contributors: > > --- a/dillo-browser.org.html Sat Nov 8 09:11:31 2025 > +++ b/dillo-browser.org.html Sat Nov 8 09:12:41 2025 > @@ -60,6 +60,7 @@ table { margin: 1.5em; } > <li>Helps authors to comply with web standards by using the > <a href="old/help/bug_meter.html">bug meter</a> > <img alt="Bugmeter icon" style="vertical-align:middle" > src="img/bugmeter.png">.</li> > + <li>100% human-made. No AI or LLM is used to create Dillo.</li> > </ul> > <p> > Read the <a href="user_help.html">user manual</a> to discover how to > use
I take such things too literally, I know, but FWIW to me this implies the project only accepts code that is verifiably human generated, which is hard to do. You'd need the maintainer watching over your shoulder while you write it or something. Something like "AI-generated code contributions are not accepted" would inform contributors without implying the ability to verify the unverifiable. _______________________________________________ Dillo-dev mailing list -- [email protected] To unsubscribe send an email to [email protected]
