Yuriy's Wish List and other related thoughts

yuriyandropov

Active member
I will try to gather in this thread some thoughts on how to improve the indexxx. Everybody: feel free to join the debate.

1. SQL Search. This is arguably what differentiates indexx from other sites, like ebi or thenude.eu.
I can search both set names and model names from the same form. From what I can surmise, the query uses SQL WHEN ... LIKE clause including the the _ and % wildcards. This is very good first step. For example I can type "062_j%" and get back DDF sets "062bj, 062fjh, 062bjfjh", but not, for example "062hot", as it does not contain in the 5th position in the string. So far so good. The problem is when I get a lot of entries back I can not sort them by criteria of my choosing.
I would also like gradual implementation of search using simplified regular expressions. Most SQL DB engines support XQuery by now, for example MySQL support it as of ver. 5.0


2. I am not sure how your "Similar names found" algorithm is implemented. As it is now, it gives back a lot of useless data. For example, using the same search string "062_j%" return a lot of model names beginning with "J". This is way off target. At the same time SOUNDEX ( "phonetic match") is probably not implemented. When I type in "Olexandra" ( Ukrainian spelling of Alexandra"), the engine does not return any "Alexandra" from the index, as it should.
 
Here my comments at your points:

1. hehe, if regex was implemented, you would probably be the only one using it :p (Too advanced for most people). Do you have a problem case in which you would use regex or XQuery where normal wildcards wouldn't be sufficient?
I think that most people that search for photo sets by codes, won't use any patterns. They would probably know in advance the complete code of the set they want to search for, and copy/paste in the search. But patterns can be useful when searching for model names when you only know a part (like the first 3 letters) of that name. In that case, basic wildcards can be enough I think?

The amount of entries returned by some queries, is a problem. Maybe pagination can be implemented to split the results over multiple pages.
On what type of properties would you like to sort the results? And is that for models or photo sets?


2. "Similar names found" uses soundex. Soundex retains the first letter of each name, so "Olexandra" doesn't match with "Alexandra". I agree that it would be better is those language spellings would also be found.
 
Thoughts, pt 2

Thoughts, pt 2

3. I would like to see the date of birth (DOB) and the country of birth added to the model db table. Preferably DOB is displayed in the international YYYY-MM-DD format, and the country is displayed as the 3-letter country code following the ISO 3166-1 alpha-3 standard ( see http://en.wikipedia.org/wiki/ISO_3166-1_alpha-3 for the codes). It would be nice to have that data, somehow, available as part of the query. For example, I would like to be able to search for all Claudias OR Klaudias from Hungary born after 1984.

Also, for a more "professional" look and to allow proper space for the other info panels to the right of the model photo, it is best to have model photo in portrait mode, with 0.65 - 0.70 aspect ratio, generally not to exceed 200 X 300 pixels.
In addition, for the same reasons of space, it make sense to utilize the space on the model name line, and move the "Vote for her" box up a bit.
For a bit of visual illustration of what result will look like, let's take one of my faves, Klaudia , aka Cindy Hope http://www.indexxx.com/models/336/klaudia/
(ignore the dots)

Klaudia ... (HUN)...1985-08-22 ...... Vote for her
......................................................... * * *
________________________
|..........................................| ........ Websites:
|..........................................|
|..........................................|



If you need the DOB data, PM me (Euro girls only).
 
Last edited:
4. Here is a wish list in terms of adding content in 2011:

European
... LSG Models <--- DONE
... InFocusGirls
... Pier999
... TeenRotica
Russian/Ukrainian
... MPL Studios <--- DONE
American
... suze.net
... Digital Dream Girls / Digital Desire


All of the sites above feature established models, quality photography, and original contents, so there is no risk of duplicate sets on a model page.
 
Last edited:
Good points Yuriy,

Currently indexxx is limited a bit by the framework used to develop the website, which obstructs the implementation of new features. Changing indexxx to a new framework/version takes some time, but after that it will hopefully be easier.

I agree that the space isn't divided very well. The problem is caused by flexible CSS layout and dynamic content. So I'll put it on the TODO list.

Your content wish list will gradually be added to indexxx :)
 
Here my comments at your points:

1. ...
The amount of entries returned by some queries, is a problem. Maybe pagination can be implemented to split the results over multiple pages.
On what type of properties would you like to sort the results? And is that for models or photo sets?


2. "Similar names found" uses soundex. Soundex retains the first letter of each name, so "Olexandra" doesn't match with "Alexandra". I agree that it would be better is those language spellings would also be found.

To reduce the clutter I would probably tighten a bit the range of the return from SOUNDEX, that you consider a match. In addition, I'd add more parameter validation. For example, if a search input string starts with a number, do not return any of the model names, i.e. user searches the sets. If the search string starts with a letter, but contains 2 digits or more, again, do not return any model names ( this accounts for some "fancy" model names, such as "Pretty4Eva" etc. If the search string contains 2 alpha characters, do not perform any soundex match, as it will be too vague, etc., etc.
Also, if I understood the 1st char problem correctly, it is very limiting, as there are a lot of "related" names that differ in the 1st letter, e.g. Wanda/Vanda, Christine/Kristine etc. In such case I would probably consider a custom match function, i.e. a function that would contain a mini dictionary of related names, but this probably merits separate discussion.
 
Questions

Questions

Questions:

1. What does "Show Photo Set codes" link on the right panel do? It resolves to http://www.indexxx.com/#, but the presence of "#" seems to make no difference to the appearance of the page.

2. What are the criteria for the decision to "promote" a red model to a blue model? Is it one-way street or can a model be "demoted" to red? I've seen some obscure models in blue, and some better-known models with 3 different websites and multiple sets as red. Is the decision done manually or by a script?

3. Does the content in the "Last added Models" section of the homepage ever update? Since the addition of 3 new websites in late December, one would expect to see a ton of new names in that section, yet it tends to stay the same. If it is not working, maybe it is better to remove it altogether, as it seems to have marginal utility at best.
 
Questions:

1. What does "Show Photo Set codes" link on the right panel do? It resolves to http://www.indexxx.com/#, but the presence of "#" seems to make no difference to the appearance of the page.
It should be removed. It was requested by a user when the photoset codes were not visible.

2. What are the criteria for the decision to "promote" a red model to a blue model? Is it one-way street or can a model be "demoted" to red? I've seen some obscure models in blue, and some better-known models with 3 different websites and multiple sets as red. Is the decision done manually or by a script?
In the beginning this feature wasn't implemented. The models that were added at that time, are all "blue", so they are listed with their photo in the model lists, which might include not well known models.
The decision is done manually, but should be done automatic with criteria like: blue for models with at least 5 sets and 3 different websites.
(At the moment the implemenation is a bit broken due to code changes.)[/quote]

3. Does the content in the "Last added Models" section of the homepage ever update? Since the addition of 3 new websites in late December, one would expect to see a ton of new names in that section, yet it tends to stay the same. If it is not working, maybe it is better to remove it altogether, as it seems to have marginal utility at best.
At the moment it's only showing *blue* models. It will be changed to include red in the next update.
 
[...]3. Does the content in the "Last added Models" section of the homepage ever update? Since the addition of 3 new websites in late December, one would expect to see a ton of new names in that section, yet it tends to stay the same. If it is not working, maybe it is better to remove it altogether, as it seems to have marginal utility at best.
The section is now listing the latest models (including *red* models).
 
Teendreams lesbian sets marked up

Teendreams lesbian sets marked up

Please find attached the text file containing IDs of the models in TeenDreams lesbian and group sets. File is zipped to fit within space requirements of this BB.
Hope it will be a valuable addition to the indexxx database.

As usual, uncheck word-wrap when viewing and enjoy :cool:
 

Attachments

  • teendreams group sets.zip
    8.9 KB · Views: 0
Wow, nice, that's a large list :D
I'll start working on it. I'll let you know when it's finished :)
 
Question about the TeenDreams list. It says "Model aliases marked with * are randomly chosen by TeenDreams, and do not need to be included in the alias table for a given model". How do determine whether a model name is randomly chosen by TeenDreams? Aren't most names from TeenDreams randomly chosen?
If you're planning to make more of such model-to-set-mapping lists, let me know. Then we can work out a format for it. :)
 
Complete model / scene list of PornPros' Cock Competition

Complete model / scene list of PornPros' Cock Competition

Continuing effort to tidy up the indexxx database.
Please see the text file attached. Same format as Teendreams group sets (see my earlier post in this thread).
 

Attachments

  • c-competition-setlist.TXT
    7 KB · Views: 0
Add-Model-to-Set format proposal

Add-Model-to-Set format proposal

I would to propose the following format for mapping models to existing sets.
If you have any suggestions, or things that should be added/changed that would help you making such lists, just let me know.


-date format: year-month-day
-modelNameAtWebsite: if the name is random, prepend a "*" before the model name. If no model name is known, leave it empty, but do add the tab separator.
-indexxxUrl: if no indexxxUrl is known, use a * character instead.
-Multiple entries can be added. No empty line is needed to seperate entries, but it can be added if it helps you visually to see each distinct entry.
-"[tab]" stands for a tab character.

Code:
======= ENTRY FORMAT =========
date[tab]setid
modelNameAtWebsite[tab]indexxxUrl
modelNameAtWebsite[tab]indexxxUrl
modelNameAtWebsite[tab]indexxxUrl
modelNameAtWebsite[tab]indexxxUrl



======= example of the entries file content: ==============
2005-05-11	6375
Veronika	http://www.indexxx.com/models/258/jasmin/
Adrienne	http://www.indexxx.com/models/729/yasmine-gold/

2004-09-08	5267
*Katie	http://www.indexxx.com/models/55/anita-queen/
*Julia	http://www.indexxx.com/models/62/aschley-robins/	

2005-08-10	6771
Danielle	*
Ellen	http://www.indexxx.com/models/188/ellen-saint/

2004-01-01	3483
Faith	http://www.indexxx.com/models/31687/faith-15/
	http://www.indexxx.com/models/31189/natalie-28/
 
Last edited:
Please find attached the text file containing IDs of the models in TeenDreams lesbian and group sets. File is zipped to fit within space requirements of this BB.
Hope it will be a valuable addition to the indexxx database.

As usual, uncheck word-wrap when viewing and enjoy :cool:
Added :)
 
Back
Top