From: Michael Tremer <michael.tremer@ipfire.org>
To: location@lists.ipfire.org
Subject: Re: Auto-generated plaintext updates; re: regression
Date: Thu, 10 Mar 2022 14:48:40 +0000 [thread overview]
Message-ID: <7433146A-A01A-49CE-A54C-AE5E33372D12@ipfire.org> (raw)
In-Reply-To: <9d5cae24-744d-cdc6-fd69-75876344072a@posteo.net>
[-- Attachment #1: Type: text/plain, Size: 2193 bytes --]
Hello,
> On 10 Mar 2022, at 14:45, Jordan Savoca <jsavoca(a)posteo.net> wrote:
>
> On 3/10/22 02:15, Michael Tremer wrote:
>> Yes, I will do this as soon as possible. At the moment, there are lots of other changes in the repository and I didn’t yet know for certain that they won’t break anything.
>
> Awesome, thank you!
>
>> But in general, I would like to say, that you should not use the text dump. It is only there for audit purposes and committed to the Git repository so that everyone can see any changes to the database easily.
>> I would strongly recommend using the binary database and the Python/Perl bindings. What is your application for the data?
>
> I had originally intended to use the binary database but I found the non-standard format and introduction of dependencies less flexible for my use case relative to fetching the plaintext set via submodule to store in a sqlite db where it can then be queried using standard libraries. For now my use case is limited to visualizing announcement changes over time but I hope to make something of import at some point.
I would strongly recommend this, because parsing the text database and going with the first match is quite likely going to give you inaccurate results.
The reason why we are going with a binary format is because it is organised as a binary tree and therefore can be searched *very* quickly. It also allows us to store multiple networks with the same start address, but a different prefix length which is what you won’t have in a relational database and therefore you will quite likely have inaccurate results.
We kept the library as small as possible and we are looking at upstreaming it to all major distributions because that will help integrating it into other software a lot easier. Any help with this would be greatly appreciated.
> The semi-recent change to maxmind's license + requiring an account to fetch geolocation data led me to look into alternative sources, so thank you for your work on location(8) :).
You are welcome :) You can also support us with a donation if you like at https://www.ipfire.org/donate.
Best,
-Michael
>
> --
> Jordan Savoca
next prev parent reply other threads:[~2022-03-10 14:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-09 23:42 Jordan Savoca
2022-03-10 9:15 ` Michael Tremer
2022-03-10 14:45 ` Jordan Savoca
2022-03-10 14:48 ` Michael Tremer [this message]
2022-03-10 16:02 ` Jordan Savoca
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=7433146A-A01A-49CE-A54C-AE5E33372D12@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=location@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