From: "Nguyễn Gia Phong" <cnx@loang.net>
To: "Adolfo Santiago" <epoch@adol.pw>, <~cnx/loang@lists.sr.ht>
Subject: Re: AI scrapping bot ban
Date: Thu, 17 Aug 2023 17:30:11 +0900 [thread overview]
Message-ID: <CUUOGO9BK2TM.9XKM0TV7IDAT@guix> (raw)
In-Reply-To: <ohf2h2ji46eis3wp6tvmbdtncfluld4p2stl33agl7zczdhaoe@4cyllbaxehva>
[-- Attachment #1: Type: text/plain, Size: 1150 bytes --]
On 2023-08-16 at 16:19+02:00, Adolfo Santiago wrote:
> I write to the list in order to propose a wide-block
> of AI bots scrapping anything from loang services.
>
> Recently I came accross the GPTBot[1] documentation,
> where it says how to block the bot
> if you don't want it to scrap anything.
>
> The idea would be to not allow the bot the posibility
> of scrapping anything, regardless of the loang service(s)
> you're using.
>
> [1]: https://platform.openai.com/docs/gptbot
Thanks for reminding me of this!
I saw this on fedi a few days ago and forgot about it.
Personally I don't object scraping, but given OpenAI
doing it to mass-launder copyright and its oligopolistic power,
I am open to blocking it server-wide.
Until anyone wants to opt into the OpenAI dataset,
I will set up the firewall to block its IP ranges.
Do note that whatever one puts out to the public interwebs
will eventually be scraped. A resource could be mirrored
by a archiving initiative and OpenAI could scrape from there.
Other big tech corps are also building their own LLM.
Think of the block more as an act of protest, if anything.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 248 bytes --]
prev parent reply other threads:[~2023-08-17 8:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-16 14:19 Adolfo Santiago
2023-08-17 8:30 ` Nguyễn Gia Phong [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CUUOGO9BK2TM.9XKM0TV7IDAT@guix \
--to=cnx@loang.net \
--cc=epoch@adol.pw \
--cc=~cnx/loang@lists.sr.ht \
/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.
Code repositories for project(s) associated with this public inbox
https://trong.loang.net/nixos-conf
https://trong.loang.net/phylactery
https://trong.loang.net/site
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 IMAP folder(s).