How about each search gives you temporary list of images with their links stored in a cookie(memory) that gets renewed with each post? Im not sure how this would work with multiple konachan pages though.
Other work around would be a facebook style picture opening in a new window while search page is still in the back.
Other work around would be a facebook style picture opening in a new window while search page is still in the back.
NO, no no no. I don't like that, I hate those types of viewers.braincruser said:
Other work around would be a facebook style picture opening in a new window while search page is still in the back.
Posts opening in new tab was put down before I think.
If you want it in a new tab then ctrl+click, FireGestures, 3rd Button
If you want it in a new tab then ctrl+click, FireGestures, 3rd Button
we are talking about previous and next buttons on search images
Suffice to say the DB for Konachan is not as robust and flexible as I thought or would like (Shuugo feels the same way at times whenever I bring up DB-related functions and features ^_^;).
I won't get into details (because I don't know all of them and what I DO know is pretty dull anyway), but the way the DB stores and handles data is fairly convoluted for a DB-based system. It's great for what it does (tags, images), but sucks at pretty much anything else (it's a bloody fucking bitch for maintenance and administration from what Shuugo tells me.) If you want an idea of how convuloted it is, there's a reason we simply don't delete unused accounts: the data is stored over like 5 tables and you'd have to find and delete the relevent data on EACH one manually, one table at a time. (They don't cross-link very well, if at all.)
This is part of the reason why the Dmail message list system is annoying (i.e. you can't delete older messages), though in this case the the cause is the complete opposite: the system store one instance of the message and links the 2 accounts to that message. So one user deleting the message would delete the message for BOTH users. Though I have spoken to Shuugo about alternate options for managing the Dmail system so you don't have to stare at message all the way back to when you first joined (or you know, the countless "Your user record has been updated" messages we mods generate on a daily basis for bans and warnings.)
I won't get into details (because I don't know all of them and what I DO know is pretty dull anyway), but the way the DB stores and handles data is fairly convoluted for a DB-based system. It's great for what it does (tags, images), but sucks at pretty much anything else (it's a bloody fucking bitch for maintenance and administration from what Shuugo tells me.) If you want an idea of how convuloted it is, there's a reason we simply don't delete unused accounts: the data is stored over like 5 tables and you'd have to find and delete the relevent data on EACH one manually, one table at a time. (They don't cross-link very well, if at all.)
This is part of the reason why the Dmail message list system is annoying (i.e. you can't delete older messages), though in this case the the cause is the complete opposite: the system store one instance of the message and links the 2 accounts to that message. So one user deleting the message would delete the message for BOTH users. Though I have spoken to Shuugo about alternate options for managing the Dmail system so you don't have to stare at message all the way back to when you first joined (or you know, the countless "Your user record has been updated" messages we mods generate on a daily basis for bans and warnings.)
I've made simplified copy of konachan in two days (lol, google indexed it). It's not that sad.
The "cross-link" thing is called constraint and has option for "delete cascade". It's disabled for safety (or you can delete half site with one request). Designing such complex systems as kona for easy deletion is pain, it's often replaced by marking objects as deleted/hidden.
In my opinion relational databases aren't suited for large tag clouds (many-to-many). Every tag assigned for each post makes one row in single table. This results in millions of rows. And to get one page having posts with tag A (or worse tags A and B, but not C) db needs to check these millions, sort resulting set and return little part. More fun to view second page - same actions, but skip first part from page 1 and return second (this is why viewing page 1000 is slower than 1st).
More on topic: you may implement Next-Previous for search on client-side - get JSON with N results and compose page for the first post keeping others in memory. On server-side it'll require many resources to keep all sessions, but on client it's relatively easy. It's more like google images works. Alternative clients use same method (forum #7624).
I may help with implementation.
The "cross-link" thing is called constraint and has option for "delete cascade". It's disabled for safety (or you can delete half site with one request). Designing such complex systems as kona for easy deletion is pain, it's often replaced by marking objects as deleted/hidden.
In my opinion relational databases aren't suited for large tag clouds (many-to-many). Every tag assigned for each post makes one row in single table. This results in millions of rows. And to get one page having posts with tag A (or worse tags A and B, but not C) db needs to check these millions, sort resulting set and return little part. More fun to view second page - same actions, but skip first part from page 1 and return second (this is why viewing page 1000 is slower than 1st).
More on topic: you may implement Next-Previous for search on client-side - get JSON with N results and compose page for the first post keeping others in memory. On server-side it'll require many resources to keep all sessions, but on client it's relatively easy. It's more like google images works. Alternative clients use same method (forum #7624).
I may help with implementation.
Any idea how to search for images without a source? I mean... only images with no source whatsoever?
Closest thing I can think of is -source:*.
Doesn't work.
Having same problem with stars as kumacuda, also using Chrome 12.0.742.91.
Seems the "-" mode doesn't work for that meta-tag in searches.Tensa said:
Doesn't work.
I've notice the parent and child posts are constantly switching with one another lately. My guess is that users(mostly new) meant to click on the "parent post" but clicked the "make this the parent" option instead >.< Maybe because the two options are so close to one another. It's no big deal but gets a little annoying at times because it happens so often.
^ So how about putting that "Make this the parent" button among the left menu "button", like Add to Favorites and View Original?
Looks like a chrome bug... I'm using the same version for mac and it has the same problem.Cacha said:
Having same problem with stars as kumacuda, also using Chrome 12.0.742.91.
The easiest thing would to hide it for people that it's not contributor or higher user level. What do you think?opai said:
I've notice the parent and child posts are constantly switching with one another lately. My guess is that users(mostly new) want to click on the "parent post" but clicked the "make this the parent" option instead >.< Maybe because the two options are so close to one another. It's no big deal but gets a little annoying at times because it happens so often.
That would be the easiest* solution for now, unless someone else comes up a better option later on.
Redesign sign up to include a recaptcha so as to weed out the bots.
You could use a specialist, suitably themed, one located on-site, but it would need it's images changed every so often. IPB Forum didn't change images often enough and eventually the previous version's captcha got cracked (they released a new version a bit over a year ago).
You could use a specialist, suitably themed, one located on-site, but it would need it's images changed every so often. IPB Forum didn't change images often enough and eventually the previous version's captcha got cracked (they released a new version a bit over a year ago).
Actually, Shuugo brought that up/mentioned that idea to me not too long ago (when I started doing user list reviews to spot bot accounts.)
I'm also thinking we should hide the "Add to Pool" link for non-contrib & above users as well...
I'm also thinking we should hide the "Add to Pool" link for non-contrib & above users as well...
I always wanted that Make a new pool lock to Members. If they need to make a pool there plenty of Reg's who can do it.StahnAileron said:
I'm also thinking we should hide the "Add to Pool" link for non-contrib & above users as well...
To be honest, the only users who NEED to make pools are the mass uploaders, most of whom are Contribs anyway, so they know what they're doing. Wiresetc, oranganeh (speaking of whom, I think s/he should be bumped up to Contrib), and a handful of others being examples of those that upload a lot and know how to use pools correctly.
Perhaps we should consider instating the "Privileged" rank and locking down "Member" rank a little more?
Perhaps we should consider instating the "Privileged" rank and locking down "Member" rank a little more?
A not so sensitive search engine, It gets annoying sometimes when you have to put "-" in between each word, for example; "Higurashi-no-naku-koro-ni", when you could just type it like "higurashi no naku koro ni" instead. (Not complaining, just saying.)
That is complaining because you're saying it's too sensitive.AlexHigurashi said:
(Not complaining, just saying.)
And it's a _ not a -...
Easy to say, hard to do. Also there's the autocomplete which should solve most of the problems.AlexHigurashi said:
A not so sensitive search engine, It gets annoying sometimes when you have to put "-" in between each word, for example; "Higurashi-no-naku-koro-ni", when you could just type it like "higurashi no naku koro ni" instead. (Not complaining, just saying.)
I've done a lot of tag maintenance lately and sometimes I stumble upon tags that we don't use normally here. But as soon as I search for images that are using these tags, those images are already deleted. So I'd like to be able to delete those tags from already deleted images. I just like it "unmessy". I know normal users (like me) were able to do that some time ago, but that ability was cut down (for understandable reasons).
Hrm, this isn't really a suggestion, more a bump on the idea with privileged accounts *cough*
Hrm, this isn't really a suggestion, more a bump on the idea with privileged accounts *cough*
You mean the images that you removed a certain tag, and then you search with that certain tag and get nothing although it says like ... "<tag> 6" or something like that? Give you a number after the tag yet there is no image? If that's it, I don't think it will be possible. I mean, nor can we Contributors do that. Only mods and admins. Even so, in a day or so it will go away. That tag, that is. So you don't have to worry about it.
Hrm, okay, if it really is a fully automatic thing then I just have to bite my lower lip and be patient. But if this needs manual maintenance ... *lifts a hand*
It gets cleaned every 6 hours...
There are a few times back when I was non-mod that that 6 hour clean up didn't for what ever reason or whatever clean up thing you at on at thei time, I haven't seen it lately tho, Charly if you do see it, screen cap it and send it to Shuugo.
It seems that clicking on one's avatar gives you an error.
edit: Fast fix is fast?
edit: Fast fix is fast?
That was the maid's fault.
kisumi
almost 2 years agoI can see what Stahn's saying though, and if it's too much then it's too much.