public inbox for dbl@lists.ipfire.org
 help / color / mirror / Atom feed
From: Stefan Schantl <stefan.schantl@ipfire.org>
To: dbl@lists.ipfire.org
Subject: Re: Hello list & FAQ
Date: Fri, 27 Feb 2026 18:49:53 +0100	[thread overview]
Message-ID: <75efebd30dfe8d0e280b9b4ed9ea4235c40fb21d.camel@ipfire.org> (raw)
In-Reply-To: <61E55741-2601-4232-9067-5E69847EE9BD@ipfire.org>

Hello Michael,

thanks for creating this list and the FAQ on the DBL main page.

I hope this will help to get most questions for new users and
contributors of DBL answered.

During reading through the FAQ's I've noticed that in the "API &
Programmatic Access" section at point "Are there rate limits on
downloads or zone transfers?" your are using the following text:

If you are periodically downloading plaintext files, please avoid
fetching them more often than necessary — once per hour should be more
than sufficient for most use cases. 

The same sentence is also used in the next main section "Contributing"
at the point "How can I contribute a new domain source or feed?" which
may be some kind of copy paste issue.

Besides this small issue, the questions are well choosen and answered
in a very clear way.

Best regards,

-Stefan


> Hello everyone,
> 
> I hope you found this list well.
> 
> So that more people are aware of this list and other infrastructure
> existing, I created an FAQ page for the DBL website. Please let me
> know what you think:
> 
>   https://www.ipfire.org/dbl/faq
> 
> -Michael


      reply	other threads:[~2026-02-27 17:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-27 16:05 Michael Tremer
2026-02-27 17:49 ` Stefan Schantl [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=75efebd30dfe8d0e280b9b4ed9ea4235c40fb21d.camel@ipfire.org \
    --to=stefan.schantl@ipfire.org \
    --cc=dbl@lists.ipfire.org \
    /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