Re: FreeDOS caveats

Liste des GroupesRevenir à c misc 
Sujet : Re: FreeDOS caveats
De : nospam (at) *nospam* example.net (D)
Groupes : comp.misc
Date : 27. Apr 2024, 20:23:04
Autres entêtes
Organisation : i2pn2 (i2pn.org)
Message-ID : <aab90344-3cd1-657d-1fd6-c12d98aaefa0@example.net>
References : 1 2 3 4
On Fri, 26 Apr 2024, Ivan Shmakov wrote:

On 2024-04-25, Ben Collver wrote:
>
It looks as though some effort was put into composing this
message.  Nice work, assuming it is human generated.
>
When working time and again as a part-time university
lecturer, I'd typically feed bits of my students' works to
Duckduckgo to detect plagiarism.  Makes me wonder if this
approach can be adapted for detecting AI-generated texts.
Granted, it is not university level work or students, but what I do is to just compare students work. The AI-people more often than not, hand in the exact same source, same spelling, same variable names. That is enough proof for me to not pass them.
But sophisticated cheaters rewrite, and then it is of course a bit more difficult. In that case I do manage to catch them during code reviews when they cannot explain what they do or the algorithm.

Date Sujet#  Auteur
21 Apr 24 * Using FreeDOS In 202238Ben Collver
22 Apr 24 +* Re: Using FreeDOS In 202228Kyonshi
22 Apr 24 i`* Re: Using FreeDOS In 202227Ben Collver
23 Apr 24 i +* Re: Using FreeDOS In 202225Computer Nerd Kev
23 Apr 24 i i+* Re: Using FreeDOS In 20229Ben Collver
24 Apr 24 i ii+- Re: Using FreeDOS In 20221Computer Nerd Kev
24 Apr 24 i ii`* Re: Using FreeDOS In 20227Lawrence D'Oliveiro
24 Apr 24 i ii `* Re: Using FreeDOS In 20226Ben Collver
24 Apr 24 i ii  `* Re: Using FreeDOS In 20225Kerr-Mudd, John
24 Apr 24 i ii   +- Re: Using FreeDOS In 20221Dan Cross
25 Apr 24 i ii   `* Re: Using FreeDOS In 20223Lawrence D'Oliveiro
25 Apr 24 i ii    `* Re: Using FreeDOS In 20222Kerr-Mudd, John
26 Apr 24 i ii     `- Re: Using FreeDOS In 20221Lawrence D'Oliveiro
23 Apr 24 i i`* Re: Using FreeDOS In 202215candycanearter07
23 Apr 24 i i +* Re: Using FreeDOS In 20227Kerr-Mudd, John
23 Apr 24 i i i+* Re: Using FreeDOS In 20225Kerr-Mudd, John
26 Apr 24 i i ii`* Re: Using FreeDOS In 20224Andy Burns
26 Apr 24 i i ii +- Re: Using FreeDOS In 20221Ben Collver
26 Apr 24 i i ii `* Re: Using FreeDOS In 20222Ben Collver
27 Apr 24 i i ii  `- Re: Using FreeDOS In 20221Lawrence D'Oliveiro
23 Apr 24 i i i`- Re: Using FreeDOS In 20221candycanearter07
24 Apr 24 i i `* Re: Using FreeDOS In 20227Lawrence D'Oliveiro
24 Apr 24 i i  `* Re: Using FreeDOS In 20226Bob Eager
24 Apr 24 i i   `* Re: Using FreeDOS In 20225candycanearter07
24 Apr 24 i i    +- Re: Using FreeDOS In 20221Bob Eager
25 Apr 24 i i    `* Re: Using FreeDOS In 20223Lawrence D'Oliveiro
25 Apr 24 i i     `* Re: Using FreeDOS In 20222candycanearter07
25 Apr 24 i i      `- Re: Using FreeDOS In 20221Bob Eager
24 Apr 24 i `- Re: Using FreeDOS In 20221Lawrence D'Oliveiro
22 Apr 24 +* Re: Using FreeDOS In 20225John McCue
24 Apr 24 i`* Re: Using FreeDOS In 20224Lawrence D'Oliveiro
24 Apr 24 i `* Re: Using FreeDOS In 20223John McCue
24 Apr 24 i  +- Re: Using FreeDOS In 20221Scott Dorsey
25 Apr 24 i  `- Re: Using FreeDOS In 20221Lawrence D'Oliveiro
25 Apr 24 `* FreeDOS caveats4Ivan Shmakov
25 Apr 24  `* Re: FreeDOS caveats3Ben Collver
26 Apr 24   `* Re: FreeDOS caveats2Ivan Shmakov
27 Apr 24    `- Re: FreeDOS caveats1D

Haut de la page

Les messages affichés proviennent d'usenet.

NewsPortal