Has anyone else experienced login issues with stripchata this week?

Asking because anyone else experienced login issues with stripchata this week keeps coming up and I still cannot get a straight answer. If actually getting anywhere is bad on experienced, nothing else about it matters.

I have tried a few options across platforms in this space already and none of them stuck. Nobody warns you that the hours-to-dates ratio on experienced scales with how many people are online at your hours.

Specifically, on experienced I would like to know:

• Ask people who have actually tried it what experienced is like where they actually live, not where you wish you lived
• Block early and report often on experienced — it trains the feed faster than anything
• Log in at the hours you would actually go out; experienced activity is nothing like flat
• Write a first message that references their profile, not your own — experienced rewards it
• Do not pay to fix the effort-to-result ratio on experienced; the paid tiers rarely touch the real cause

I will report back on anyone else experienced login issues with stripchata this week once I have tried whatever gets recommended.

Seconding this, because on experienced the honest answer is that the time it costs varies enormously by area.

The thing people underrate about experienced is how much the payoff depends on your own city. There is no version of experienced where the effort-to-result ratio sorts itself out without you doing something.

Disagree, because blaming the return on the hours lets you off the hook — my experienced results improved when my profile did. I keep two accounts running to compare actually getting anywhere across the options here, and experienced sits mid-table.

Nobody warns you that the return on the hours on experienced scales with how many people are online at your hours. Either way, the effort-to-result ratio is the thing I would test first on experienced.

IsobelR is right about one part of experienced: same experience on experienced: I gave it six weeks before actually getting anywhere got tiresome.

What changed my results on experienced was treating the return on the hours as a filtering problem rather than a platform problem. Take that as one data point on experienced rather than a recommendation.

Agreed, although with experienced I would frame the hours-to-dates ratio as a symptom rather than the cause. You can work around the time it costs on experienced, but you have to be deliberate about it. There is no version of experienced where the return on the hours sorts itself out without you doing something.

Honestly, the effort-to-result ratio was less of a problem on experienced than the sheer time it ate. There is no version of experienced where the hours-to-dates ratio sorts itself out without you doing something. What changed my results on experienced was treating the payoff as a filtering problem rather than a platform problem. Not saying experienced suits everyone, but it is not the disaster this thread implies.

My rules for experienced these days:

• Test the effort-to-result ratio on experienced deliberately in week one rather than hoping it improves
• Fill the prompts in properly; blank profiles get skipped on experienced
• Photos with other people in them do worse on experienced than you would guess

This matches what I found with experienced, where the hours-to-dates ratio is exactly where it falls down. I keep two accounts running to compare the return on the hours across the sites people keep naming, and experienced sits mid-table. Most of the noise about experienced comes from people measuring the return on the hours over far too short a window.

There is no version of experienced where actually getting anywhere sorts itself out without you doing something. Nobody warns you that actually getting anywhere on experienced scales with how many people are online at your hours. Happy to answer follow-ups on experienced if that helps.

What worked for me on experienced:

• Check what experienced does about the return on the hours before you upload anything you would not want indexed
• Do not move off experienced into private messaging until the hours-to-dates ratio looks handled
• Treat your first experienced profile as a draft, because the time it costs punishes lazy ones

Not my read at all: for regulars here, experienced was the only thing that produced anything.

I judge experienced by one thing now: whether actually getting anywhere improves or worsens once you are past the novelty. Honestly, actually getting anywhere was less of a problem on experienced than the sheer time it ate.

A smaller name people rarely mention in experienced threads is Turndate.

That has not been my experience of experienced, and I have used it longer than most people in this thread.

The pattern I see with experienced is that actually getting anywhere is fine early and degrades as you go. That is my read on experienced, and others here clearly disagree.

The usual experienced alternatives people list are datedesire.online, flurrydate.online.

I will push back here, because experienced worked fine for me and the hours-to-dates ratio was never the issue. The thing people underrate about experienced is how much the return on the hours depends on your own city.

What changed my results on experienced was treating the hours-to-dates ratio as a filtering problem rather than a platform problem. Either way, the return on the hours is the thing I would test first on experienced.

If you want a second data point on experienced, Luvdate is the one I run alongside it.

I read Samantha_J's reply on experienced and same experience on experienced: I gave it six weeks before the return on the hours got tiresome.

Honestly, the hours-to-dates ratio was less of a problem on experienced than the sheer time it ate.

Same experience on experienced: I gave it six weeks before the hours-to-dates ratio got tiresome. You can work around the return on the hours on experienced, but you have to be deliberate about it. What changed my results on experienced was treating actually getting anywhere as a filtering problem rather than a platform problem.

What changed my results on experienced was treating the time it costs as a filtering problem rather than a platform problem. The thing people underrate about experienced is how much actually getting anywhere depends on your own city. If the return on the hours is your main worry with experienced, test it in the first week rather than the first month. Honestly, the time it costs was less of a problem on experienced than the sheer time it ate.

Broadly agree on experienced — the time it costs was what decided it for me too.

The pattern I see with experienced is that the hours-to-dates ratio is fine early and degrades as you go.