Presenting... Replit User Search v3
Heya, it's me! I haven't posted anything in some time, so here's a kewl little project. Ever wanted to look for a Replit user, but didn't know what their username was?
Presenting... Replit User Search v3!
OPEN IN A NEW WINDOW
My previous two search engines are defunct, broken, and just no longer good solutions. This new search engine is a full-stack NextJS project that utilizes actual Replit API's to give you the best search experience.
It's very simple!, first log in via your Replit username/password*. Then start typing a username and watch as search results pop up!
I hope you enjoy this project, and hope it remains useful longer than the previous two search engines xD. Please leave suggestions and bugs below, I'll address them when possible!
Website URL: https://replit-user-search-v3.rayhanadev.repl.co/
Repl URL: https://replit.com/@RayhanADev/Replit-User-Search-v3
Github Repo: https://github.com/RayhanADev/Replit-User-Search-v3
* I need your username/password to get some cookies, and ReplAuth doesn't provide them so I use the actual login API. For those with concerns about typing in usernames/passwords just know I don't store your credentials, the website is serverless, and the API is the same one you use to sign in on Replit! I grab a
connect.sidcookie when you sign in so that I can use authenticated GraphQL queries (which username search requires). You can also login with just the sid via this url.
Also if you want an explanation:
Some GraphQL queries (userByUsername, posts, comments) don't require
connect.sidhowever others (mainly mutations, but also currentUser and userSearch) need a valid
connect.sidtoken to perform the query which is why I use the Login API to get the cookie.
I used SID because of GitHub login but it works great otherwise! Maybe add other logins and it will be helpful for us OAuthers.
@JakeHu2020 then I would go to your cookies, look for one called
connect.sid and then go to https://replit-user-search-v3.rayhanadev.repl.co/login?useSid=true and put the value from the cookie.
it would be better to use repl auth and the repl talk api because your connect sid cookie is sensitive information, but other than that this is cool!
(please make sure this is absolutely secure and won’t leak user information)
If this was a scam do tell why so many people still used it? Do tell why moderators haven't taken down this post? Do tell why me, a moderator myself, would try to run a scam. The application is serverless anyways so anything you see is done on your browser. Do you really need me getting more defensive?