We have now developed an integration between Dreams and Discourse. A Discourse instance can be linked to an organization on Dreams. Projects that are posted on Dreams get their own Discourse thread, and comments on Dreams are stored as replies to that thread.
To connect to edgeryders.eu, we would need to accept that the API key of the system user is stored on the SenseStack servers. This will not be required later, but right now we are unlisting and listing topics which is an admin function. We will implement another solution within the next few months that will only require sending us an API key of a non-admin bot user that posts the topics.
We are just about to add ToS and GDPR agreements next week and start offering it as a service. It is free for now, but we will start paid plans later this year.
Hmm interesting! What’s the idea behind posting the same content on both platforms? Do you want to use the forum as an accessible entry point and point them towards using Dreams?
Is this integration two-way? Means, are comments posted to the Discourse thread also posted to the corresponding Dreams project?
What would you see us using it for? Proposing and evaluating application options, collaborations and other business opportunities?
Mostly the other way around actually. On Dreams, people are prompted to create project proposals where they answer a set of questions in a form, upload some pictures and set a budget.
However, many projects need to be discussed in-depth and the discussion needs to be referenced and quoted elsewhere. And if some things are discussed on Dreams, it becomes messy and fragmented.
This way, engagement could start with someone posting a proposal, which them leads them into a discussion with people on the forum, and eventually into other topics and conversations in the community.
Connecting Dreams to Discourse (integration with Loomio is also planned) is a way to make sure that those discussions end up with the rest of the conversations of the community.
Yes.
For example, when we run decentralized events like the Edgeryders Festival in 2019 or the OCI incubator. It becomes a structured entry point, and it becomes unambiguous for people if their proposals have been accepted and funded.
It really depends on the proficiency of the users, but most of these applications were made by new users without any prior experience of the platform without any hand-holding: https://dreams.blivande.com/gallery
Basically, submitting a project should not be much harder than filling out a google form.
Question - does the url on the dreams platform have a correspondence to the topic ID on discourse?
I’m working on project pages that automatically aggregate different types of content from a discourse category. If say a dreams topic exists in a specific category, it could be cool to display it with a direct link to the project on the dreams platform.
Yep, exactly what I was thinking. The way I’ve set up events and pages for example is simply by filtering topics by tag (‘event’/‘page’) in a category, so if this could be automated it would work really well.
As long as the topic on Discourse has a link to the project on Dreams (which seems to be the case here) it should only take a bit of regex to parse the URL and create a link to the right page. I’ve already done this with GitHub URLs in manuals - which you can see here.
