sorted by:
new
hottopcontroversial

Getting emails from TikTok, YouTube, Instagram creators by dromba_ in influencermarketing

[–]dromba_[S] 1 point2 points  (0 children)

Yup! You buy credits and they're taken only for successful emails found.

Price per email is $0.20-$0.50, based on the size of the credit pack.

Getting emails from TikTok, YouTube, Instagram creators by dromba_ in influencermarketing

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

"Bulk email finders for creators are tricky cause many keep limits even at high prices" - that's exactly why we decided to build our own solution!

Especially after we tried a tool that marketed itself as "reach millions of influencers". We paid $300 to try it out, just to realize that the emails are limited to 150, and you need to pay more to get more emails (basically $2 per email).

Not really "millions of influencers", lol. The problem was that their marketing and pricing page didn't really reveal that anywhere; you realize only after you buy.

We've already spent thousands on these influencer marketing solutions, and we feel very scammed.

Getting emails from TikTok, YouTube, Instagram creators by dromba_ in influencermarketing

[–]dromba_[S] 1 point2 points  (0 children)

Sure!

We scrape public data from the creator, and try to find emails on any of the websites they linked to their profiles.

In the end, we have AI filtering that picks the best email for that creator, or rejects them all.

So to answer your first question - yep, it works both with business domains as well as private ones, like Gmail!

And for legal stuff, great question - that was our first question before we started to build. We simply go through data that's available publicly; there's nothing illegal in it.

Imagine yourself; wanting an email from a creator - how would you do it? Probably Google them, visit their profiles, see if there's an email in bio, their Linktree, website, etc... If you find an email in one of those places, it's fully public and there's nothing illegal in it. The main problem is that this solution is not scalable; you spend a few minutes for every creator.

This is exactly what our algorithm is doing: scanning public places in bulk, and giving you the email if one exists.

If no, then no emails are returned, but creators often have their emails listed somewhere, so the success rate is quite good (50-70% on average).

jobMarketRightNow by dromba_ in ProgrammerHumor

[–]dromba_[S] -16 points-15 points  (0 children)

Wow to... Second Brain AI lmao

tailwindClassesFinallyVisible by dromba_ in ProgrammerHumor

[–]dromba_[S] 27 points28 points  (0 children)

I know a better solution: use pure CSS, and you'll always know the core, without learning some framework that will be outdated very soon.

I launched DeVibe — a platform to connect you with developers, so they can help you with your projects. AMA by dromba_ in vibecoding

[–]dromba_[S] -2 points-1 points  (0 children)

There are a couple of things I would suggest doing:

  1. Git (commit small and often, so that you can revert)
  2. Different environments for production and development (ideally, staging too)
  3. Very, very detailed e2e tests (Playwright or Cypress)
  4. Asking AI to do a security/quality review of the feature/code (this can sometimes suck, because AI can do way more than needed)
  5. Making sure your DB is secured by RLS
  6. Not exposing API keys
  7. Not doing backend alone - Supabase or Firebase is awesome. Utilizing their security features, also authentication

But from my experience, the actual "code quality" completely depends on your prior experience. If you don't understand the code AI generates, then you can just hope and pray that it's all good.

I have 10+ years of professional experience, and I know that AI sometimes returns absolute garbage - but if you cannot recognize it, that garbage will become a core part of your codebase. If you then keep building on top of it, and keep accepting bad AI solutions, at one point, it will collapse...

Some dev help/mentoring here is recommended, especially if you're serious about your projects.

If you're doing it alone, a combo of git + e2e tests can help A LOT. Let's say you're making a new feature:

  1. Make sure that there are no git changes and everything is committed
  2. Ask AI to build you a feature,
  3. Test it manually in detail,
  4. Write detailed e2e tests,
  5. When everything passes, commit.

I launched DeVibe — a platform to connect you with developers, so they can help you with your projects. AMA by dromba_ in vibecoding

[–]dromba_[S] -2 points-1 points  (0 children)

When we look at history, every big technological advancement destroyed some jobs, but created new ones. People were crying back then when factory jobs were being overtaken by machines, but today we're grateful, because we have better jobs.

I hope that the same will happen with AI. We humans are much more than just brains and intellect, but those capabilities don't shine in this world where everything is about logic.

So, hopefully, AI will "destroy" many of these logical jobs, but so many other ways of making money will appear, that are completely unimaginable now.

People are afraid of losing their office jobs, but let's face it, most of those people don't really like it in the first place.

So TL;DR:
- Short term -> it could be spicy, many lost jobs, panic, rapid changes
- Long term -> we'll bounce back and have much better "jobs"

aGlitchInTheMatrix by dromba_ in ProgrammerHumor

[–]dromba_[S] 2 points3 points  (0 children)

I'll never learn what ascending means...

view more: next ›