what you are thinking of, in whatever form, requires multiple joins on the "ignore list" table.
You're thinking too big and too unoptimized. Any joins would be very small, number matrix joins of data that would only be fetched once per page request in the worst case:
requesting member ignore list uids x post "quoted user" uids (mostly 1, rarely >= 2, often 0)
And of the three major steps of normal forum usage, these small, simple comparisons would only be needed in steps two and three.
Some server-side functions that would need modifying:
You're thinking too big and too unoptimized. Any joins would be very small, number matrix joins of data that would only be fetched once per page request in the worst case:
requesting member ignore list uids x post "quoted user" uids (mostly 1, rarely >= 2, often 0)
matrix?
i'd see a tensor / 3rd dimension (10 posts per page)?
And of the three major steps of normal forum usage, these small, simple comparisons would only be needed in steps two and three.
you see, this is where i start having a problem...
what if your feature has such a success that everybody starts adding 1/2 a dozen ppl to his/her ignore list...
user opens forum page
for all the authors of posts on that page, check normal ignore list
for all posts with quote, check if quoted author is on ignore list
like i put on the 1st quote now, i removed the ID part thus you are not identified as author any more but it's still your post, isn't it?
my main problem, i still don't understand what more / else you intend to implement, thus...
simply don't display a post quoting an listed author?
what if a post quotes several posts from different authors?
Some server-side functions that would need modifying:
Add, change or delete a post
Request a list of unread threads
Request a thread
when i see your last list, i can't help feeling i'm missing something here...
like i said, not clear to me what your feature will achieve, thus tricky to asses the impacts. which is a no-no in terms of development. no offence.
