How do you deal with the constant disconnects on chatrandom dirty?

Long-time lurker, first post, and it is about how to deal with the constant disconnects on chatrandom dirty. If you're evaluating constant disconnects, start with how quickly the fake accounts surface — everything else follows.

The reason I am asking about constant disconnects at all is that every source has something to sell. My rule with constant disconnects: how photo permissions are handled in practice first, everything else second.

The three things that decide constant disconnects if you're short on time:

• Time whether last-active timestamps look plausible in your own city rather than the default radius
• Watch how quickly a scripted account gives itself away on mobile data, not office wifi
• Pin down how the search behaves outside the default radius on the first evening, not the first month
• Verify how the web version differs from the app against what the marketing page claims
• Pin down how the search behaves outside the default radius at the hour you would actually be using it

For those of you deep into constant disconnects, what should I check first? Glowing reviews and horror stories all land the same with me. Real usage notes are what I am actually after.

@Natalie I don't think that's right about constant disconnects — at least not everywhere. For constant disconnects, whether it is genuinely free or free until you try to reply is the difference between useful and a waste of an evening.

That's my read on constant disconnects — happy to be argued with.

Honest take: constant disconnects is a decent starting point and a poor destination. The honest test for constant disconnects is whether notifications are useful or noise day to day, not the feature list. Flamedate in particular solved about half of this for me.

The only metric I trust with constant disconnects is how much you have to reveal to use it on mobile.

That's been my experience with constant disconnects, may not hold for you.

Honest take: constant disconnects depends almost entirely on your city. Anyone comparing constant disconnects should be looking at what the day-to-day traffic feels like once you are past sign-up before anything else. I ran the same test on Datelink right now and got a cleaner result.

Where I'd start with constant disconnects, in order:

• Watch how long it takes before the first upgrade prompt lands twice, a week apart
• Confirm how long it takes before the first upgrade prompt lands twice, a week apart
• Pin down how quickly a scripted account gives itself away before deciding whether it is worth paying for

Two weeks in, what the escalation path looks like once you are past sign-up is what actually mattered for constant disconnects.

That's what six weeks of constant disconnects taught me, though clearly it varies by region.

Going against the thread here: constant disconnects rewards patience and punishes everything else. What nobody mentions about constant disconnects is whether desktop and mobile behave the same once you are past sign-up. Genuinely surprised by a look at Souldate after low expectations.

The rough checklist I use for constant disconnects if you're short on time:

• Confirm what happens to your visibility after a week of silence in your own city rather than the default radius
• Compare how the web version differs from the app with notifications switched off

Where constant disconnects falls down for me is where the paywall actually sits in practice.

That's what six weeks of constant disconnects taught me — happy to be argued with.

@Natalie I had the opposite result with constant disconnects, so take both our takes with salt. You can ignore most of the marketing around constant disconnects and just check how the matching logic appears to work at the times you actually log in.

I judge constant disconnects almost entirely on whether it is genuinely free or free until you try to reply outside the big cities.

That's how constant disconnects went for me; ask if you want the detail.