# Local Documentation

**URL:** https://community.mp3tag.de/t/local-documentation/56871
**Category:** General Discussion
**Created:** [March 30, 2022, 4:29pm UTC](https://community.mp3tag.de/t/local-documentation/56871 "2022-03-30T16:29:46Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![tgm](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/t/c68b51/32.png) [@tgm](https://community.mp3tag.de/u/tgm)
#### Post date: [March 30, 2022, 4:29pm UTC](https://community.mp3tag.de/t/local-documentation/56871/1 "2022-03-30T16:29:46Z")

</div>

Every developer wants us to look through whatever documentation is available instead of asking the same questions repeatedly. But these days it is becoming much more difficult to go look at their documentation without also creating privacy concerns. How about a method of downloading the entire documentation package without the need of performing screen scrapes?

---

<div class="post-metadata">

### Author: ![ohrenkino](https://community.mp3tag.de/user_avatar/community.mp3tag.de/ohrenkino/32/4843_2.png) [@ohrenkino](https://community.mp3tag.de/u/ohrenkino)
#### Post date: [March 30, 2022, 5:05pm UTC](https://community.mp3tag.de/t/local-documentation/56871/2 "2022-03-30T17:05:02Z")

</div>

> [@tgm](#):
>
> without also creating privacy concerns

where do you see the privacy concerns?  
The current MP3tag documentation is available here:

> **[Mp3tag Documentation](https://docs.mp3tag.de/)**
>
> Mp3tag is the universal Tag Editor. It supports editing of metadata and cover art for many different audio and video formats (MP3, MP4, FLAC, WAV, ...), file renaming, metadata import and repeatable actions.

and can be accessed without the need to login or identify oneself.  
I am not even sure which cookies (if at all) are used.

---

<div class="post-metadata">

### Author: ![Zerow](https://community.mp3tag.de/user_avatar/community.mp3tag.de/zerow/32/11379_2.png) [@Zerow](https://community.mp3tag.de/u/Zerow)
#### Post date: [March 30, 2022, 5:51pm UTC](https://community.mp3tag.de/t/local-documentation/56871/3 "2022-03-30T17:51:46Z")

</div>

> [@tgm](#):
>
> [...]  
> How about a method of downloading the entire documentation package  
> [...]

Count me in:

> [@Updated Documentation — Work in Progress](https://community.mp3tag.de/t/updated-documentation-work-in-progress/56547/54):
>
> 1] Why send the user to the website? What happens if the user's Internet connection is down? 2] Why remain old help files at C:\Program Files (x86)\Mp3tag\help\ when the first three entries in the Help tab send the user to the never version posted on-line? 3] How to access those locally stored help files from within Mp3tag? Which button or menu entry takes to that content?

---

<div class="post-metadata">

### Author: ![tgm](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/t/c68b51/32.png) [@tgm](https://community.mp3tag.de/u/tgm)
#### Post date: [March 30, 2022, 6:31pm UTC](https://community.mp3tag.de/t/local-documentation/56871/4 "2022-03-30T18:31:14Z")

</div>

> [@ohrenkino](#):
>
> I am not even sure which cookies (if at all) are used.

This is a privacy concern in of itself. You don't know, nor do I. Does some data aggregator like Google (for example) need to know what specific things I'm researching inside MP3Tag documentation?  
There are many more. I'm not suggesting that it's because of MP3Tag, but instead because of the out of control capturing of data by just about anyone who wants to. I'm not looking for this comment to get out of control, but people need to be a lot more concerned where their network communications are going. Every communication outside of your local network is a risk.

---

<div class="post-metadata">

### Author: ![MotleyG](https://community.mp3tag.de/user_avatar/community.mp3tag.de/motleyg/32/440_2.png) [@MotleyG](https://community.mp3tag.de/u/MotleyG)
#### Post date: [March 30, 2022, 6:49pm UTC](https://community.mp3tag.de/t/local-documentation/56871/5 "2022-03-30T18:49:52Z")

</div>

> [@tgm](#):
>
> I'm not looking for this comment to get out of control, but people need to be a lot more concerned where their network communications are going. Every communication outside of your local network is a risk.

If a quick search for info about mp3tag online is a concern with your browser, I think there are plenty of bigger concerns IMO. Just posting in a thread like this... wait a second... 🤔

---

<div class="post-metadata">

### Author: ![Florian](https://community.mp3tag.de/user_avatar/community.mp3tag.de/florian/32/5759_2.png) [@Florian](https://community.mp3tag.de/u/Florian)
#### Post date: [March 30, 2022, 7:23pm UTC](https://community.mp3tag.de/t/local-documentation/56871/6 "2022-03-30T19:23:08Z")

</div>

I'm currently not offering the documentation for download. One reason is that it's not easily browsable (is this a word?) due to each page using it's own folder for URLs like [https://docs.mp3tag.de/filter](https://docs.mp3tag.de/filter). This doesn't play well without a web server.

Another reason is, that I also hoped for a reality where I can easily update the documentation and make it available instantly to everybody interested.

> [@tgm](#):
>
> without also creating privacy concerns

I hoped that your concerns would be more specific to the online documentation, now I need to answer more generically:

I'm not using any cookies for the docs or track you in any identifiable way. I'm not sending installation tokens attached to your installation when you access the documentation from within the app. I don't know if you opened the docs once, twice, or a hundred times per day. I'm not using anything Google on my sites.

If _you_ use Google to search via `site:docs.mp3tag.de` I suggest switching to DuckDuckGo, which also allows for limiting the search scope to a specific site.

I might offer an offline version of the documentation sometime in the future, but I'm currently not actively working on this.
