THIS SHIT HAS EXISTED FOR NEARLY A DECADE AND NO ONE TOLD ME...

THIS SHIT HAS EXISTED FOR NEARLY A DECADE AND NO ONE TOLD ME? REEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEE

Attached: tmsu.png (814x252, 8.64K)

Other urls found in this thread:

tmsu.org/
github.com/oniony/TMSU
twitter.com/SFWRedditImages

Are you trying to evade filters?
What does this mean?

this actually looks pretty neat OP
i have 1.5tb of furry porn that needs tagging badly

are you schizo or retarded

fpbp why the shit photo OP

would you have preferred this one?

Attached: 1643860566.jpg (260x131, 5.71K)

what does it do?

found it tmsu.org/
Hydrus sounds like a better solution anyways who cares

How does it compare to Hydrus?
I've always thought of running a danbooru server, is that a good idea?

Attached: 2022-02-03_12-25.png (238x286, 12.07K)

hydrus is bloatware, this you can use on a chinkpad

upboat for le rare pepe collection

helps you find memes

/cumg/ tried to tell you about tmsu.

It associates tags with files and lets you do tag queries to find them later.
You can also mount a virtual filesystem that lets you navigate your tags through the filesystem.
It's very clever.
github.com/oniony/TMSU

it's where i found it the other day

how big does the db get? i have like 1-2g of memes

...and yet, the jannies want to ban one of the most useful and productive threads in Any Forums.

Attached: 83b5dbfa498fa6383cac45920f41fb65.jpg (800x800, 279.9K)

gee I wonder why

CREATE TABLE tag (
id INTEGER PRIMARY KEY,
name TEXT NOT NULL
);
CREATE INDEX idx_tag_name
ON tag(name);
CREATE TABLE file (
id INTEGER PRIMARY KEY,
directory TEXT NOT NULL,
name TEXT NOT NULL,
fingerprint TEXT NOT NULL,
mod_time DATETIME NOT NULL,
size INTEGER NOT NULL,
is_dir BOOLEAN NOT NULL,
CONSTRAINT con_file_path UNIQUE (directory, name)
);
CREATE INDEX idx_file_fingerprint
ON file(fingerprint);
CREATE TABLE value (
id INTEGER PRIMARY KEY,
name TEXT NOT NULL,
CONSTRAINT con_value_name UNIQUE (name)
);
CREATE TABLE file_tag (
file_id INTEGER NOT NULL,
tag_id INTEGER NOT NULL,
value_id INTEGER NOT NULL,
PRIMARY KEY (file_id, tag_id, value_id),
FOREIGN KEY (file_id) REFERENCES file(id),
FOREIGN KEY (tag_id) REFERENCES tag(id)
FOREIGN KEY (value_id) REFERENCES value(id)
);
CREATE INDEX idx_file_tag_file_id
ON file_tag(file_id);
CREATE INDEX idx_file_tag_tag_id
ON file_tag(tag_id);
CREATE INDEX idx_file_tag_value_id
ON file_tag(value_id);
CREATE TABLE query (
text TEXT PRIMARY KEY
);
CREATE TABLE setting (
name TEXT PRIMARY KEY,
value TEXT NOT NULL
);
CREATE TABLE implication (
tag_id INTEGER NOT NULL,
value_id INTEGER NOT NULL,
implied_tag_id INTEGER NOT NULL,
implied_value_id INTEGER NOT NULL,
PRIMARY KEY (tag_id, value_id, implied_tag_id, implied_value_id)
);
CREATE TABLE version (
major NUMBER NOT NULL,
minor NUMBER NOT NULL,
patch NUMBER NOT NULL,
revision NUMBER NOT NULL,
PRIMARY KEY (major, minor, patch, revision)
);


The above is the schema tmsu uses. Every file that's tagged will take up one row in file table and one row in the file_tag table for each tag you apply to it. Based on what sqlite3_analyzer said, you're looking at about 100 bytes per file + 6 bytes for every tag you apply to the file.

>1-2g of memes
The number of files matters more than how much storage you consume in this case.

need to make the mods understand

how's this compare to hydrus?

They want to keep us from knowledge, so as to not become overthrown by the populace.

>how's this compare to hydrus?
All tmsu does is associate files with tags.
It doesn't try to do anything else.
It's not going to automatically download things for you or automatically tag things for you like hydrus does.

Any Forumsfags TOLD by the JANNIES

Attached: neelamlick.png (672x448, 350.22K)