Over the past few months, I had the pleasure of being part of an exciting experiment at Yahoo! called Sled.
Sled was a collaborative list making tool with a strong
focus on life events and collaboration between friends and family. Planning a
party, a house move, getting ready for a new baby, planning a trip, organizing
a junior soccer league, or preparing for a marathon, are some of the areas Sled
was focused on. We also found it really useful for building Sled itself,
keeping track of issues and assignments.
There is a lot we don’t know about how to make our daily
lives more productive and organized, and how to collaborate better. What we do
know is that the wide range of tools and services available to us are,
generally speaking, not very helpful. Everything is either too limited or too
complicated. Usually too complicated. We know what doesn't work, but figuring
out what does requires experimentation.
Sled was developed as a virtual startup at Yahoo!, using
open technologies and the freedom to experiment. As is often the case with
startups and experiments, we have been constantly evaluating the product and
its fit within our existing and future roadmap, and have made the decision to
discontinue the project (shutting down sled.com at the end of the week). But
our story doesn't end there.
We built Sled on an entirely open stack, using open
source tools (Node.js, MongoDB, Express, Socket.IO, Jade) and open standards
(JS, HTML5, OAuth 2.0). We have relied and benefit from a vibrant community of
amazing developers and we want to give something back. One weak area for the
community is the availability of fully-baked, showcase applications written in
Node.js.
Instead of following the typical industry path of
discontinued products, we have decided in the experimental spirit of Sled to
release the entire project under an open source license using a new name:
Postmile. This means anyone will be able to grab the code and run the entire
service, back and front, exactly as it was hosted on sled.com (including the
soon to be open sourced iPhone app we never got to release).
We hope you will find Postmile helpful, fun, and an
insightful resource for the kind of projects you can build with Node.js today.
Check it out at http://j.mp/postmile. You
can use Postmile as a back-end API server for building new list-based products
(to-do apps, simple project management tools, bug tracking), as a list making
tool for your friends or your company, or just as a useful example to grab code
from.
At Yahoo!, we are super excited about Node.js and it is
already part of our standard infrastructure in many areas. For us, Node.js is
not just a cool new toy to play around with but a strategic investment. We have
a growing internal Node.js community and at least a dozen Node.js opportunities
we would love to talk to you about. Some are:
Yahoo!’s Mobile and Presentation Services team is looking
for a principal software development engineer to work on adding core
functionality to Node.js. This is a great opportunity for someone with strong
kernel and sockets development experience to help take Node.js to the next
level as the backbone of Yahoo!’s hosted services infrastructure. http://j.mp/ocqsj3 or contact @olympum.
The User Intent and Experience group is looking for a
front-end engineer to join Yahoo!'s innovation track to work on Search Direct
and new products. You will work closely with user experience designers, product
managers, and other engineers in an agile, highly collaborative team, developing everything from proof of concept to
production systems, both client-side and server-side. http://j.mp/poLgwy or contact @Fabian_Frank.
The Communications Experiences team (think highly
scalable experiences used by 300+ million users around the globe) is looking
for an architect to lead the development of new unique communication
experiences across our entire product portfolio. If you have experience with
C++, Audio/Video streaming, REST based service APIs, and of course Node.js,
you'll fit right in. http://j.mp/qrGfSF
Check out Postmile at http://j.mp/postmile
and let us know what you think @postmile!
EHL
http://hueniverse.com / @hueniverse / @eranhammer
Aviso Legal: El contenido de este mensaje de correo electrónico, incluidos los ficheros adjuntos, es confidencial y está protegido por el artículo 18.3 de la Constitución Española, que garantiza el secreto de las comunicaciones. Si usted recibe este mensaje por error, por favor póngase en contacto con el remitente para informarle de este hecho, y no difunda su contenido ni haga copias.
Legal Notice: The information transmitted is intended only for the person to whom or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender by e-mail reply or by phone and delete all copies of the material.
Mentions Légales: Ce message et toutes les pièces jointes sont confidentiels ou même couverts par le secret professionnel et transmis à l'intention exclusive de leurs destinataires. Toute modification, édition, utilisation ou diffusion non autorisée est interdite. Si vous avez reçu ce Message par erreur, merci de nous en avertir immédiatement soit en répondant à ce courrier, soit par téléphone. RavelSoft décline toute responsabilité au titre de ce Message s'il a été altéré, déformé, falsifié ou encore édité ou diffusé sans autorisation.
--
Job Board: http://jobs.nodejs.org/
Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to nod...@googlegroups.com
To unsubscribe from this group, send email to
nodejs+un...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en
I'm planning to rewrite 301.tl which represents a fully working (prod server's latest uptime is around 3 months), basic (simple URL shortener), and open source application fully written in node.js but still full of bad practices as it was my pet project for learning ;-)
It's not clear if you intend to keep working on the project or not,
but if you decide to add other authentication methods, you should
check out EveryAuth:
https://github.com/bnoguchi/everyauth
I just spent a total of 30 seconds looking at the project and it isn't
clear what module dependencies it has. The package.json file lists no
dependencies. I saw *.jade files, so I'm assuming it is a dependency.
And you are using MongoDB, so there's probably some dependency for it.
Would it be possible to provide a dependency list?
Thanks again!
Tauren
> Doing password-based authentication is not trivial given the number of attacks you need to protect against. This was an important design decision.
>
> As for OpenID... should not take you long to find out how I feel about it (and my 4 years effort to see it die).
Winning friends and influencing people here as well Eran? ;)
I would agree with the password-based authN.
I think the OpenID support would be useful for picking up Google hosted accounts -- but OpenID 2.0 has failed as being a widely adopted ID standard.
-- Dick