Group items matching

in title, tags, annotations or url

¡Por fin terminó la espera para determinar quiénes ganarán los premios del público de los BOBs 2010! Ya tenemos nominados y ahora es el turno de los internautas de todo el mundo para votar por sus favoritos en las 17 categorías. De entre las cerca de 8.300 propuestas realizadas en la primera fase, el jurado compuesto por conocidos bloggers  de todo el mundo nominó a once candidatos por categoría: seis categorías principales (Mejor Weblog, Mejor Podcast, Mejor Videoblog, Premio Blogwurst,  Premio Reporteros sin Fronteras y Categoría Especial Cambio Climático) y once categorías destinadas al Mejor Weblog por Idioma (alemán, español, inglés, francés, ruso,  portugués, árabe, farsi, chino, indonesio y, por primera vez en los BOBs, bengalí). En total, 187 blogs, podcasts y videoblogs nominados a los que se podrá votar aquí hasta el 14 de abril de 2010.   Al día siguiente, el 15 de abril de 2010, se harán públicos los ganadores en el marco de una gran ceremonia. Esta vez con invitados de excepción. Por primera vez en su historia, los premiados se anunciarán en el marco de re:publica 2010, la conferencia de bloggers e Internet más grande de Alemania, en uno de los escenarios más importantes de Berlín: el Friedrichstadtpalast.

What do you think are the most important features a social network should have? How would you prioritize them? Do you plan to Build Less or go big? If building less, what is the minimal set of features you can get away with? We plan to “build less.” These are the features which we aim to complete first: 1. A good secure protocol, encrypted at every leg, including a specification for a lightweight, probably HTTPS, RESTful set of routes. We see all of this communication happening between two Diaspora servers, rather than strictly between peers. We realize there is the problem with polling with this model, but we think there are several tricks worth trying which all have their relative pros and cons: PubSub (fast and easy, requires some level of centralization), querying friends servers from the browser side and posting responses back (requires browser side decryption) to name a couple. Alternatively, we are considering going with XMPP altogether due to the ability to be able to push content between nodes, but we need to research it further to see if it is something we would want to implement. 2. A datastore and corresponding interface that can store all of your stuff in one place. MongoDB is what we are looking at for V1, but the redundancy of TahoeFS is intriguing(as well as serving a slightly different purpose). 3. A clear extension framework. Diaspora will be service-agnostic and we will need to make it easy to import from and export to any format/web service. It is also our goal to make Diaspora as content-agnostic as possible, by providing abstract data types and an easily extended UI so that whatever new content people want to store and share can be integrated without re-rewriting parts of the whole application stack. 4. Be your own OpenID provider. Having a single identity across lots of services is great, but why trust a web service to hold it? Once we are the keepers of our own data, we can also selectively allow services access to it through Oauth.

Pros and Cons Debated