whatupdave

That's super cool. I worked on Smyte and have wanted to replace the language with something very similar to what you're describing. I'd love to learn more about it.

Have to be careful here, this would send phone numbers into logs files and other potential downstream services which is a bit of a GDPR nightmare now.

I've always thought this too but I haven't come up with a better plot device

the article states that they'll be ~800 miles up, so about 8ms there and back

Here's a helpful video on the topic: https://www.youtube.com/watch?v=krbKkLPXwlQ

Someone should build something like this, based off startup domain names, cross-checked with availability.

I almost alway use Que [1] now. It uses postgres advisory locks instead of Redis so one less dependency to worry about. You probably only need Redis if you're running a tonne of jobs.

[1] https://github.com/chanks/que

All the source code and public data is still available. Some teams might still choose to run the software.

Third!

Perhaps https://paidapi.com/ might work for you?

The youtube stream is so much better

Here's an example: https://twitter.com/fredwilson/status/570336180849373185

It can be tough to stay motivated while working alone. If you're happy to share the success with other people you could build it with the help of the assembly.com community.

This is awesome. I want this for ruby.