Key metrics

• Number of couples formed (self reported, as of 4 October, 2021): >= 15
• Number of users: 11740 (117.40% to 10k)

This what we optimize for (see explanation in the blogpost). Please reach out to me if you are a couple who met through the site.

General metrics

• Weddings (self reported, as of 4 October, 2021): 0
• Verified users: 11740
  • Female: 3834 (32.7%)
  • Male: 7850 (66.9%)
  • Non-binary: 56 (0.5%)
  • With photos: 6192 (52.7%)
    • 3321 always unblurred (28.3% of all users)
  • With "empty" profiles : 1746 (14.9%)
  • By relationship type:
    • Friendships only: 1045
    • Romantic only: 5291
    • Both: 4886
  • By FIRE type:
    • "lean": 1335
    • regular: 5904
    • "fat": 1425
  • By activity (when visited site last):
    • < 1 day: 142 (1.2%)
    • < 7 days: 422 (3.6%)
    • < 28 days: 844 (7.2%)
    • < 90 days: 1516 (12.9%)
  • By v2 design enrollment:
    • beta: 211
    • bleeding edge: 69
  • By registration:
    • < 1 day: 4
    • < 7 days: 19
    • < 28 days: 74
    • 
      
• Profile observations : 626373
  • < 1 day: 200
  • < 7 days: 1653
  • < 28 days: 6195
  • 
• Profile fullness
  • 
  • 
  • 
• Requests :
  • Sent: 99541
    • < 1 day: 53
    • < 7 days: 345
    • < 28 days: 1243
  • Accepted: 28893 (29.0%)
    • 
• Messages:
  • Sent: 313925
    • < 1 day: 148
    • < 7 days: 1268
    • < 28 days: 4623
  • Read: 296539 (94.5%)
    • 
• Geography:
  • Top 10 countries:
    • United States - 7100
    • Canada - 901
    • United Kingdom - 503
    • Australia - 408
    • Germany - 361
    • India - 243
    • Netherlands - 205
    • Russian Federation - 168
    • Spain - 121
    • Switzerland - 112
  • Top 10 cities:
    • New York, NY, United States - 308
    • Seattle, WA, United States - 298
    • Los Angeles, CA, United States - 249
    • Chicago, IL, United States - 223
    • London, United Kingdom - 201
    • Toronto, Canada - 198
    • Denver, CO, United States - 174
    • Austin, TX, United States - 158
    • San Francisco, CA, United States - 155
    • Boston, MA, United States - 154
• Last hour activity log (max 100 items)
  • [43 minutes ago] Profile seen for the first time
• Viktor's time spent (as of 1st of June 2021) : 605 hours
• Money spent (as of 1st of June 2021): 226.65 EUR (~276 USD)
• Volunteers: 6 (as of 23th of June 2021) = 3 designers + 3 React developers.
• Fun: infinity
• Learned: a lot (especially CSS, web design, public communication)
• Interesting people met: a lot, all over the world
• RAM usage
  • 
• CPU usage
  • 
• Hard drive usage
  • 
• Number of non-initialized accounts (these are not included in the counts above)
  • without validated email: 943
  • not attempted test: 571
• All known privacy incidents
  1. February 7, 2024 - Email addresses & usernames of 16 users were each exposed to a single, different user.
     I was in the process of rewriting message notification emails to include more details and make them more personalized, in the hope of receiving more responses. As part of this rewrite, I intended to include the sender's pseudonym in the title. Internally, user data is represented as a DatingProfile object. This object has a helper method "get_possibly_handcrafted_pseudonym" which returns the user pseudonym or age-gender. However, due to an oversight, I wrote "current_user.datingprofile.get_possibly_handcrafted_pseudonym" instead of "current_user.datingprofile.get_possibly_handcrafted_pseudonym()". Instead of calling the method, I referenced the method as it is. This wouldn't have been an issue, but in Python, this leads to a string "a bound method of DatingProfile...". For debugging, the string representation of a dating profile includes the username and email. As a result, both of these were unintentionally included in the email title. This bug was active for about an hour, and during that time, 16 such emails were sent out, each exposing the details of one user to another. I quickly noticed and fixed the issue by double-checking the impact of my changes. I deeply regret the unintended exposure this bug caused. I've informed all affected users, both the ones whose details were exposed and their recipients.
     I've mitigated this from happening in the future. I've removed all the user-generated information from the string representations. I will test such changes better in the future.