Remove some unneeded links

This commit is contained in:
Paul Friederichsen 2021-12-22 16:43:07 -06:00
parent 24da1d24c6
commit b65b5598f3
4 changed files with 2 additions and 14 deletions

View File

@ -141,7 +141,3 @@ In general, hydrus is good for individual files like you commonly find on imageb
If you are looking for a comic manager to supplement hydrus, check out this user-made guide to other archiving software [here](https://github.com/CuddleBear92/Hydrus-Presets-and-Scripts/wiki/0-Alternative-Programs-and-Resources#software)!
And although the client can hold millions of files, it starts to creak and chug when displaying or otherwise tracking more than about 40,000 or so in a single gui window. As you learn to use it, please try not to let your download queues or general search pages regularly sit at more than 40 or 50k total _items_, or you'll start to slow other things down. Another common mistake is to leave one large 'system:everything' or 'system:inbox' page open with 70k+ files. For these sorts of 'ongoing processing' pages, try adding a 'system:limit=256' to keep them snappy. One user mentioned he had regular gui hangs of thirty seconds or so, and when we looked into it, it turned out his handful of download pages had three million files queued up! Just try and take things slow until you figure out what your computer's limits are.
[I want to learn more about files! ---->](getting_started_more_files.md)
[No, let's learn about tags! ---->](getting_started_tags.md)

View File

@ -139,5 +139,3 @@ By default, hydrus stores all your user data in one location, so backing up is s
Do not put your live database in a folder that continuously syncs to a cloud backup. Many of these services will interfere with a running client and can cause database corruption. If you still want to use a system like this, either turn the sync off while the client is running, or use the above backup workflows to safely backup your client to a separate folder that syncs to the cloud.
I recommend you always backup before you update, just in case there is a problem with my code that breaks your database. If that happens, please [contact me](contact.html), describing the problem, and revert to the functioning older version. I'll get on any problems like that immediately.
[Let's import some files! ---->](getting_started_files.html)

View File

@ -3,15 +3,13 @@ title: ratings
---
# getting started with ratings
[<\-\-\- Back to downloading](getting_started_downloading.html)
The hydrus client supports two kinds of ratings: _like/dislike_ and _numerical_. Let's start with the simpler one:
## 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_:
![](ratings_like.png)
![](images/ratings_like.png)
You can set a variety of colours and shapes.
@ -38,5 +36,3 @@ Once you have some ratings set, you can search for them using system:rating, whi
![](images/ratings_system_pred.png)
On my own client, I find it useful to have several like/dislike ratings set up as one-click pseudo-tags, like the 'OP images' above.
[Go back to the index --->](index.html)

View File

@ -44,6 +44,4 @@ These programs are free software. Everything I, hydrus dev, have made is under t
--8<-- "license.txt"
```
Do what the fuck you want to with my software, and if shit breaks, DEAL WITH IT.
[Happy? Go on to the getting started guide ---->](getting_started_installing.html)
Do what the fuck you want to with my software, and if shit breaks, DEAL WITH IT.