DEV Community: Kendraio

Kendraio FundOSS

Antonio Talarico — Mon, 14 Jun 2021 09:53:12 +0000

Throw between two and five dollars to Kendraio today and we'll end up receiving up to an extra $20 in matched funding! FundOSS is a new system for fundraising open source software that rewards projects based on the size of their community rather than the amounts they raise.

So the multiples on the matched funding are bigger for the smaller the amount donated. Hence $2 gives the greatest multiplier! You need to have a GitHub account to donate. But that's easy to get.

Head to https://fundoss.org/collective/kendraio and donate a few dollars! And then tell your friends, family, and loved ones!

$500 USD developer bounty!

Antonio Talarico — Tue, 27 Apr 2021 13:22:32 +0000

Who? Fullstack JavaScript developer
When? Anytime from now
What? Integrating the open-source music information encyclopedia MusicBrainz within Kendraio Player, a proof-of-concept for a multi-service player for music streaming using web monetisation technology.

We want to give $500 to whoever can create an interface where you can look up as well as upload information to MusicBrainz via Kendraio Player in Kendraio App. We want users to be able to use Kendraio Player to display and also upload information to and from MusicBrainz.

Kendraio App is a general framework for creating low-code applications. Kendraio App was originally created to service the creative/music industry to enable easy asset and rights management both locally and on third-party platforms. But what we've ended up creating is a generic data browser that plugs into remote APIs and enables highly configurable low-code interfaces to be built. As part of our project for Grant for the Web, we developed Kendraio Player, an end-to-end reimagining of the interactions between streaming services, artists and consumers and how we can monetise music on the web to create the healthier, more open and fair internet that Grant for the Web strives to see built. MusicBrainz is an open-source, community-led music encyclopedia.

If all tasks have been completed after the mutually agreed-upon time frame, you will receive a $500 reward! This bounty is proposal-based, so have a look and submit your proposal here:

Kendraio App MusicBrainz integration (bounty) #184

dahacouk posted on Apr 27, 2021

Our second bounty is to integrate the open-source music encyclopedia MusicBrainz into Kendraio App. Kendraio App is our low-code 'data browser' application. Within Kendraio App we've built Kendraio Player, a proof-of-concept for a multi-service music streaming player using web monetisation technology, funded by Grant for the Web towards their mission to create a healthier internet.

We want this integration to enable Kendraio App users to search and browse, and also upload information to MusicBrainz. To participate, we would like talented full-stack JavaScript developers to propose how they would integrate MusicBrainz with Kendraio App.

Timeframe: 2 weeks
Bounty: $500 USD (paid out via https://opencollective.com/kendraio -- so you need to have an account here to be paid)

We're rewarding the individual (or group) that carries out this bounty in a transparent, interoperable, and easy to use way.

See how our first bounty went at Kendraio Player Audiotarky integration. And see Radhy's writeup of his experience at Afterthought on integrating Audiotarky API into Kendraio App.

Deliverables

A proposal written out before work starts and agreed upon beforehand in our Google Drive.
Interfaces created in Kendraio App using Flows where a user can:
- Look up information about a particular MusicBrainz entity ("give me info about The Beatles")
- Browse MusicBrainz to find entities connected to a particular entity ("show me all releases by The Beatles")
- Search for entities matching a specific query ("show me all artists matching the query 'Beatles'").
Interfaces created in Kendraio App using Flows where a user (artist) can:
- Upload information about a specific music release to MusicBrainz via Kendraio App.

Technical details and source code

Kendraio App: https://github.com/kendraio/kendraio-app
MusicBrainz development resources: https://musicbrainz.org/doc/Development
MusicBrainz API: https://musicbrainz.org/doc/MusicBrainz_API
MusicBrainz GitHub: https://github.com/Borewit/musicbrainz-api

Evaluation

The bounty will be evaluated by the Kendraio Team and advisors.
Evaluation will be based on the completion of the task, as well as on how transparent, interoperable and easy to use it is.
The more you can commit to documenting and talking about your experience with Kendraio App the more excited we will be to work with you.

Requirements

Candidates should have some existing experience with JavaScript and web APIs. Must be willing to document and talk about their experience of working on the tasks in this bounty.

Process

Once a candidate has put themselves forward, our Kendraio developers will mentor them exclusively for 2 weeks (or more, by mutual agreement). If after the agreed-upon period tasks remain open, another candidate may be given the opportunity instead.

About Kendraio

Kendraio App is a general framework for creating low-code applications. Kendraio App was originally created to service the creative/music industry to enable easy asset and rights management both locally and on third-party platforms. But what we've ended up creating is a generic data browser that plugs into remote APIs and enables highly configurable low-code interfaces to be built. And we'll use this framework as the basis of this project. Please check out these links before accepting this mission: Kendraio App demo, Kendraio App on GitHub, Kendraio App documentation, Kendraio App website. As you create this project your feedback will influence the direction and capabilities of the Kendraio framework.

The Kendraio App lets users build interfaces from blocks. The blocks themselves are plumbed together with modern JavaScript, TypeScript, and are configured using JSON. We have various backend APIs, and proxy endpoints hosted using Vercel's serverless platform.

</div>
<div class="gh-btn-container"><a class="gh-btn" href="https://github.com/kendraio/kendraio-app/issues/184">View on GitHub</a></div>

You can also find more specifications, evaluation criteria and documentation in it.

$500 USD developer bounty!

Antonio Talarico — Tue, 09 Mar 2021 13:40:29 +0000

Who? Fullstack Javascript developer

When? Anytime from now

What? Integrating fair streaming platform, Audiotarky, within Kendraio Player – a proof-of-concept media player interface for aggregating and streaming multiple services, incorporating web monetisation technology, built within Kendraio App.

Kendraio App is a general framework for creating low-code applications. Kendraio App was originally created to service the creative/music industry to enable easy asset and rights management both locally and on third-party platforms. But what we've ended up creating is a generic data browser that plugs into remote APIs and enables highly configurable low-code interfaces to be built. As part of our project for Grant for the Web, we developed Kendraio Player, an end-to-end reimagining of the interactions between streaming services, artists and consumers and how we can monetise music on the web to create the healthier, more open and fair internet that Grant for the Web strives to see built. Audiotarky are building a "new music streaming platform, that puts privacy and fairness in front of algorithms and shareholders".

We have an existing audio player that supports Web Monetization with Coil login - with or without a browser extension - but not yet with Audiotarky. Candidates should have some existing experience with Javascript and web API’s. Your task will be to enable a user to retrieve artist and track metadata from Audiotarky’s API using a Kendraio Flow. Bonus points for enabling an artist to import tracks to Audiotarky including payment pointers using Kendraio App.

Learn more and get in touch via our GitHub issue below.

Kendraio Player Audiotarky integration (bounty) #169

dahacouk posted on Mar 04, 2021

We're kicking off our first of four bounty programmes in collaboration with Simon Metson from Audiotarky. Audiotarky is one of our partners in our project, Kendraio Pay, funded by Grant for the Web. Grant for the Web is founded on the belief that a healthy internet needs openness and opportunity. It's a fund by Coil, Mozilla and Creative Commons, supporting an open, fair, and inclusive standard for monetising content on the web. In this bounty, we're exploring how rights management and payments operate when working with multiple DSPs.

The bounty

Timeframe: 2 weeks
Bounty: $500 USD

For this bounty, we're rewarding the individual (or group) that carries out the tasks below, in a way that is transparent, interoperable, and easy to use.

We have an existing audio player that supports Web Monetization with Coil login - with or without a browser extension - but not yet with Audiotarky. Candidates should have some existing experience with Javascript and web API's. Once a candidate has put themselves forward, our Kendraio developers can work with them exclusively for 2 weeks (or more by mutual agreement). After the agreed period if tasks remain, another candidate may be given the opportunity instead.

Tasks

Enabling a user to retrieve artist and track metadata from Audiotarky's API using a Kendraio Flow.
Enabling a user to play Audiotarky tracks within Kendraio Player, alongside existing DSP1 tracks.
Bonus points for enabling an artist to import tracks to Audiotarky including payment pointers using Kendraio App.

We will be very flexible with any hiccups that may occur and we will hold your hand all the way. We don't like stress here at Kendraio. We just want to see people enjoying building with Kendraio App.

Technical details

We have a technical blog post that provides background and demonstrates a simple Flow using the Kendraio Player block with the "Web Money" block. The more advanced Kendraio Player uses GraphQL to load a track list and artist payment pointers from DSP1.

Source code

Audiotarky API

Audiotarky data is available through a simple API. Currently this is not "discoverable"; you need to know the artist stub ID to find their work. There will be a genre API ~soon.

Discover artists API: https://www.audiotarky.com/$/artists/index.json
Discover albums API: https://www.audiotarky.com/$/albums/index.json
Artist details: https://www.audiotarky.com/$/artists/chris-foster/index.json
Album details: https://www.audiotarky.com/$/artists/chris-foster/hadelin/index.json
Track details: https://www.audiotarky.com/$/artists/chris-foster/hadelin/the-seeds-of-love/index.json

Evaluation

The bounty will be evaluated by the Kendraio Team and advisors.
Evaluation will be based on the completion of the task, as well as on how transparent, interoperable and easy to use it is.
The more you can commit to documenting and talking about your experience with Kendraio App the more excited we will be to work with you.

Kendraio Player

Kendraio Player is a media player incorporating Coil's implementation of Web Monetization and funded by Grant for the Web. The player was built in Kendraio App. Kendraio App is a low-code dashboard creator that helps build interfaces using Flows that connect to APIs with minimal code needed. The App has an audio player block (Kendraio Player) that supports Web Monetization, using either Coil's browser extension or login API -- but it is not yet integrated with the Audiotarky streaming service.

The Kendraio App let's users build interfaces from blocks. The blocks themselves are plumbed together with modern Javascript, Typescript, and are configured using JSON. We have various backend APIs, and proxy endpoints hosted using Vercel's serverless platform.

Requirements

Candidates should have some existing experience with Javascript and web APIs. Must be willing to document and talk about their experience of working on the tasks in this bounty.

Process

Once a candidate has put themselves forward, our Kendraio developers will mentor them exclusively for 2 weeks (or more, by mutual agreement). If after the agreed upon period tasks remain open, another candidate may be given the opportunity instead.

Please check out these links before accepting this mission:

As you create this project your feedback will influence the direction and capabilities of the Kendraio framework.

</div>
<div class="gh-btn-container"><a class="gh-btn" href="https://github.com/kendraio/kendraio-app/issues/169">View on GitHub</a></div>

Coil Web Monetization on mobile - no browser extension needed

Luke Stanley — Fri, 05 Mar 2021 14:52:29 +0000

This post explains how you can use Coil's OAuth login API to stream payments from Coil users without them having to use a browser extension. Coil has proposed and implemented a new standard to monetise content online without depending on advertising, called Web Monetization. The service is built on the Interledger Protocol. They are doing an amazing job at squaring a circle to make a better web for everyone. They have a service for Coil subscribers who pay to a personal balance, which is then distributed to content owners via Coil browser extensions, mobile apps and apps connecting to the Coil API.

If you want to see what you'll learn in this article, try out our implementation in the Kendraio Player and see our screencast.

Setting up OAuth and login process

Several steps are needed to set up OAuth. To get started, email Coil, fill in the web form on their site, make a one-off API request to get a key, and implement your own backend (to securely access Coil with a secret key) as well as your frontend to present a button and deal with various redirects as part of the OAuth authentication.

Thanks to funding from Grant for the Web, we were able to add Web Monetisation support to our low-code tool, Kendraio App, which enables users to make data-driven apps with custom workflows. Kendraio is a non-profit organisation and all our code is open-source, so you may benefit if you're implementing your own Coil login integration.

Maybe you have some content you want to monetise with Coil or maybe you have already monetised and want to provide users with access to content they've already paid for with Coil. Either way, if you're interested in making this content available and monetisable without your users needing to depend on a particular browser or browser extension, then you may find this technical guide useful.

Step 1 - Request access and provide resources

As outlined by Coil themselves on their docs, the first step is to make a Coil account.

After making an account, email the Coil developers with your use-case so they can approve your use of their API. Once approved, you'll need to register your app or website by providing them with a link to your logo, privacy policy, terms of service, and a list of URLs your users may be redirected to after logging in with Coil.

A word of warning: As there does not appear to be an easy way to change the list of URLs later, ensure you have a development URL or two set aside. This might be a staging URL and a localhost URL. Without this, testing the login flow could be a lot more clunky, so it's worth having a good think about what URLs you will need ahead of time.

Once you've sent the form, you should be emailed a registration access token that you can use once to get a secret key. This key is needed to connect your users to their Coil accounts and the Coil API for each subsequent login.

I used the Insomnia web client to make this POST request to their API at https://coil.com/oauth/reg and it returned a pretty printed JSON response containing the OAuth secret key and other info. Another option is to use a curl command directly or from Postman. Be careful to store the key securely, as you only get it once and it is used for potentially sensitive activity, such as moving money around and accessing user account info.

Step 2 - Create Backend API

Now that you have the key, it can be used by a login backend. The backend must use the key to verify you are who you say you are, to complete OAuth login attempts for your users.

We used Vercel, a serverless (think Lambda) platform, to make our backend API. Vercel has a way of securely storing environment variables that must be manually selected. Other backend solutions have different options for secrets managers.

After the user visits a Coil login URL and has been redirected back to your site with the OAuth access code parameter, your backend API will need an endpoint that accepts the OAuth access code and returns a Bilateral Transfer Protocol token.

This is done by using the users OAuth code, and the secret OAuth key to request an OAuth session token from Coil's API. Once you have it, the session token is used to request the BTP token, which finally is returned to the browser. This must be done in a backend to prevent exposure of the secret OAuth key from Coil.

You can see our backend API implementation here, and our frontend button that calls it is here.

Step 3 - Integrate frontend

A unique ID is needed for each OAuth session, and a UUID generator is a good way to create one. Our frontend does this and combines it together with other URL parameters to generate a login button link to Coil.

After the user clicks the link and approves your app's access to Coil, the user should be redirected back to the URL specified by you, with a token parameter. You'll need to send this token to your backend, and get a BTP token back for the user.

Step 4 - PROFIT!

Once we have a BTP token for a user, it's possible to start streaming payments using the Web Monetization protocol! Thankfully, Coil provides a script that can speak this protocol and stream money! Now that the user is finally authenticated and in possession of a BTP token, we can provide the Coil script with the token. The script, like the browser extension, checks the webpage for a payment pointer meta tag. With an active BTP token, as soon as the Coil script finds the meta tag, the payment stream should start.

Initial setup cheat sheet

Manually make a Coil account for the organisation
Email devs@coil.com with your use case
- E.g. OAuth login is needed to support users without the browser extension)
Fill out the OAuth registration form
- At https://coil.com/oauth_register provide Coil with your logo, privacy policy, TOS, what URIs Coil is allowed to redirect to (don't forget production, dev and localhost URLs!) Then wait for the REGISTRATION_ACCESS_TOKEN to be emailed to you
OAuth registration API
- Use the REGISTRATION_ACCESS_TOKEN to register with the OIDC provider to get your client_id and client_secret by manually make a POST request to https://coil.com/oauth/reg (with a lot of the same info as the prior registration step)

Login flow cheat sheet

We generate a random session ID
We assemble an OAuth login URL by adding a few parameters to https://coil.com/oauth/auth: client_id, session ID and a callback URL (e.g. hosted at localhost for testing, or your domain)
User presses a login button and visits the generated login URL
User returns at the callback URL, with an OAuth access code parameter from Coil (and session ID) added
POST the access code to our secure backend. Our own API then talks to Coil's API to:
- get an OAuth token from https://coil.com/oauth/token using the user's access code and our secret key (from our secrets store)
- use the OAuth token to get the Bilateral Transfer Protocol token for the user via https://api.coil.com/user/btp
- return the BTP token to the browser for the next step
A Coil Web Monetization client is run via a script and is provided with the BTP token
When a metatag with a payment pointer is detected, the payment stream can start (and works much like the Coil extension)

Kendraio Player block integration

Kendraio App, a low-code dashboard creator, helps build interfaces using Flows that connect to APIs with minimal code needed. We created a player workflow in the app and integrated a Coil login within Kendraio Player. We have a simplified player workflow example of how to use the audio player block and a "Web Money" block. It uses JSON data provided by a mapping block:

{
  "display_artist": "Patient Pacifist",
  "display_title": "Divided",
  "url": "https://dsp1-track-uploads.s3.amazonaws.com/auth0|5fa9852a2576900076396b60/b49cd51b-6f0a-4c7a-9c69-b83b753ee867",
  "paymentPointer": "$ilp.uphold.com/QhJqdGMmjZM4"
}

Then, below, we have a block that configures the audio player with JSON:

{
   "type": "player",
   "onPlay": [
       {
           "type": "web-money"
       }
   ],
   "onPause": [
       {
           "type": "web-money",
           "enabled": false
       }
   ]
}

See here for an introduction to Kendraio.

Don't forget to check out our latest bounty!

That's enough for now!

Kendraio App is a project by Kendraio, the interoperability advocacy initiative. Kendraio App is an open-source dashboard application currently focused on music/media creators, copyright and related rights owners. The app was developed to investigate how the transformative benefits of interoperability can improve existing processes — and to demonstrate how they can impact business, personal and public life.
Subscribe to the Kendraio newsletter here.