Adrien Joly

🎉 TADAAA: [L'avenir d'Openwhyd](https://medium.com/openwhyd/lavenir-d-openwhyd-818b0f34196c) (🇫🇷) ...and it's 🇬🇧 translation: [The Future of Openwhyd](https://medium.com/openwhyd/the-future-of-openwhyd-9a39e0839ac3)

@SkinyMonkey Please tell us more about your ideas on how Openwhyd (or DIggaz) could fund itself!

Also interested in your constructive feedback on proposed architecture changes:  (FYI, I'm considering to integrate these charts into the article) Source document: [Openwhyd v1.0...

Thanks for your reply, @SkinyMonkey! First, about architecture: - `openwhyd-web` is just of a part of the current implementation: it handles identification and sessions thanks to cookies (on which the...

After discussion with Pia from Open Collective, there are two other alternatives (or rather *complements*) that could be considered in order to pay the bills: - She can connect us...

This is a high-level vision of the strategic projects (and other tasks that require effort from contributors/volunteers) I foresee for Openwhyd, as presented yesterday evening:  Happy to read your...

Also, I would like to add 2 additional ideas on how to incentivise donations/sponsoring: - We could generate a **static version** of Openwhyd and host it for free on github...

Ongoing discussion about how to integrate external auth (e.g. OAuth) to Openwhyd's back-end: https://github.com/openwhyd/openwhyd-react/issues/5 => your opinion and help is welcome there!

In [that discussion](https://github.com/openwhyd/openwhyd/issues/109#issuecomment-341991285), I clarify the reasons why I'd like to encourage the development of new front-end/clients rather than new back-ends (or integrated stacks like Meteor).

Hey @smallcapyo, can you share the name of the playlist that you're failing to search for + the URL of your Openwhyd profile, please, so we can reproduce and fix?