CodyReichert
Depending on the nature of the service, you don't always want to block disposable emails. We built Identibyte to give us the flexibility to act on certain types of email addresses and provide a better experience depending on the type of user.
The case for and against disposable emails
I love disposable emails, and I think it's great people use them to try out a service. We want to help companies (and anyone running a site with a signup form really), manage these better.
A lot of times users signing up with disposable emails don't need the time and attention that other users do - they just want to try out the product with little interruption. We encourage that!
Identibyte aims to helps the companies manage these accounts better. By pointing out information like this, you can focus your resources on the users who WANT and NEED it - instead of spreading everything evenly.
We've implemented this in our products by deleting disposable accounts after a certain time of inactivity. This helps us, and doesn't block people who just want to try out a product! Users who like the product almost always change their email to a real one.
I'd love to hear if this is something you would do, as opposed to completely blocking these signups?
It says more about the individuals than it does about the company.
"Connecting the world!" is indeed the job of almost all employees at Facebook. You can have a large majority of the company focus on this one goal, and also know that the byproduct of that goal allows you to expand another part of a bigger goal: to make more money on ads.
A company in a capitalist economy must make money, of course. No one is arguing that and no one is saying that Facebook doesn't want - indeed must - make money.
It's like asking an Uber driver what is job is: "to transport people!". Of course, that much is obvious. If you ask someone in the "growth" department (or whatever) what their job is - the description will necessarily be much different.
Can We Measure Delusions?
Just put up a sample issue page (as best I can for now) and I'll find some way to post them automatically as they're sent.
Thanks again!
Thanks for the tip - I'm finalizing the first issue right now so I'll get it on the site asap as an example. Makes sense :)
iirc, you make all of the issues available online after the fact, right?
The first issue goes out tomorrow - would you mind giving me some thoughts on the landing page and description of the content?
Show HN: QA for the Web – a weekly newsletter for the latest in software testing
Measuring productivity as a technical founder
Why Pingdom wasn't enough for me today
7 HTTP methods every web developer should know and how to test them
Similarly, On Intelligence is an absolutely brilliant book on what 'intelligence' is, how it works, and how to define it.
2) Hooked. Although it's very formulaic, Hooked provides a lot of good ideas and approaches on building a product.
3) REWORK. If you're a fan of 37 Signals and/or DHH, this is a succinct and enjoyable read about their principles on building and running a business.
Currently I'm reading SmartCuts and The Everything Store - both of which are great so far.
Show HN: Test and monitor your API Gateway endpoints with Assertible
Show HN: Automated API Testing with Jenkins and Assertible
Show HN: Automated API testing with Jenkins
Do you or your team have a similar approach to deployment testing?
The code for the tutorial is on GitHub: https://github.com/assertible/ruby-example
Add Post-Deploy Smoke Tests to Any Codeship Pipeline
- CircleCI for CI build status
- Coveralls for unit test coverage
- Assertible for integration tests status
For example: http://i.imgur.com/ZrKUK3t.png
Any new ones I should check out?
Ask HN: Best GitHub commit status checks?
I'm curious to hear what status check integrations people are using on GitHub pull requests?