From: Shane Mulligan <mullikine@gmail.com>
To: rms@gnu.org
Cc: Eli Zaretskii <eliz@gnu.org>, Stefan Kangas <stefan@marxist.se>,
emacs-tangents@gnu.org, Jean Louis <bugs@gnu.support>
Subject: Re: Help building Pen.el (GPT for emacs)
Date: Sat, 24 Jul 2021 15:14:20 +1200 [thread overview]
Message-ID: <CACT87Jpn1iXAuikenrn2-_1sdg5-4c=vkMeBO_4EoazcYE-W1w@mail.gmail.com> (raw)
In-Reply-To: <CACT87Jpbm=wwenh-RUE0vNkQzNXjjUMVd=hjToiZHj9FGW7axA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 4856 bytes --]
Proprietary code from within the M$ ecosystem is uninspired and bad code by
comparison. Open source code is the gold mine so M$ will not like being
told they cannot use open source to compile codex. It's a complete r*pe of
open source. GPT is trained on public language and language belongs to
people generally, not some select group. It's not meant to be a tool for
controlling people. GPT is literally the soul of a billion people and
should be public domain and not feared by GNU but instead rescued. Sorry
for the rhetoric!
On Sat, Jul 24, 2021 at 2:34 PM Shane Mulligan <mullikine@gmail.com> wrote:
> This is why the technology is a bit like a
> personal Google search, Stackoverflow, which
> you can store offline because it's an index of the internet that is
> capable of reconstruction.
>
> But it's not limited to code generation. Codex
> is nothing. Emacs + GPT would carve a large
> piece out of M$.
>
> Codex is a model trained for the purpose of
> generating code, but GPT models will become
> abundant for all tasks, including image and
> audio synthesis and understanding.
>
> Emacs is a complete operating system.
> VSCode is geared towards programming.
>
> Emacs can do infinitely more things with GPT
> than VSCode can because it's holistic.
>
> Even the 'eliza' in emacs can pass the turing
> test with GPT. GPT can run sequences of commands in emacs to automate
> entire workflows with natural language.
>
> But the future is in collaborative GPT.
>
> The basis/base truth would become versions of
> LMs or ontologies.
>
> Right now that's EleutherAI.
>
> Shane Mulligan
>
> How to contact me:
> 🇦🇺 00 61 421 641 250
> 🇳🇿 00 64 21 1462 759 <+64-21-1462-759>
> mullikine@gmail.com
>
>
> On Sat, Jul 24, 2021 at 2:10 PM Shane Mulligan <mullikine@gmail.com>
> wrote:
>
>> It's a bit like whitewashing because it's
>> reconstructing generatively by finding
>> artificial/contrived associations between
>> different works that the author had not
>> intended but may have been part of their
>> inspiration inspiration, and it compresses the
>> information based on these assocations.
>>
>> It's a bit like running a lossy 'zip' on the
>> internet and then decompressing
>> probabilistically.
>>
>> When run deterministically (set the temperature of GPT to 0), you may
>> actually
>> see 'snippets' from various places, every time, with the same input
>> generating
>> the same snippets.
>>
>> So the source material is important.
>>
>> What GitHub did was very, very bad but they
>> did it anyway.
>>
>> That doesn't mean GPT is bad, it just means
>> they zipped up content they should not have
>> and created this language 'index' or ('codex'
>> is what they call it).
>>
>> What they really should do, if they are honest
>> people, is train the model on subsets of
>> GitHub code by separate licence and release
>> the models with the same license.
>>
>> Shane Mulligan
>>
>> How to contact me:
>> 🇦🇺 00 61 421 641 250
>> 🇳🇿 00 64 21 1462 759 <+64-21-1462-759>
>> mullikine@gmail.com
>>
>>
>> On Sat, Jul 24, 2021 at 1:14 PM Richard Stallman <rms@gnu.org> wrote:
>>
>>> [[[ To any NSA and FBI agents reading my email: please consider ]]]
>>> [[[ whether defending the US Constitution against all enemies, ]]]
>>> [[[ foreign or domestic, requires you to follow Snowden's example. ]]]
>>>
>>> > > That's not what happens with these services: they don't _copy_ code
>>> > > from other software (that won't work, because the probability of
>>> the
>>> > > variables being called by other names is 100%, and thus such code,
>>> if
>>> > > pasted into your program, will not compile). What they do, they
>>> > > extract ideas and algorithms from those other places, and express
>>> them
>>> > > in terms of your variables and your data types. So licenses are
>>> not
>>> > > relevant here.
>>>
>>> > According to online reviews chunks of code is copied even verbatim
>>> and
>>> > people find from where. Even if modified, it still requires licensing
>>> > compliance.
>>>
>>> From what I have read, it seems that the behavior of copilot runs on a
>>> spectrum from the first description to the second description. I
>>> expect that in many cases, nothing copyrightable has been copied, but
>>> in some cases copilot does copy a substantial amount from a
>>> copyrighted work.
>>>
>>> --
>>> Dr Richard Stallman (https://stallman.org)
>>> Chief GNUisance of the GNU Project (https://gnu.org)
>>> Founder, Free Software Foundation (https://fsf.org)
>>> Internet Hall-of-Famer (https://internethalloffame.org)
>>>
>>>
>>> --
Shane Mulligan
How to contact me:
🇦🇺 00 61 421 641 250
🇳🇿 00 64 21 1462 759 <+64-21-1462-759>
mullikine@gmail.com
[-- Attachment #2: Type: text/html, Size: 10603 bytes --]
next prev parent reply other threads:[~2021-07-24 3:14 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CACT87JohxuswvDcqGOiQR7BrHoqJFG252QD6XjEuAPU2HSuWOw@mail.gmail.com>
[not found] ` <CADwFkm=cN4W0Mgo_hYgwWgddoe=cXj5+WYJWnAHZmmd+rd7gKw@mail.gmail.com>
[not found] ` <E1m4YYb-0005Ds-GJ@fencepost.gnu.org>
[not found] ` <CACT87JqMZ+pbVDQ-5gZHMsGcfm04CoeKZn6sY5yy+1rnxCimOQ@mail.gmail.com>
[not found] ` <83im1948mj.fsf@gnu.org>
[not found] ` <CACT87JrCAi3Umdke6gL+_W_7k2j+21jsuT=1hq5kyOx19L2x+A@mail.gmail.com>
[not found] ` <CACT87Jo41S2FJKxfPs0qP=qkXvwvcc0xnf1X6oEkjuhmAJ6w3A@mail.gmail.com>
[not found] ` <YPO+bAMpqMhxDBxU@protected.localdomain>
[not found] ` <83lf642jeh.fsf@gnu.org>
[not found] ` <CACT87JriMaF1kFjEE_8=8FEQpAi6sxr3x3vZT3rafjY=4mQgZg@mail.gmail.com>
2021-07-19 17:00 ` Help building Pen.el (GPT for emacs) Jean Louis
2021-07-23 6:51 ` Shane Mulligan
2021-07-23 10:12 ` Jean Louis
2021-07-23 10:54 ` Eli Zaretskii
2021-07-23 11:32 ` Jean Louis
2021-07-23 11:51 ` Eli Zaretskii
2021-07-23 12:47 ` Jean Louis
2021-07-23 13:39 ` Shane Mulligan
2021-07-23 14:39 ` Jean Louis
2021-07-26 0:16 ` Richard Stallman
2021-07-26 0:28 ` Shane Mulligan
2021-07-30 3:20 ` Shane Mulligan
2021-07-30 6:55 ` Jean Louis
2021-07-23 19:33 ` Eli Zaretskii
2021-07-24 3:07 ` Jean Louis
2021-07-24 7:32 ` Eli Zaretskii
2021-07-24 7:54 ` Jean Louis
2021-07-24 8:50 ` Eli Zaretskii
2021-07-24 16:16 ` Jean Louis
2021-07-24 16:44 ` Eli Zaretskii
2021-07-24 18:01 ` Jean Louis
2021-07-25 1:09 ` Richard Stallman
2021-07-24 1:14 ` Richard Stallman
2021-07-24 2:10 ` Shane Mulligan
2021-07-24 2:34 ` Shane Mulligan
2021-07-24 3:14 ` Shane Mulligan [this message]
2021-07-24 6:49 ` Eli Zaretskii
2021-07-24 7:33 ` Jean Louis
2021-07-24 8:10 ` Eli Zaretskii
2021-07-24 8:21 ` Jean Louis
2021-07-24 8:35 ` Jean Louis
2021-07-24 8:59 ` Eli Zaretskii
2021-07-24 16:18 ` Jean Louis
2021-07-24 16:45 ` Eli Zaretskii
2021-07-24 17:57 ` Jean Louis
2021-07-24 18:15 ` Eli Zaretskii
2021-07-24 7:41 ` Philip Kaludercic
2021-07-24 7:59 ` Eli Zaretskii
2021-07-24 9:31 ` Philip Kaludercic
2021-07-24 11:19 ` Eli Zaretskii
2021-07-24 14:16 ` Philip Kaludercic
2021-07-24 14:37 ` Eli Zaretskii
2021-07-24 14:49 ` Philip Kaludercic
2021-07-24 15:13 ` Eli Zaretskii
2021-07-25 1:06 ` Richard Stallman
[not found] ` <YN8bZEJAkWyQwjrB@protected.localdomain>
[not found] ` <CACT87JpAcUfuRB01CcnfbL4yCTPyDoiG_WOzzxVvAW7rhj0=Mw@mail.gmail.com>
2021-07-23 15:37 ` Jean Louis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CACT87Jpn1iXAuikenrn2-_1sdg5-4c=vkMeBO_4EoazcYE-W1w@mail.gmail.com' \
--to=mullikine@gmail.com \
--cc=bugs@gnu.support \
--cc=eliz@gnu.org \
--cc=emacs-tangents@gnu.org \
--cc=rms@gnu.org \
--cc=stefan@marxist.se \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).