Topic: The Yiff Index

Posted under Off Topic

I'm sure I'm not the only one who's heard of the Yiff Index program by klaue, right? It's an indexing database to organize any off-line images you might have, similar to how e621 tags everything. I always thought it would be very handy to have both e621 & YI to work hand in hand. If someone uploaded an image here & it was already tagged in the YI db all the tags would be added upon upload, & if not the tags would merged with the YI db keeping everyone's off-line pics up to date.

I searched the forums for anything about this & found nothing. Not sure if this is even possible, but it never hurts to ask...right? Any-who, just something to think about.

*link*
http://fenris.vos-systems.net/YI/index.php

*edit*
I'd just like to add, this isn't some crafty ad I'm trying to post or something of the like. It's a legit question. These two services seem like they would go hand in hand. Yet, as improbable as it might be, it seems the two never crossed eachother's paths nor crossed the minds of anyone else who might've used both services.

---
>^.=.^<

Updated by Klaue

Cross-platform, synchronisable image tagging? Why didn't I know about this?

Thanks for the heads-up.

Updated by anonymous

leo_nine said:
Cross-platform, synchronisable image tagging? Why didn't I know about this?

Thanks for the heads-up.

They aren't synchronisable at the moment, I was just asking why they aren't. It seems like it might be a benefit if they did though. Right now I have a lot of images on an external. I'd like to tag them all in YI so I can pull them up fast without looking through my folders for them. But that's a lot of images & the YI db is kind of small, e621 on the other hand is huge! Also, I would know right away if an image I had wasn't on e621 if it doesn't get tagged in YI. Just think of the possibilities! Am I right?

Updated by anonymous

Hey there, Developer speaking, found this through my referers and thought that I might just as well throw in my two cents :)

I actually thought about such an interaction, but the problem is twofold:
1) it would need a code change on e621 (and YI) to synchronize the stuff, as YI can't just go through the whole of e621 all the time. Everytime a tag changes, the change would have to be submitted to YI. And of course the same thing the other way around.

2) The tags don't really fit. For most things, like species, gender etc, YI uses predefined tags. I did this to ensure that as few tags as possible could be in there several times with misspellings (or alternative names for the same) and to make the different languages work. It would suck to have the same tag there for every language (for example, snow leopard and Schneeleopard), but using predefined tags, the translation is no problem. It also keeps the data to be sent/received to the server down and ensures a bit of privacy if your network is monitored, as all the fetishes are only sent/received as numbers (IDs) instead of clear text.
But I digress. The issue with that is that there would have to be some way to map the tags of e621 to the ones of YI. As I'm not really an user of e621, I don't know how often tags change or if they're "free text", so keeping that mapping up to date could be pretty complicated.
Also, for some things, a mapping probably wouldn't be possible. For example: e621 has a tag "feline", YI on the other hand uses "feline" automatically if any feline species like tiger is there (the only tag applicable would be the catch-all "I don't know which type of feline" tag which is not supposed to be used when you know the species). Now say there's a pic on e621 with a single tiger and the tags "feline" and "tiger", how would the synchronizing know to ignore the feline? How would it know that there aren't two felines in the pic, one a tiger, the other one undetermined? etc etc
Sorry if that sounds a bit confusing..

Of course, there are some other issues, like if my little server could handle the storm of requests from e261 or the way YI merges tags (e621 would have to get higher priority than normal submitters, as currently, a tags "value" is determined by the number of times it was individually submitted), but I think the two above would be the worst.

@William: Oh, YI is synchronizable, but currently only with itself :P

Personally, I think this is an interesting idea, but I don't know if it's really do-able. And I wouldn't be against the influx of new users at all ;)
(My poor prog has pretty much no users.. people DL it, see that none of their pics are in the DB, and delete it again without tagging anything. most of the ~6300 pics in the DB were tagged by myself. Kinda depressing when I think how many months went into that.)

Updated by anonymous

Hey there Klaue! I was the one that posted the suggestion on the YI site...also one of the few people that occasionally upload new pic tags to the DB. I'm glad my message got through, wasn't sure if you might've abandoned the project.

I can see the troubles that might be encountered when trying to merge the two services together, but I fell that there's nothing that couldn't be dealt with once you and the head admin talked it over.

I'm not really a programmer, but I have had a little experience with coding. The proper use of &&'s, ||'s, NAND's & NOR's could ease some of the troubles present in assimilating e621's DB with YI's DB. Also there are some things that I feel would benefit the e621 DB & would ease the merging. For example separating the special tags (e.g. Artists, Characters, Copyrights, Genders, Species, Kinks) from general tags (e.g. colors, items, limbs (like tails), emotions, etc.). This would not only provide a cleaner DB on e621, but also make the merger much smoother. There are also a few other things that would be nice to see on e621, like a field for number of characters to name one thing.

As for the initial surge of DB requests from the merger, I'm sure there's a way to limit the amount on a per hour basis so as to trickle in the massive amounts of pictures that e621 houses at least until everything is up-to-date. Or even have the e621 team do it somewhat locally so as not to eat up bandwidth for either of you & then merge their YI DB with the one you currently host...or even host the DB themselves.

There are many solutions, to complete the task at hand of such a feat, for those who seek them.

I hope to soon see what might become of all this that I catalyzed, & am poised with fixed ears to hear of good news!

---
>^.=.^<

Updated by anonymous

WilliamYamagoshi said:
Hey there Klaue! I was the one that posted the suggestion on the YI site.. [...] I'm glad my message got through, wasn't sure if you might've abandoned the project.

I'm sorry, I see no new message on the site.. the newest one is from more than a year ago..

I'm not really a programmer, but I have had a little experience with coding. The proper use of &&'s, ||'s, NAND's & NOR's could ease some of the troubles present in assimilating e621's DB with YI's DB.

I don't even think that there would have to be much, if any, boolean logic - but a mapping table that has to be kept up to date, which is a tedious job, if even possible (if any user can just add new tags as they go, that could be a full time job..)

Also there are some things that I feel would benefit the e621 DB & would ease the merging. For example separating the special tags (e.g. Artists, Characters, Copyrights, Genders, Species, Kinks) from general tags (e.g. colors, items, limbs (like tails), emotions, etc.). This would not only provide a cleaner DB on e621, but also make the merger much smoother. There are also a few other things that would be nice to see on e621, like a field for number of characters to name one thing.

Certainly, implementing that on e261 would be great and make the process a lot easier, but that would mean lots of work for the e261 devs. Also, it would probably make it too different from the main branch of Ouroboros (the software here) so any future update of that would be hell (that's only a guess, dunno if Ouroboros would allready have the features needed).
And, after all, they still would have to do a one-time-mapping of the old tags to the reorganized ones.

All in all, I think that would be a load of work on the backs of the e261 people, and let's stay real here, they gain pretty much nothing from it
Sorry if I sound overly pessimistic, though :) It would be a great thing, especially for me (fame and fanart, here I come! :P), but realistically, e261 has not much to gain from it, so why should they put the metric ass ton of work into it? But hey, I don't know them, could be that they're just philanthropic like that

Updated by anonymous

Strange, I submitted a few messages on the YI site, it seemed like they went through at first but later they disappeared. I though they had to be approved or something before they were public like a few places I know do. Any-who, I agree that there would be a lot of work & the payout not so bountiful in relation. But it sure would be kewl.

Oh well, a dragon can dream.

---
>^.=.^<

Updated by anonymous

Hmm, there seems to be something wrong with the comment form since last server update. No wonder I never get any comments!

Maybe someone can nudge one of the e621 devs (or the dev if singular) in the direction of this thread to see what they have to say about it. Maybe I do that, but right now, gotta run.

Updated by anonymous

  • 1