The Dot Hack

This is the Dot Hack:



The point of the hack is that it will place a dot on each thread that you have posted in. I think it is a great hack, what do you think?

I would like to release it but you have to modify the search index function and update the threadindex field for every user. If John wants to include it in the new version I will send him the code and give him hints on how to make the threadindex and search by user functions more robust, as I have done.

I can do that but it would have nothing to do with the dot hack. I will see about giving you code that will achive what you want. Just add it to my long list of stuff to do.

Should be able to just do a left join with the fav_threads table to achieve what you want. You will have to create the glowing icons though.

How are you determining if the user's posted in it?

Splitting up the data with explode, and cycling through with a loop?
If so, you might want to look into strpos or strstr for a more optimized solution.

I forget, let me check ...

yes strpos of ",username," as I used commas to delimit the threadindex.

Otherwise if you have a user named "joe" and "joe blow", doing a strpos of " joe " will return true if "joe blow" is in the index with its current usage of a space as a delimiter.

Great, nice and optimized

Just a thought, but wouldn't adding the User ID to the query instead of using the username be more reliable?

peter you don't fully grasp what is going on as I would be the last person to ever use a username in a query.

Threads already contain an index of the users in the table. So I saved doing a query on the post table to see who has posted in a particular thread by just using the index that is already available to me, hence the matching of names.

Ah, well.

any luck in getting john to change this for version 2.0? another great hack i would like.

I have no clue Chris, as I have said, I have no contact with Jelsoft. There does exist a bug since you cannot use a space delimiter when the data itself may contain spaces. Mike/Ed has said all "known" bugs have been fixed in 1.1.4 so perhaps they have changed the delimiter, if not then all known bugs haven't been fixed.

I made a bug report about this maybe 4 months ago but only in the last 1-2 months have I come to known vBulletin in and out so it became obvious to me what the problem is.

ok cool. We can but wait