Topic: viewing all members temporarily disabled? (Read 1119 times)
ted and ted* produce the same results.
Dogie, can you clarify what you meant by using *.?
I think he meant searching like so:Code:
ted*
the dot at the end was used to denote the end of a sentence.
Thanks, got it. FWIW, that doesn't actually seem to work. If I search "ted*", I see, inter alia, "unsolicited" (ted at the end of the string), "tedstein" (ted at the beginning of the string) and "twistedtime09" (ted in the middle of the string). It would be nice to be able to constrain the search, I think.
Dogie, can you clarify what you meant by using *.?
I think he meant searching like so:Code:
ted*
the dot at the end was used to denote the end of a sentence.
What do you guys would like to see the Members list for? 
I often want to look at the profile/recent posts of some member who's account name I know but where I can't remember the last threads I saw him/her in. For that reason, I'd like to be able to use the find members functionality better.
Dogie, can you clarify what you meant by using *.?
What do you guys would like to see the Members list for?
Theymos, could you not put it on Github or a Google Doc in order for uers to download the information and use a DBMS to systematically analyse the information in it. That may speed up the forum traffic and could speed up the efficiency of the server.
You already can with *.
The dot is a separator? So if I'm trying to find a user "Ted", how do I use the star-dot syntax to avoid finding "unitedpx"?
I found this feature around the same time I found the seclog and could never figure out how to search effectively. Hope what comes down the pipe is easier to navigate.
Actually I have similar issues searching the forum.
Tend to go to google if its broader than a thread search. Make it easier for us Turtles.
Actually I have similar issues searching the forum.
Tend to go to google if its broader than a thread search. Make it easier for us Turtles.
It was working a few days ago but at a speed of a turtle. No, It was slower than a turtle. I guess there is a problem with the code or the database just needs maintance, probably that's why they disabled it.
You already can with *.
I don't know if it's easy to implement, but if you could add something to make it easier to search, say at the beginning of a word rather than anywhere. Let's say you're trying to find a user "ted", right now, searching "ted" returns all users with that substring in their name. It would be nice if you could say "^ted$" or something like that.
It's too resource intensive. I need to figure out some way to make it faster.
The search still works.
The search still works.
Why?
Jump to: