Align header IDs with original and other fixes
This commit is contained in:
parent
60f7188fe7
commit
83ad525d40
|
@ -1,3 +1,7 @@
|
|||
---
|
||||
title: PTR Guide
|
||||
---
|
||||
|
||||
# PTR for Dummies
|
||||
or *Myths and facts about the Public Tag Repository*
|
||||
|
||||
|
|
|
@ -24,7 +24,7 @@ I have tried very hard to ensure the PTR respects your privacy. Your account is
|
|||
|
||||
Most users should have very few worries about privacy. The general rule is that it is always healthy to use a VPN, but please check [here for a full discussion and explanation of the anonymisation routine](privacy.html).
|
||||
|
||||
## a note on resources
|
||||
## a note on resources { id="ssd" }
|
||||
|
||||
!!! danger
|
||||
**If you are on an HDD, or your SSD does not have at least 64GB of free space, do not add the PTR!**
|
||||
|
@ -62,7 +62,7 @@ Then you can check your PTR at any time under _services->review services_, under
|
|||
|
||||
![](images/review_repos_public_tag_repo.png)
|
||||
|
||||
## jump-starting an install
|
||||
## jump-starting an install { id="quicksync" }
|
||||
|
||||
A user kindly manages a store of update files and pre-processed empty client databases to get your synced quicker. This is generally recommended for advanced users or those following a guide, but if you are otherwise interested, please check it out:
|
||||
|
||||
|
|
|
@ -15,7 +15,7 @@ The downloader is highly parallelisable, and while the default bandwidth rules s
|
|||
|
||||
It also takes a decent whack of CPU to import a file. You'll usually never notice this with just one hard drive import going, but if you have twenty different download queues all competing for database access and individual 0.1-second hits of heavy CPU work, you will discover your client starts to judder and lag. Keep it in mind, and you'll figure out what your computer is happy with. I also recommend you try to keep your total loaded files/urls to be under 20,000 to keep things snappy. Remember that you can pause your import queues, if you need to calm things down a bit.
|
||||
|
||||
## let's do it
|
||||
## let's do it { id="start" }
|
||||
|
||||
Open the new page selector with F9 and then hit _download->gallery_:
|
||||
|
||||
|
@ -63,7 +63,7 @@ To edit the defaults, hit up _network->downloaders->manage default tag import op
|
|||
!!! warning
|
||||
The file limit and file/tag import options on the upper panel, if changed, will only apply to **new** queries. If you want to change the options for an existing queue, either do so on its highlight panel below or use the 'set options to queries' button.
|
||||
|
||||
## watching threads
|
||||
## watching threads { id="threads" }
|
||||
|
||||
If you are an imageboard user, try going to a thread you like and drag-and-drop its URL (straight from your web browser's address bar) onto the hydrus client. It should open up a new 'watcher' page and import the thread's files!
|
||||
|
||||
|
@ -87,7 +87,7 @@ Again: the real problem with downloading is not finding new things, it is keepin
|
|||
|
||||
Subscriptions are a way to automatically recheck a good query in future, to keep up with new files. Many users come to use them. When you are comfortable with downloaders and have an idea of what you like, come back and read the subscription help, which is [here](getting_started_subscriptions.html).
|
||||
|
||||
## other downloading
|
||||
## other downloading { id="other_downloaders" }
|
||||
|
||||
There are two other ways of downloading, mostly for advanced or one-off use.
|
||||
|
||||
|
@ -112,8 +112,4 @@ Most sites only have one way of logging in, but hydrus does support more. Hentai
|
|||
|
||||
The login system is new and still a bit experimental. Don't try to pull off anything too weird with it! If anything goes wrong, it will likely delay the script (and hence the whole domain) from working for a while, or invalidate it entirely. If the error is something simple, like a password typo or current server maintenance, go back to this dialog to fix and scrub the error and try again. If the site just changed its layout, you may need to update the login script. If it is more complicated, please contact me, hydrus_dev, with the details!
|
||||
|
||||
If you would like to login to a site that is not yet supported by hydrus (usually ones with a Captcha in the login page), see about getting a web browser add-on that lets you export a cookies.txt (either for the whole browser or just for that domain) and then drag and drop that file onto the hydrus _network->data->review session cookies_ dialog. This sometimes does not work if your add-on's export formatting is unusual. If it does work, hydrus will import and use those cookies, which skips the login by making your hydrus pretend to be your browser directly. This is obviously advanced and hacky, so if you need to do it, let me know how you get on and what tools you find work best!
|
||||
|
||||
[Read about ratings --->](getting_started_ratings.html)
|
||||
|
||||
[Go back to the index --->](index.html)
|
||||
If you would like to login to a site that is not yet supported by hydrus (usually ones with a Captcha in the login page), see about getting a web browser add-on that lets you export a cookies.txt (either for the whole browser or just for that domain) and then drag and drop that file onto the hydrus _network->data->review session cookies_ dialog. This sometimes does not work if your add-on's export formatting is unusual. If it does work, hydrus will import and use those cookies, which skips the login by making your hydrus pretend to be your browser directly. This is obviously advanced and hacky, so if you need to do it, let me know how you get on and what tools you find work best!
|
|
@ -12,7 +12,7 @@ If any of this is confusing, a simpler guide is [here](https://github.com/Zweiba
|
|||
|
||||
There are no limits and few brakes on your behaviour. It is possible to import millions of files. For many new users, their first mistake is downloading too much too fast in overexcitement and becoming overwhelmed. Take things slow and figure out good processing workflows that work for your schedule before you start adding 500 subscriptions.
|
||||
|
||||
## the problem
|
||||
## the problem { id="hellmode_dot_exe" }
|
||||
|
||||
If you have ever seen something like this--
|
||||
|
||||
|
@ -22,7 +22,7 @@ If you have ever seen something like this--
|
|||
|
||||
Finding the right picture quickly can be difficult. Finding everything by a particular artist at a particular resolution is unthinkable. Integrating new files into the whole nested-folder mess is a further pain, and most operating systems bug out when displaying 10,000+ thumbnails.
|
||||
|
||||
## so, what does the hydrus client do?
|
||||
## so, what does the hydrus client do? { id="the_client" }
|
||||
|
||||
Let's first focus on _importing_ files.
|
||||
|
||||
|
@ -100,7 +100,7 @@ Although some support is imperfect for the complicated filetypes. For the Window
|
|||
|
||||
The client can also download files from several websites, including 4chan and other imageboards, many boorus, and gallery sites like deviant art and hentai foundry. You will learn more about this later.
|
||||
|
||||
## inbox and archiving
|
||||
## inbox and archiving { id="inbox" }
|
||||
|
||||
The client sends newly imported files to an **inbox**, just like your email. Inbox acts like a tag, matched by 'system:inbox'. A small envelope icon is drawn in the top corner of all inbox files:
|
||||
|
||||
|
@ -116,7 +116,7 @@ A trashed file will not appear in subsequent normal searches, although you can s
|
|||
|
||||
A quick way of processing new files is–
|
||||
|
||||
## filtering
|
||||
## filtering { id="filtering_inbox" }
|
||||
|
||||
Lets say you just downloaded a good thread, or perhaps you just imported an old folder of miscellany. You now have a whole bunch of files in your inbox--some good, some awful. You probably want to quickly go through them, saying _yes, yes, yes, no, yes, no, no, yes_, where _yes_ means 'keep and archive' and _no_ means 'delete this trash'. **Filtering** is the solution.
|
||||
|
||||
|
@ -132,7 +132,7 @@ Your choices will not be committed until you finish filtering.
|
|||
|
||||
This saves time.
|
||||
|
||||
## lastly
|
||||
## lastly { id="what_hydrus_is_for" }
|
||||
|
||||
The hydrus client's workflows are not designed for half-finished files that you are still working on. Think of it as a giant archive for everything excellent you have decided to store away. It lets you find and remember these things quickly.
|
||||
|
||||
|
|
|
@ -121,18 +121,18 @@ I use [ToDoList](http://abstractspoon.com/) to remind me of my jobs for the day,
|
|||
|
||||
By default, hydrus stores all your user data in one location, so backing up is simple:
|
||||
|
||||
* #### the simple way - inside the client
|
||||
|
||||
#### the simple way - inside the client
|
||||
:
|
||||
Go _database->set up a database backup location_ in the client. This will tell the client where you want your backup to be stored. A fresh, empty directory on a different drive is ideal.
|
||||
|
||||
|
||||
Once you have your location set up, you can thereafter hit _database->update database backup_. It will lock everything and mirror your files, showing its progress in a popup message. The first time you make this backup, it may take a little while (as it will have to fully copy your database and all its files), but after that, it will only have to copy new or altered files and should only ever take a couple of minutes.
|
||||
|
||||
|
||||
Advanced users who have migrated their database across multiple locations will not have this option--use an external program in this case.
|
||||
|
||||
* #### the powerful way - using an external program
|
||||
|
||||
#### the powerful way - using an external program
|
||||
:
|
||||
If you would like to integrate hydrus into a broader backup scheme you already run, or you are an advanced user with a complicated hydrus install that you have migrated across multiple drives, then you need to backup two things: the client\*.db files and your client\_files directory(ies). By default, they are all stored in install\_dir/db. The .db files contain your settings and file metadata like inbox/archive and tags, while the client\_files subdirs store your actual media and its thumbnails. If everything is still under install\_dir/db, then it is usually easiest to just backup the whole install dir, keeping a functional 'portable' copy of your install that you can restore no prob. Make sure you keep the .db files together--they are not interchangeable and mostly useless on their own!
|
||||
|
||||
|
||||
Shut the client down while you run the backup, obviously.
|
||||
|
||||
!!! danger
|
||||
|
|
|
@ -5,7 +5,7 @@ title: ratings
|
|||
|
||||
The hydrus client supports two kinds of ratings: _like/dislike_ and _numerical_. Let's start with the simpler one:
|
||||
|
||||
## like/dislike
|
||||
## like/dislike { id="like_dislike" }
|
||||
|
||||
A new client starts with one of these, called 'favourites'. It can set one of two values to a file. It does not have to represent like or dislike--it can be anything you want, like 'send to export folder' or 'explicit/safe' or 'cool babes'. Go to _services->manage services->local->like/dislike ratings_:
|
||||
|
||||
|
@ -23,7 +23,7 @@ As well as the shape and colour options, you can set how many 'stars' to display
|
|||
|
||||
If you change the star range at a later date, any existing ratings will be 'stretched' across the new range. As values are collapsed to the nearest integer, this is best done for scales that are multiples. 2/5 will neatly become 4/10 on a zero-allowed service, for instance, and 0/4 can nicely become 1/5 if you disallow zero ratings in the same step. If you didn't intuitively understand that, just don't touch the number of stars or zero rating checkbox after you have created the numerical rating service!
|
||||
|
||||
## now what?
|
||||
## now what? { id="using_ratings" }
|
||||
|
||||
Ratings are displayed in the top-right of the media viewer:
|
||||
|
||||
|
|
|
@ -6,7 +6,7 @@ title: tags
|
|||
|
||||
If any of this is confusing, a simpler guide is [here](https://github.com/Zweibach/text/blob/master/Hydrus/Hydrus%20Help%20Docs/00_tableOfContents.md), and some video guides are [here](https://github.com/CuddleBear92/Hydrus-guides)!
|
||||
|
||||
## how do we find files?
|
||||
## how do we find files? { id="intro" }
|
||||
|
||||
So, you have stored some media in your database. Everything is hashed and cached. You can search by inbox and resolution and size and so on, but if you really want to find what we are looking for, you will have to use _tags_.
|
||||
|
||||
|
@ -39,7 +39,7 @@ If you add more tags or system predicates to a search, you will limit the result
|
|||
|
||||
[![](images/sororitas_hanako.png)](images/sororitas_hanako.png)
|
||||
|
||||
You can also exclude a tag by prefixing it with a hyphen (e.g. '-heresy').
|
||||
You can also exclude a tag by prefixing it with a hyphen (e.g. `-heresy`).
|
||||
|
||||
## OR searching
|
||||
|
||||
|
@ -57,11 +57,11 @@ If you enter an OR tag incorrectly, you can either cancel or 'rewind' the under-
|
|||
|
||||
![](images/or_buttons.png)
|
||||
|
||||
You can also cancel an under-construction OR by hitting Esc on an empty input. You can add any sort of search term to an OR search predicate, including system predicates. Some unusual sub-predicates (typically a '-tag', or a very broad system predicate) can run very slowly, but they will run much faster if you include non-OR search predicates in the search:
|
||||
You can also cancel an under-construction OR by hitting Esc on an empty input. You can add any sort of search term to an OR search predicate, including system predicates. Some unusual sub-predicates (typically a `-tag`, or a very broad system predicate) can run very slowly, but they will run much faster if you include non-OR search predicates in the search:
|
||||
|
||||
![](images/or_mixed.png)
|
||||
|
||||
This search will return all files that have the tag 'fanfic' and one or more of 'medium:text', a positive value for the like/dislike rating 'read later', or PDF mime.
|
||||
This search will return all files that have the tag `fanfic` and one or more of `medium:text`, a positive value for the like/dislike rating 'read later', or PDF mime.
|
||||
|
||||
## tag repositories
|
||||
|
||||
|
@ -93,8 +93,4 @@ I recommend you not spam tags to the public tag repo until you get a rough feel
|
|||
|
||||
You can connect to more than one tag repository if you like. When you are in the _manage tags_ dialog, pressing the up or down arrow keys on an empty input switches between your services.
|
||||
|
||||
[FAQ: why can my friend not see what I just uploaded?](faq.html#delays)
|
||||
|
||||
[Read about downloading --->](getting_started_downloading.html)
|
||||
|
||||
[Go back to the index --->](index.html)
|
||||
[FAQ: why can my friend not see what I just uploaded?](faq.html#delays)
|
|
@ -2,7 +2,7 @@
|
|||
title: introduction and statement of principles
|
||||
---
|
||||
|
||||
## on being anonymous
|
||||
## on being anonymous { id="anonymous" }
|
||||
|
||||
Nearly all sites use the same pseudonymous username/password system, and nearly all of them have the same drama, sockpuppets, and egotistical mods. Censorship is routine. That works for many people, but not for me.
|
||||
|
||||
|
@ -10,7 +10,7 @@ I enjoy being anonymous online. When you aren't afraid of repercussions, you can
|
|||
|
||||
I've been on the imageboards for a long time, saving everything I like to my hard drive. After a while, the whole collection was just too large to manage on my own.
|
||||
|
||||
## the hydrus network
|
||||
## the hydrus network { id="hydrus_network" }
|
||||
|
||||
So! I'm developing a program that helps people organise their files together anonymously. I want to help you do what you want with your stuff, and that's it. You can share some tags and files with other people if you want to, but you don't have to connect to anything if you don't. **The default is complete privacy, no sharing**, and every upload requires a conscious action on your part. I don't plan to ever record metrics on users, nor serve ads, nor charge for my software. The software never phones home.
|
||||
|
||||
|
@ -24,7 +24,7 @@ As well as the client, there is also a server that anyone can run to store files
|
|||
|
||||
I have many plans to expand the client and the network.
|
||||
|
||||
## statement of principles
|
||||
## statement of principles { id="principles" }
|
||||
|
||||
* No speech should be outlawed.
|
||||
* Everyone should be able to control their own media diet.
|
||||
|
|
Loading…
Reference in New Issue