Should be added now if you refresh your Profile page. I've added an Account Settings button that lets you reset all your card votes and delete your account and all its data.
Should be added now if you refresh your profile page and click "Account Settings" there. I've added a feature for resetting all your votes and deleting your entire account.
I think you are 100% right here. Wow, thanks so much. This really is amazing. I'm going to begin work on this soon (just need to get some sleep first!)
Haha, this is actually still an open question. My marketing thus far has been exclusively just posting it on a couple subreddits and this Hacker News thread. I don't think I've yet achieved traction because there aren't enough users to sustain interest so most people get bored pretty quickly and log off, but I'm working on it! If I figure this out I'll let you know though.
Another fantastic reply! I really need to get this to take off already so I can hire you before you make your own and out-compete me.
The more I read this reply, the more I agree with it, and I think it may actually not be that difficult of a change. Card sets could be integrated into the existing cluster concept and I could just give users the ability to choose which sets (clusters) they swipe on and the weighting that they apply to each. They could also decide which clusters should be factored into their similarity matching. I _think_ this will all work with the existing CUBE concept, which is exciting, because many other proposed solutions by others didn't fit nicely within that mathematical structure.
You've honestly given me a lot to think about and I think I see a better way forward now. Your insight really increased my mood because I think you've discovered something very important that I am likely going to be spending quite a bit of time on in the next coming weeks and months.
Wow, this is an incredible reply. Thanks so much for such an in-depth analysis and compliments!
I actually really like your mock-up and really appreciate that you took the time to make it. Hopefully you don't mind if I take quite a bit of inspiration from it, because I definitely think it looks much better than my current one.
Yeah, I agree that the network effect is one of the biggest problems. Retention seems very tricky with a concept like this because while posting it to reddit or HN can result in many registrations, few people stick around because there isn't much to do on the site because there's so few users at the moment. It honestly does make motivation pretty difficult, but I am indeed going to stick with it regardless.
With regard to your last 4 numbered points, currently 0% == not answered == neutral, and this is mostly due to technical limitations. Your default similarity cube is just (0.0, 0.0, 0.0, 0.0, 0.0, ..., 0.0) (50 zeroes), and voting on cards adjusts this accordingly. Such that if you answer 100% to every card in the first cluster and answer no other cards then your CUBE would look like (1.0, 0.0, 0.0, 0.0, 0.0, ..., 0.0)
I was thinking about a potential way to solve this, but as of right now due to the constraints of CUBE similarity matching, this is the current solution.
Yeah, the first pass for the clustering was SciKit's Agglomerative Hierarchical Clustering Function and then the clusters were manually tweaked in an attempt to increase accuracy. Clusters are also manually updated and curated, so hopefully they shouldn't be able to be gamed at the moment.
Yeah, a lot of people have been requesting this. In the interim you can go to the Cards page and click on cards and change your votes there to baseline. This has been a heavily requested feature though and I'll be adding the ability to reset your votes and delete your account this week.
This is actually something that I'm still trying to figure out, and hopefully can be improved in the future. Maybe you can help me out:
So, the problem we'd like to solve is what set of 250 or so cards has the highest predictive value in that similar answers lead to the best interpersonal matches?
The problem with hobbies is that there are so many of them and not many people feel very strongly one way or the other about many of them. You probably wouldn't not give someone a chance just because they prefer ping pong to pool, for example. Rather, I was looking for what might be deal-breakers.
The Interests page and tagging in general is what I am hoping will fill that need of specifying your individual interests and matching based on them. Here is where you can tag yourself with whatever you'd like and then search for users and posts based on these tags. The card swiping's function is mostly just a first-pass elimination filter.
I had the thought of perhaps doing categories instead with regard to cards. For example, sense of humor is often very important in people. Perhaps 50 of the cards should be memes? And then perhaps 50 of the cards be political, 50 of the cards be hobbies, etc.? Or perhaps there could be multiple similarity percentages, each of a different category? It's still very experimental and I'm not sure what the correct path is.
In the beginning it was a bit tricky because the migration to async was happening within the Rust community, so that caused some code churn early on. Lately though it's been smooth sailing.
I'm using tokio-postgres for my database library and both it and Rocket are async, so they synchronize very well together. I do not believe Diesel is currently async, but in either case I'm using tokio-postgres instead so I haven't had to look into how to integrate Diesel with Rocket.
Other than that, my needs were pretty simple and I used well-supported platforms, so I haven't really run into any major issues yet.
So, the clustering situation is a bit of a double-edged sword. Here's the pros and cons I've found:
Pros:
1) Allows for instant similarity-searching. I am using the Postgres CUBE data structure to index users' votes and it has a limit of 100 items. So, if I didn't use clusters then there could only be 100 cards maximum, but ideally you would have even less than that because the CUBE can start to slow down when you approach that limit.
2) It's also a bit of a privacy feature as people can only see how you voted along cluster lines, and not how you voted on individual cards. This provides the aforementioned plausible deniability.
Cons:
1) Not all clusters are ideal, as you've seen. I spent a lot of time exploring different clustering algorithms and none of them were perfect. Some cards were naturally a part of multiple clusters and others didn't align to any at all. I'm sure a lot of this comes down to card choice, which I definitely could improve.
2) Can be confusing to users as opposed to just listing theirs and others votes on cards.
---
If you'd like to help and create better clusters, I'd definitely be open to tweaking them. Most of the required data can be found by navigating to the Cards page. For example, if you go there and click "War on Drugs" and then click "View Correlations", you'll find that "War on Terror" correlates the most with "War on Drugs". This data can then be used to try and create your own clusters. I've found it to be a very tricky puzzle satisfying all the constraints.
In the end, for performance reasons, I felt like I had to choose between either having clusters or only 50-75 cards, and I chose clusters. There's probably a better way of doing it, but I was unable to find it at the time.
I'm glad you're a fan too! Yeah, vanilla Javascript seems pretty powerful these days. If you don't care too much about backwards compatibility or supporting really old browsers then you can get a lot done with really thin wrappers tailored to your use case. I suppose time will tell whether or not it was the right decision, but in the meantime I really like the peace of mind from not having to rely on npm.
This is very good insight and I definitely agree. With regard to your first point, I'll look to add a limit to how many users a person can message per day.
I spent some time already and plan to spend a lot more on moderation tools to mitigate the effects of your second point. Ideally fake profiles can be both reported and detected, but as of yet I have not invested too much time into these efforts, other than adding basic reporting features and a moderation page for those with sufficient power.
I tried to mitigate your third point by only allowing users to see your total cluster vote as opposed to your individual card votes. As a result, there is a bit of plausible deniability as your vote for each card is somewhat masked by the average. This could be furthered by reducing the cluster count and thereby making each cluster larger and mask more individual card votes.
Right, that is a very good point. That reason is why I neglected to add a gender option, as I felt the inclusion of that filtering criteria would steer the culture towards that of a dating site.
As for its reason for being, it's mostly because I just think it's a bit of a shame how there could be this awesome person down the street or in my city, and I could live my whole life without finding that out. I was hoping to develop a service that might alleviate that.
For example, if you were into some obscure Steam game, you could specify that as an interest and potentially see that someone else near you also shares that interest as well. You then might message them, play together, and then if you hit it off some time down the line you could eventually meet in real life as well.
Hmm, yeah, the swiping UX seems to be pretty tricky to get right. Initially I didn't have the percentage but some early testers highly recommended I add it for two reasons:
1) They couldn't see well and found the addition of the percentage was helpful in clarifying their swipe value.
2) It made it more obvious that the magnitude of swiping mattered, as opposed to swiping just being a binary yes/no option.
The two concepts idea is interesting. I'll have to think more on that. I think it might be tricky to implement though, because not every topic has a natural converse.