Network Neutrality is back! Let´s make the technical aspects heard this time!
 help / color / mirror / Atom feed
From: le berger des photons <thejoff@gmail.com>
To: "Network Neutrality is back! Let´s make the technical aspects
	heard this time!" <nnagain@lists.bufferbloat.net>
Subject: Re: [NNagain] detecting GPT-generated text
Date: Fri, 22 Dec 2023 13:23:20 +0100	[thread overview]
Message-ID: <CAO-LeMwp+bcMtQ0y6JiEpdk=vRcoJ2riVecndjcQeVCH4Jjv2Q@mail.gmail.com> (raw)
In-Reply-To: <91B34F49-D567-4ED2-84CC-EFDBF9895725@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1135 bytes --]

cut out the middleman and eliminate the 30 page paper.  just keep the oral.

On Tue, Dec 19, 2023 at 9:49 PM Rich Brown via Nnagain <
nnagain@lists.bufferbloat.net> wrote:

> Sorry, OT: but I couldn't resist...
>
> On Dec 19, 2023, at 2:33 PM, Alexandre Petrescu via Starlink <
> starlink@lists.bufferbloat.net> wrote:
>
> I asked a few persons around how could one identify GPT-generated text?
>
>
> I recently heard a radio interview with a college professor who was
> changing his assignments (especially the standard 30-page paper) in the
> face of ChatGPT. His (semi-humorous) metric for detecting AI-generated
> content was the lack of spelling or grammar errors...
>
> Rich
>
> PS He did have a serious plan: ask each student to give a 15-minute
> presentation on the topic that would have been the subject of that 30 page
> paper. It takes the same time (or less!) to assess the work, and gives a
> personal connection with the students...
> _______________________________________________
> Nnagain mailing list
> Nnagain@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/nnagain
>

[-- Attachment #2: Type: text/html, Size: 2075 bytes --]

  reply	other threads:[~2023-12-22 12:23 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAJUtOOi7rSiPTFGVkadh4XPvFOnmzLidX5=7-LTJnoiyPauNag@mail.gmail.com>
     [not found] ` <A8DC9114A92F47D5AAE1D332B5E5007D@SRA6>
2023-12-13 22:38   ` [NNagain] [Starlink] FCC Upholds Denial of Starlink's RDOF Application Frantisek Borsik
2023-12-14  2:46     ` Robert McMahon
2023-12-14  6:11       ` Frantisek Borsik
2023-12-14 17:48         ` David Bray, PhD
2023-12-14 18:47           ` Frantisek Borsik
2023-12-14 18:51           ` Nathan Simington
2023-12-14 19:44             ` Frantisek Borsik
     [not found]             ` <f7d6522d-db06-4ee6-a814-76810ad01e1f@gmail.com>
     [not found]               ` <ZXxIdbzif5ogB0IQ@Space.Net>
     [not found]                 ` <02cc2879-ef99-4388-bc1e-335a4aaff6aa@gmail.com>
     [not found]                   ` <ZXxKMZ-pEbS4QAzW@Space.Net>
2023-12-15 12:46                     ` Frantisek Borsik
2023-12-15 13:24                       ` Gert Doering
2023-12-15 13:40                       ` Sebastian Moeller
2023-12-15 18:06                         ` David Lang
2023-12-15 18:51                           ` rjmcmahon
2023-12-15 19:13                             ` David Lang
2023-12-15 21:29                               ` rjmcmahon
2023-12-15 21:42                                 ` David Lang
2023-12-15 22:04                                   ` David Bray, PhD
2023-12-15 22:10                                     ` David Lang
2023-12-15 22:13                                       ` David Bray, PhD
2023-12-15 22:33                                         ` Kenline, Doug
2023-12-15 22:36                                         ` Dave Taht
2023-12-17 21:22                                           ` Tanya Weiman
     [not found]                                         ` <de59330f-e05a-4c2e-9d64-e2821f113e76@gmail.com>
2023-12-19 20:49                                           ` [NNagain] detecting GPT-generated text Rich Brown
2023-12-22 12:23                                             ` le berger des photons [this message]
2023-12-22 13:06                                               ` Rich Brown
2023-12-15 22:05                                   ` [NNagain] [Starlink] FCC Upholds Denial of Starlink's RDOF Application rjmcmahon
2023-12-15 22:13                                     ` David Lang
2023-12-15 22:26                                   ` Dave Taht
2023-12-16  4:16                                     ` David Lang
2023-12-16 17:30                                       ` rjmcmahon
2023-12-16 18:18                                         ` Dick Roy
2023-12-16 18:48                                         ` Robert McMahon
2023-12-16 21:44                                           ` Frantisek Borsik
2023-12-16 22:28                                             ` Robert McMahon
2023-12-17  0:25                                               ` Dave Taht
2023-12-23 21:17                                                 ` J Pan
2023-12-18  8:25                                               ` David Lang
2023-12-17  1:54             ` [NNagain] other fcc services at sea Dave Taht

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://lists.bufferbloat.net/postorius/lists/nnagain.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAO-LeMwp+bcMtQ0y6JiEpdk=vRcoJ2riVecndjcQeVCH4Jjv2Q@mail.gmail.com' \
    --to=thejoff@gmail.com \
    --cc=nnagain@lists.bufferbloat.net \
    --cc=thejoff@mail.com \
    /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