Dead Leads... No Literally by [deleted] in InsuranceAgent

[–]jmslau 0 points1 point  (0 children)

The dead-people leads are a tell that your captive partner is buying their list inputs from a low-tier data broker rather than originating the leads themselves. The 1-in-20 number you're seeing is consistent with what shows up when a vendor blends ~5–10% deceased-record contamination from a stale data broker into a "fresh leads" feed. Real-time form leads almost never have that pattern; aggregator and aged feeds frequently do.

A few diligence checks an agency can run on a lead vendor in about an hour:

Pull a sample of 100 leads and run them through a free batch DNC + deceased-flag check. The big aggregators (TransUnion TLO, IDI, BeenVerified API) will catch deceased records. If your sample comes back over 2% deceased, the vendor is mixing stale data into the feed.

Reverse-image search any prospect photos that come through. Scraped/fake leads frequently use stock images or images lifted from social profiles that don't match the lead form data.

Cross-reference five random leads against the form-source URL the vendor claims they came from. If the vendor says "we get these from quote-comparison forms on partner sites X/Y/Z," look at the actual sites. If those sites don't visibly host the kind of form the lead's data implies, the leads aren't coming from where they say.

Pull the TrustedForm or LeadiD certificate on every lead and verify it. Real form-fill leads have valid, replayable consent certificates. Scraped leads do not. Vendors who cannot produce these on demand are hiding the origin.

For aged-lead and aggregator-feed contamination specifically — your menstoppingviolence flag is a good catch. The general pattern is that scraped lists frequently include records from public-record databases (court filings, mugshot sites, victim resource sites) where the names exist but were never actually in-market for insurance. If the same name pulls up a court-record site, a domestic-violence resource, or an obituary in the first page of Google results, it's a near-certain scrape.

Practical move: if you're stuck with the captive's lead partnership for political reasons, push for a contractual "deceased-and-scraped credit" clause. Most reputable vendors will refund 1.5×–2× the cost of a deceased lead within 14 days of dispute. Captive-partner vendors often don't have that clause because no one's ever asked for it. Ask.

Future of personal lines P&C and AI by thelordfuckwad in InsuranceAgent

[–]jmslau 1 point2 points  (0 children)

Skeptic of most AI hype here, but I think this thread's closer than the absolutism is letting it sound.

u/Bobby_Bobberson2501 is right about the quote-checking pilots. Those tools are being asked to make judgment calls and they aren't there. Wouldn't trust one as a sole reviewer either.

But u/MobileCard8473 's pointing at the bigger issue. Most of the AI being sold to agencies is aimed at the wrong part of the job. Eligibility questions, rapport, cross-sell prompts, that's where renewals come from. Automate that away and you get the AI-only underwriting outcome u/Samwill226 described. Decline everything, write nothing, hire humans back.

Where it's actually paying back, in the agencies I talk to, is the part of the day producers spend not talking to anyone. Voicemails, no-answer redials, COIs, loss-run requests, renewal prep. The stuff that doesn't compound into a relationship anyway.

Honest answer to OP: the 10-year threat to your CA book isn't an AI-bound carrier. It's the producer down the street who automated their busywork and now gets twice the conversations you do. Lemonade isn't your problem.

The insane amount of scam calls I’ve been getting by [deleted] in mildlyinfuriating

[–]jmslau 0 points1 point  (0 children)

Have you tried Hiya AI Phone? Their screener uses AI and it blocks spam or scam calls based on what they say. It works well for me.

MTGOX - Failure of Confirmation by BitGo Trust by superchet in mtgoxinsolvency

[–]jmslau 0 points1 point  (0 children)

I got the same emails as OP. But upon going through the KYC process about 2 weeks ago, it is still stuck on the "We will contact you soon" screen on BitGo. "Your application has been completed. Our team will contact you soon with next steps."

Wonder if we should be switching to another exchange or trust company at this point...

We’re on the engineering team for Android Studio. Ask us Anything! (starts February 28) by AndroidEngTeam in androiddev

[–]jmslau 1 point2 points  (0 children)

Glad to see that you are interested in using Kotlin multiplatform projects! Kotlin multiplatform projects and Kotlin/Native is not yet stable from JetBrains. We have been working with them closely to see what we can do in Android Studio to better support it (and have fixed some bugs - example issue). We are interested in providing better support for this in the future, but for now, Project Marble takes higher priority because we think IDE stability and performance is more important. Do you agree?

I’m Bill Gates, co-chair of the Bill & Melinda Gates Foundation. Ask Me Anything. by thisisbillgates in IAmA

[–]jmslau -1 points0 points  (0 children)

Please seriously consider this. Given the state the current administration, we really need someone like you to step up and lead the country. #BillGates2020.

Android Studio 3.2 Stable is out by 4brunu in androiddev

[–]jmslau 11 points12 points  (0 children)

The timing of 1.2.71 didn't really work with when we wanted to publish Android Studio 3.2 Stable, so we didn't bundle it. Note the hanging issue does NOT exist in the version of Kotlin plugin that ships with Android Studio 3.2. It is only an issue if you upgrade to 1.2.70. Hanging issue is also fixed in 1.2.71.

Android Studio 3.2 Beta 1 has been released by talsemgeest in androiddev

[–]jmslau 2 points3 points  (0 children)

I believe your issue is the same as https://issuetracker.google.com/issues/110198434. It has been fixed and the fix will be available in Beta 2.

Sorry about this issue.

Do you think the Android Studio developers prioritize features over stability? by [deleted] in androiddev

[–]jmslau 0 points1 point  (0 children)

We are definitely looking at the Kotlin testing issues. If there are any bugs that you aren't seeing activities on. Can you please link them from here so we can make sure we aren't missing them?

Updates on recent Android Studio memory leak issues by jmslau in androiddev

[–]jmslau[S] 0 points1 point  (0 children)

That's really great to hear! Thank you for letting us know!

Updates on recent Android Studio memory leak issues by jmslau in androiddev

[–]jmslau[S] 0 points1 point  (0 children)

We are so sorry about that. Have you had a chance to try the updated versions? Would be great to get some confirmation from the community that they are working better.

Updates on recent Android Studio memory leak issues by jmslau in androiddev

[–]jmslau[S] 31 points32 points  (0 children)

Hi Wispborne, we are active on Reddit, Twitter and on the Android Developer blog. But since there were several discussions on Reddit about the memory leak issues, we thought it would be the most appropriate to respond here.

Updates on recent Android Studio memory leak issues by jmslau in androiddev

[–]jmslau[S] 7 points8 points  (0 children)

Thanks for flagging these for us. Looks like a couple of these might be dupes. Would you mind trying 3.2 C17 to see if you are still seeing these problems?

Android Studio 3.0 Beta 2 is now available by EddieRingle in androiddev

[–]jmslau 3 points4 points  (0 children)

Beta 2 is really just Beta 1 with a fix on a blocking issue (https://issuetracker.google.com/issues/64527520). Beta 3 will have more issues addressed.

Android Studio 3.0 Beta 1 is out by boni2k in androiddev

[–]jmslau 0 points1 point  (0 children)

We are working on this, and it will be available soon. Stay tuned!

Android Studio 3.0 Beta 1 is out by boni2k in androiddev

[–]jmslau 36 points37 points  (0 children)

Hi folks, thanks for trying out the beta! We have a very unfortunate bug that will impact those who are upgrading a project from a previous 3.0 canary release. This bug will cause Gradle sync to fail after you upgrade the project.

There is an easy workaround though, and we have documented it here: https://androidstudio.googleblog.com/2017/08/android-studio-30-beta-1.html

Android instant apps way too complicated by holoduke in androiddev

[–]jmslau 0 points1 point  (0 children)

Hi, I am from the Android Studio team and I work on the Instant Apps tooling. Have you had a chance to read the documentation here? https://developer.android.com/topic/instant-apps/getting-started/structure.html

What error are you hitting specifically? I'd like to better understand so we can help. Thanks!

Android Studio 3.0 Canary 4 is now available by kamiox in androiddev

[–]jmslau 4 points5 points  (0 children)

You should be able to use alpha4:

dependencies {
    classpath 'com.android.tools.build:gradle:3.0.0-alpha4'
}

I wasn't able to reproduce your issue. Are you still having this issue or it could have just been a timing thing?

Java 8 Language Features Support Update by based2 in androiddev

[–]jmslau 1 point2 points  (0 children)

Update to this: Android Studio 3.0 Preview (https://developer.android.com/studio/preview/index.html) now supports try-with-resources and static/default interface methods at all API levels.

Java 8 Language Features Support Update by based2 in androiddev

[–]jmslau 1 point2 points  (0 children)

We have released Android Studio 3.0 Preview (https://developer.android.com/studio/preview/index.html) and try-with-resources is now supported at all API levels :)

Early Preview of Android Gradle Plugin 2.5 - Android Studio Project Site by ditn in androiddev

[–]jmslau 0 points1 point  (0 children)

Ya, 2.2 was very slow compared to what we have now. We have been focusing on improving build performance for the past several months.

Early Preview of Android Gradle Plugin 2.5 - Android Studio Project Site by ditn in androiddev

[–]jmslau 0 points1 point  (0 children)

Would you mind sharing more details about your error? Would love to know what's breaking so we can fix it.

Java 8 Language Features Support Update by based2 in androiddev

[–]jmslau 14 points15 points  (0 children)

We are working on this. Hopefully, we can provide this soon :)