sevenadrian

A few reasons, but one of the primary ones is there needed to be a way to securely store the session or identity of the user on the client side. There are a few ways of doing this on the client; storing it in memory, using browser web storage, etc. But the most secure way (for users using a browser) is storing the data securely in a HTTP only cookie, and it's this aspect of the responsibilities that this library looks to handle.

hmm, yes, I guess at some level user data is stored in a database somewhere.

What is trying to be communicated here is you don't need to connect to a database at all. You can use an API, something in memory, etc. The library doesn't have to connect to a DB.

For example, I use Hasura a lot (a GraphQL wrapper around postgres), and this library works perfect with that, since blueauth can just do API calls.

But yes, even in that scenario it is Hasura that is communicating with a database but not blueauth.

Basically blueauth can interface with anything you can write in javascript (any type of DB, interface, etc)

Also if you'd like a bunch of free credit to try out, just let me know the first part of your user id (in /account)

Hey all, just posted this! It's still very much a work in progress but wanted to share regardless. So far I think it's an improvement in a few ways over existing APIs / Platforms out there at the moment that have similar offerings (clearbit, fullcontact, etc.).

Let me know what you think and how it can be better for you!

Thanks man!

HelloList can definitely do that (need to make that more obvious), mainly because it's just a simple platform. People sign up and promote it and such, and on the backend you get an ordered list of all the entries including info like who referred them, number of referrals, when they signed up, ordered by their rank (can dl it as a CSV too). Whether you let just the top 100 in your beta for free, give everyone who referred >3 people something, give the top 500 people a "badge", or etc., is entirely up to those building the list.

weird, was this on the example on hellolist.com, or on a list you had somewhere?

Yup, there's actually an example right on the home page right under the hero. Enter an email to sign up for "PicExample"

awesome catch, thanks man!

I was building the MVP for another product, but after seeing tons of other pre-launch startups starting to gamify their waitlist (by letting users move up the list by referring others to sign up) I decided I want to take advantage of that too so I started building that out.

Then I thought, "hell, why don't I try to actually turn this into something?"

Three-ish weeks later, HelloList.com was born.

Take a peek! Going to try to make this something that nearly anyone can use to build a waiting list, so would love to hear any feedback on how to make it more useful.

false, comments are always terrible, including this one.

thank you! was just looking for a quick example and was surprised to not see it immediately/obviously linked.

yeah, agreed. Sometimes it's best to not make it work and to move on, no matter the reason that makes you leave.

yeah, nuts. I wonder how many generations down she has met.

agreed, definitely why it's one of my favorite disciplines (you can consider science a discipline right?).

I always admire pursuits that strive to be objective, and science is definitely an embodiment of that.

yeah, definitely not a trivial amount.

Yeah, agreed, this was the point that stood out to me the most. Privacy, battery usage, interference, simply not obeying instructions, etc..

yes, please, so my free time is not long for this world

I don't think this is evidence of a tech bubble at large, but it is evidence that tacking on monetization onto a mass-popular app/service/site isn't always a slam dunk

Ha, I knew I recognized it. Thanks for proving I'm not crazy, at least because of this.

ha, thanks! I knew I was lucky with a useful 6 letter domain. If you have any ideas that you had wanted to implement but don't see please let me know!

and thanks for the domain brandon!

hard to say if it is more or less useful, but hopefully easier (and therefor more useful).

this hopes to centralize the search for good repos, instead of having to turn to a generalized search engine, and ideally add some functionality that facilitates the search (search/sort by created date, updated date, popularity, find similar repos, etc.).

like a personal tag cloud that applies just to the tags of that users starred repos? actually that's not a bad idea

awesome, thanks wise young man, this is exactly one of the problems I personally experienced that I was hoping to solve.

I am also interested in how this plays out. Maybe this project will succeed, or maybe something else better solves the problem. Either way I think it will be awesome.

There is so much out there, it can sometimes be hard to make sense of it or manage it in a way that suites someone the best. This is just my stab at trying to solve the problem.

If you have any other input on how to make it more useful please just let me know! Thanks again!

Hmm, never thought of that, excellent idea mamcx!

I'll start scoping that out and see what a solution would look like, seems like it would helpful for a lot of projects.

Thanks for the idea mamcx!

you can add tags, instead of just searching based on language (and description). Hopefully as things begin the flesh out, you will be able to more easily find other similar repos and repos of interest (through the "similar repos by tags" and "similar repos by stars"/"users who star this repo all star these other repos" functionality).

Very soon, besides being able to sort by popularity/star count, you will be able to sort (and search) by created date, updated date, and forks.

Also, there have been some requests to make this more service agnostic outside of just github.

So those are some points that hopefully make it more useful than github's current search functionality.

creator here!

tl;dr: yes, it is a little aspirational as of now, but will change.

The first search you can do, since I equate "star count" to popularity, and by default all results are sorted by star count/popularity.

The second search will be entirely implemented soon. You can find repos similar to other repos according to their tags, but can't sort by created or updated date yet. The information is there in the data, I just need to finish that functionality in the search and sorting.

I wanted to try to get something out the door before I finished every feature to see what people would use and what requests/issues people would have, and prioritize accordingly. Otherwise I know I would spend weeks fleshing out every feature I thought I wanted, including many that most would find useless =(.

In retrospect, you are correct in that it is a little misleading since you assume you can do that yet. It will hopefully be corrected shortly (busy trying to keep things running smoothly!).

Thanks for the input troutwine! I'll finish this functionality hopefully this week (if not sooner).

thanks for the interest everyone! This is my project that I just launched, thought I'd say hello!

I'll start answering questions as quickly as I can, it's the only thanks I can offer now for everyone melting my servers!

Very quickly some technical specs (going to write a post on this in more depth soon):

It's a ruby on rails application hosted on heroku. Unit testing with rspec, webmock, vcr, machinist, and capybara. Authentication is with devise obviously, with omniauth-github, and cancan and rolfy for authorization. Unicorn since it's awesome, and asynchronous jobs are taken care of by sidekiq. fragment caching is done with dalli/memcached. database is postgres, redis, and memcached, with monitoring by newrelic and logging by loggly and papertrail. Let me know if you have any questions!

I think this is the comment I agree with the most so far.

I believe TDD is important, especially for a MVP one could argue. Do MVPs change a lot? Yes, obviously because you are learning and adapting to the needs of you customers. This is where have good test coverage (thanks to TDD) is a big asset. You can refactor, change, pivot, all you want, without the worry that removing this feature, tweaking that feature, or adding this other feature, won't break something else.

And manual testing is way more expensive then investing in automated testing.

In my opinion, unless it is a very short lived project that you don't plan to iterate on and isn't very important, you should have good test coverage. And good test coverage is best achieved with TDD.

This is of course just my 2 coins

I believe by MVP he means "minimum viable product" http://en.wikipedia.org/wiki/Minimum_viable_product