From: Henning Hraban Ramm <texml@fiee.net>
To: ntg-context@ntg.nl
Subject: [NTG-context] Re: Offline documentations
Date: Mon, 2 Oct 2023 10:55:44 +0200 [thread overview]
Message-ID: <d0d94e28-fc7d-e3ad-064e-cd38cfb0a754@fiee.net> (raw)
In-Reply-To: <CACa+7H8gp2zwOAG4T2Dcn4ta5fxP-d5PJUCQZtamwUNw73Ju9A@mail.gmail.com>
Am 02.10.23 um 10:37 schrieb Juliano David Hilario:
> Also, if I were to do that, I might just make at the moment some sort of
> search engine, or grep it when I need something, then view whatever I
> need in the wiki. I'm just wondering if it's fine if I were to send many
> GET requests and obtain a copy of the wiki. Would that act like a DDoS
> attack?
For a DDoS attack you’d need more (for one, it’s not distributed, so at
most DoS). I assume it should be ok if you don’t do it too often (like
hourly).
And of course you’re expected to report wrong/outdated information and
to help with updating it.
Hraban
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2023-10-02 8:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CACa+7H8kYq4QtBnb-cJN2DQokYfYZddkqH5RpqNHzm-o_RT2_Q@mail.gmail.com>
2023-10-02 7:59 ` [NTG-context] " Juliano David Hilario
2023-10-02 8:24 ` [NTG-context] " Henning Hraban Ramm
2023-10-02 8:32 ` Juliano David Hilario
2023-10-02 8:37 ` Juliano David Hilario
2023-10-02 8:55 ` Henning Hraban Ramm [this message]
2023-10-02 9:07 ` Hans van der Meer via ntg-context
2023-10-02 15:57 ` Juliano David Hilario
2023-10-02 8:47 ` Henning Hraban Ramm
2023-10-02 8:57 ` Thomas A. Schmitz
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=d0d94e28-fc7d-e3ad-064e-cd38cfb0a754@fiee.net \
--to=texml@fiee.net \
--cc=ntg-context@ntg.nl \
/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 NNTP newsgroup(s).