|
Ignore feature. (pg. 3)
|
View this Thread in Original format
| paranoik0 |
| quote: | Originally posted by Arbiter
The only problem I see is that the algorithm probably retrieves a constant number of threads and displays them, so if you had ignored threads in the bunch it might display fewer threads on a page than it otherwise would. This could be avoided by repeating the querying process until threadsperpage threads have been displayed, but this would place additional stress on the database which may not be worth it. |
both cases shouldn't be a problem i think? most users should have very few people (none even) in their ignore list, so the aditional stress to the database wouldn't be big. also it isn't a huge thing that less threads would show up. maybe the best solution should be some message like "ignored thread" in the place of it |
|
|
| StereoPrincess |
| quote: | Originally posted by paranoik0
both cases shouldn't be a problem i think? most users should have very few people (none even) in their ignore list, so the aditional stress to the database wouldn't be big. also it isn't a huge thing that less threads would show up. maybe the best solution should be some message like "ignored thread" in the place of it |
yes, that is what i want. |
|
|
| DigiNut |
| quote: | Originally posted by Arbiter
I don't think it should be that hard. Every time a thread or group of threads is retrieved from the database it must retrieve the username of the thread starter of each thread in order to display that column on the forum table.
So the each "row" result of the query probably contains a field like 'thread_starter.' It would be pretty easy to simply compare that field to the contents of the logged in user's ignore list and not echo the row of information if a match is found.
The only problem I see is that the algorithm probably retrieves a constant number of threads and displays them, so if you had ignored threads in the bunch it might display fewer threads on a page than it otherwise would. This could be avoided by repeating the querying process until threadsperpage threads have been displayed, but this would place additional stress on the database which may not be worth it. |
Actually come to think of it, it's probably very easy to implement without putting any stress on the database.
If it's a SQL database, the threads are probably retrieved using an sproc that doesn't and can't take any user-specific parameters (just generic ones like forum ID and how far back to retrieve posts from), so changing the database itself to handle the issue would be nearly impossible. That's what I was originally thinking about but then I realized that there's no need to change the database at all.
Since the PHP script has to parse through all the returned records anyway to display them, all Del would have to do is stick an extra 2 or 3 lines in the PHP script with an "if" statement that checks against the ignore list and just doesn't display the record if the user is ignored. So we're not trying to modify the query's result set, just ignore some of the records inside it. I think that's essentially what the "in-thread" viewer script already does, it's just not implemented in the thread "list" script.
The thread count might end up being wrong, but in that case you could just add one more line to the if statement that decrements it for every record that gets ignored.
That should be pretty simple, right Del? I know you're a busy guy but I think this is actually a lot more straightforward than it seemed at first. :) |
|
|
| StereoPrincess |
he is back!!!
bastard.
anyways, yes, please change the whole site just for me Del. :) I won't care how many threads per page. |
|
|
| StereoPrincess |
| why god?? why?? |
|
|
| j_spot |
| Im with margs on this one. |
|
|
| StereoPrincess |
| quote: | Originally posted by j_spot
Im with margs on this one. |
it has been really bad this past week, eh? |
|
|
| Vivid Boy |
| ok well this is what we gonna have to do. we as a community have to flame the out of him till he runs away on fire. since im on his ignore list and rod rico is as well we need a team effort. since me and rod are the ones that flame him the hardest and he has us on ignore i say whenever we flame him you people should quote us so he can read it. disguise it too. when u quote us just add a lol so he doesnt think ur quoting on purpose. we need help from everyone tho. stp digi lkd, whoever |
|
|
| Jocker |
| quote: | Originally posted by DigiNut
That should be pretty simple, right Del? I know you're a busy guy but I think this is actually a lot more straightforward than it seemed at first. :) |
it's simple to code... i can even tell what the code is (or what i'd write) but when you think that this additional database query will be run each(!) time every(!) user reloads a forumdisplay page, it adds yet another considerable bunch of load on the server.
but then again, ta has the "thread preview" thing, which is, i must say, the biggest rape of servers and waste of bandwidth seen from vb - or any php script for that matter - yet:) |
|
|
| Jocker |
| as for flaming the out of or banning someone just because somebody else is annoyed by his posts, i think, is rather immature and discriminatory. |
|
|
| StereoPrincess |
| quote: | Originally posted by Vivid Boy
ok well this is what we gonna have to do. we as a community have to flame the out of him till he runs away on fire. since im on his ignore list and rod rico is as well we need a team effort. since me and rod are the ones that flame him the hardest and he has us on ignore i say whenever we flame him you people should quote us so he can read it. disguise it too. when u quote us just add a lol so he doesnt think ur quoting on purpose. we need help from everyone tho. stp digi lkd, whoever |
dude, we tried that with you but you just got stronger. we have to think, what would get you to leave, and do that. |
|
|
| Swamper |
| quote: | Originally posted by Jocker
it's simple to code... i can even tell what the code is (or what i'd write) but when you think that this additional database query will be run each(!) time every(!) user reloads a forumdisplay page, it adds yet another considerable bunch of load on the server.
but then again, ta has the "thread preview" thing, which is, i must say, the biggest rape of servers and waste of bandwidth seen from vb - or any php script for that matter - yet:) |
Thread Preview (surprisingly) seems intensive but isn't, when you retrieve all the thread info from the thread table there is also a left join on the icon table to obtain icons (if any) for that particular thread (within the same query) - a left join is also done on the post table to obtain the preview text of the first post (whose postid is already within the thread table). In order to handle the ignoring of users I would have to throw the user table into the fray and check that as well - it may slow things down a bit - and - I would try it, but, to handle the 0.0000001% of cases when it would matter - seems pointless to me. |
|
|
|
|
