User talk:Aperfectring/Random image page

I like the idea! But when I think about some of the images, there are cases where voting is just tiresome:

Some of the pictures I have taken (and one of the two pictures I saw at my first try of your page) are blurry...
... or they are really really boring like this one ...
... also there is and similar pictures.

While it is possible (and probable) that they will be voted down each time they show up, it will take very long for them to end up at the lower end of the list. It would speed things up if there was a "This picture really sucks, I want to give it -10 points" button. That's just my 2 cents because I'm lazy and I don't want to see the boring pictures often, I won't mind if you ignore this proposal. Yeah, ignoring is probably best. Why am I still typing? Ah, deleting this post is too much effort. I think I'll find something to occupy myself now. Bye. - Danatar 17:41, 17 February 2010 (UTC)

Yeah, that will happen, but there are also a lot of hidden gems that people wouldn't see otherwise, my tendency is to err on the side of caution, so that we can see all the images!
Same as point #1
That file will be filtered out, because it is not in [[Category:Meetup in LAT LON]].

There has been talk of adding a blacklist, but I think the best way is to just have the probability weight the choice of images based on their current rating. Unfortunately that means there will be some boring images you have to slog through, but as time goes on, it should get better and better. --aperfectring 17:51, 17 February 2010 (UTC)

Schema suggestion

`image` table

Column name	Type
imageID	CHAR(64)
imageName	VARCHAR(65535)
votesUp	INT() UNSIGNED
votesDown	INT() UNSIGNED
isCached	BOOL

`category` table

Column name	Type
catID	INT() UNSIGNED
catName	CHAR(64)

`wikiCatted` and `reportCatted` tables

Column name	Type
catID	INT() UNSIGNED
imageID	CHAR(64)

`wikiCatted` is emptied and repopulated on each sweep of the wiki. `reportCatted` is added to when people use the app. (Perhaps that table should have IP address and timestamp as well?)

Usage

INSERT values into the `category` table ("GPS", "XKCD Marker", "Wildlife") and link them to images using the `wikiCatted` table.

Comments

I do like this better than my idea. However, the wiki likely not swept on a regular basis, as gathering the categories of each of the images would probably be fairly wiki-intensive and time consuming. I will look into that, but the more likely it will be updated once, and randomly refreshed. --aperfectring 21:37, 17 February 2010 (UTC)

I am enjoying looking at all our beautiful pictures, even without the voting option. I would like to see, for each picture presented:

a link to the associated expedition report
list of tags
a link to that picture on the tagging page

-Robyn 03:29, 31 March 2010 (UTC)

Voting / ranking algorithm

This is mostly a summary of talks on the IRC, only little new thoughts, but I think that it should go to the wiki so I wrote it down.

Myself I look very much forward to the voting feature, and would actually love to see that implemented first. --Ekorren 17:57, 21 February 2010 (UTC)

General thoughts

The voting should be about "favourite". We thought about several categories, i.e. "more interesting" vs. "more beautiful" since that doesn't need to be the same (imagine a blurred picture of a ridiculous no trespassing sign vs. a technically perfect picture of a tree), but for most pairs of pictures such a split doesn't really work.

Given the low number of comparisons a single picture will get, and the huge number of purely documentary pictures, a simple count of won and lost votes will not do. There's too much noise in that.

Beauty is in the eye of the beholder. There is no absolute value, and there will be lots of contradictive results.

If picture 1 won over picture 2, and 2 won over picture 3, you can assume that 1 would also win over 3, but can't be sure.

An algorithm that nicely includes transitive ratings will be desirable, but difficult to implement. We should use something easier first and just collect and store the actual votes for later evaluation.

An easy version without database digging

There was an idea to use a rated count, similar to the systems some sports use. The most prominent here is the ELO system (which is quite complicated)

Sports rating systems assume that the absolute strength is a dynamic value evolving over time. A picture rating system doesn't need or even shouldn't assume that. There is no reason why the worth of old points should decline.

Sports rating systems are used to find worthy opponents of similar strength. This should not be done with a picture rating system. The bad ones shouldn't be given bad opponents to have a chance of winning, but maintain their absolute bad score (while still being able to compare their relative badness).

However, the general idea behind ELO wouldn't work too bad for us: Winning over someone with a much lower rating doesn't earn you much, winning over someone with a much higher rating gets you up.

An easy variant of that would be to give between 0 and 20 points for winning, and lose the same for losing, the actual amount derived from the difference between the current ratings of both scaled by some global factor.

Winning against a pic with the same rating would always earn you 10 points, losing -10.

The best rated picture winning against the worst rated wouldn't change their ratings by any point. "We knew that already"

Everything inbetween would scale down into the 0 to 20 range.

Now there's the issue with the global factor. Since we don't really know how the absolute ratings will develop (actually they will develop rather slow), the scaling factor should use both absolute and dynamic limits. The difference between the overall best and the overall worst score might provide a good scale, however, it has two issues:

(1) In the beginning, it's too low because it will take quite a long time until a number of pictures has a significant number of votes, scaling early votes too high compared to later ones.

(2) On a long term, it might reach astronomical heights, which means that most actual scores will be very close together relative to the overall range.

(1) could be adressed by setting an initial minimum value. (2) by using a non-linear scale (arctan comes to mind).

The overall scaling might need adjustment.

Categories for image tagging

Would it be possible to include Category:Hash tree and Category:Snowman geohash achievement in the list?

There's talk to rename them first. Category:Hash tree should be plural according to the naming conventions in Category:Galleries by topic, so that would be either Hash trees or Hashtrees. About the snowman, it might be an idea to create a category Snowmen that's not bound to the achievement, since there are a few snowmen which were not built at hashpoints (e.g. because there was no snow available at the point). Any comments? --Ekorren 12:05, 27 February 2010 (UTC)

And, I would much prefer if the categories were sorted alphabetically in each column and not from left to right. I don't know whether others agree. but for me that makes it much easier to find a category. --HiroProtagonist 11:38, 24 February 2010 (UTC)

Thanks for the suggestion on the categories, I'll get those in sometime tonight. I plan to fix up the sorting when I get a chance, but I haven't had much time to work on it the past couple of nights, and I have been prioritizing new categories over sorting by columns. --aperfectring 15:50, 24 February 2010 (UTC)

We now have Category:Winter and Category:Buses which I would like to see in the list. --Ekorren 12:05, 27 February 2010 (UTC)

I don't know that I fully agree with "Winter". In many places of the world, there is no, or little snow in winter, and thus pictures which should qualify for that category by virtue of its name, shouldn't by intended content. Busses, however, works, and I will add it. --aperfectring 02:48, 1 March 2010 (UTC)

I wasn't sure about Winter myself, and it wasn't me who introduced it, but on the choice between "Snow" and "Winter" I still would prefer "Winter". There might not be typical Winter pictures - as, for us, a typical winter picture is one with snow - in many countries of the world, but then, there also are a lot of other topics which would not be available everywhere. Still, I think collecting those great winter pictures is worth a category. And if there is something that is typical for winter in another region, just add it. Any other opinions from other people? --Ekorren 10:22, 1 March 2010 (UTC)

So here's what I gather our conclusion is: Only pictures which exemplify a typical "wintertime" photo for an area should be categorized "Winter". Just because it has some snow in it, or just because it was taken during the winter season, doesn't mean it should be classified as such. So a rainy foggy day (shown well in the picture) in the Pacific Northwest could be classified winter, but one from Germany which has a couple small patches of snow in the shot shouldn't be. Agreed? --70.102.71.170 15:27, 1 March 2010 (UTC)

That was me up there --aperfectring 15:27, 1 March 2010 (UTC)

I'm open for further suggestions, but defining it as typical wintertime photo sounds good to me. Snow is what we here in central Europe generally call typical winter, and we had quite a lot of it these two winters since invention of geohashing, but: There are years with hardly any snow just as well, and botanical seasonal changes like a leafless tree or ice covered wires are just as typical for wintertime. You know, all that talk of "white christmas" basically is myths, legends and wishful thinking. There will still be the general point that people tagging pictures tend to go for quantity instead of quality, i.e. we risk that basically every photo taken during wintertime will be tagged as "winter", no matter whether it is a typical wintertime photo or not. At some time in future, the voting may take care of that point, anyway. --Ekorren 11:15, 2 March 2010 (UTC)

Your IP address has changed (probably)

i.e. the page is down. JesseW 14:51, 15 May 2012 (EDT)