This is pretty cool, but it seems like it doesn't store data for multiple visits. Say I land via Google yesterday, come back today via HN, then sign up. I'd like to know all that.

Thanks. Do you mean track additional UTM codes etc. for each subsequent visit?

Is having the following data included in the object returned by purser.fetch() what you're after?

    "visits_before_conversion": 2,
    "subsequent_visits": [
      {
        "referrer": "news.ycombinator.com",
        "utm_source": "hn_post"
      }
    ]

I added this as an issue here https://github.com/bilbof/purser/issues/3

Just some observations I have, hope they help (I'm on mobile if that matters and I just subscribed today).

#1 - your connection rate seems horribly low. I'm guessing it's all on the originator's side. If so, that doesn't really give me confidence in the service nor in the opportunities in the newsletter.

#2 - your landing page could be way better IMO. There's very little text about what I am signing up for, and if I hadn't come with the blog or HN, I wouldn't have signed up.

First off, you should have 2 calls to action, one for devs (or people who want to sign up to the newsletter) and one for people with suggestions. I read the page and if I had an opportunity, all I can do is sign up to the newsletter, then wait for the next email.

There's very little info on what happens. I signed up, now what. It says you made money in your blog, how? I don't see anything about paying on the main page.

I could go on, but I think you get it. Talk more about the process. People coming from HN and ProductHunt probably get the idea, but organic visitors won't, and you probably can't sustain this model without some organic.

#3 - I signed up today, any chance I can get today's email?

Not trying to be a jerk, just trying to help you out.

These are all great points and I appreciate the feedback!

1. Yep its low percentage, and its a goal to improve this number.

2. You're right, could definitely be better. I made money by successfully connecting devs with the submitters. I left a "pay what you want" link in the email. I only ask people to pay in relation to the value that the conversation brings them.

3. If you want! Drop me a line - cory@oppsdaily.com

It'd be great if when you signed up you got the latest email.

This is pretty cool. Would also be neat if you could filter by date ... like what were the top JS books mentioned so far in 2017.

Good idea! Will try to make this filter as soon as possible. Thanks!

Are you hiring? :)

Can I ask what you ran into? I'm thinking about starting a side project with .Net Core for my API and React for my front end. I'm wondering if it's even worth it to use Core at this point or switch to Go or Node.

I personally hate node with all of my being, but Go is good stuff and Java has two very solid REST frameworks Jersey and Spring Boot. Depending on the project needs you could use DropWizard or Play which come with a really solid REST API framework builtin.

I was always partial to Pythons Flask as well

What did we run into? Tons of brokenness. Inability to use C# libs was the biggest problem, if you're trying to make anything significant you're going to have to roll your own everything. Java is the safest bet for large projects, I've never run into any issues finding a quality library to do anything. This is coming from a guy that's been a career C# dev for years and wishes he could defect to Java.

I have no clue if anyone really uses it, and it has a terribly un-googleable name, but the Java Spark Framework is the most beautifully simplistic REST API I have ever played with. It's the only time Java has ever felt like Node to me.