About: 🥑 Developer relations engineer at DataStax | 🎤 speaker | 📝 writer | 🌭 sausage dog owner | he/him
Location:
Melbourne, Australia
Joined:
Jan 4, 2017
An exclusive content Web Component for the Web Monetization API
Publish Date: May 24 '20
40 7
Last week I started work on a series of web components that will make working with the Web Monetization API easier for developers and site owners. The first component to be released was the <wm-ad-hider> which hides ads once payment via Web Monetization is detected.
Today I released the first version of my second component: <wm-exclusive-content>. This is a component that you wrap around content that you want to hold back until you are receiving payment via the web monetization API.
And then wrapping your exclusive content in the element and a <template> element:
<wm-exclusive-content><template><!-- Your exclusive content goes here --></template></wm-exclusive-content>
When Web Monetization is detected and payments are being sent, your exclusive content will appear.
You can use this component to display anything from that paid-for content that you want for premium users to a thank you for supporting your site and your work.
Check out the code
You can see the code for both the <wm-exclusive-content> and <wm-ad-hider> components on GitHub here:
The Web Monetization site includes a more complete example of this idea. This web component will work towards supporting the features displayed in the example, including an optional call to action, and a loading message while waiting for payments to start streaming.
This is also just the second of a potential suite of components. If you have ideas for other components, please raise an issue on the repo or drop a comment here.
I'm completely new to this, so please forgive the noob question.
It looks like the monetized content is sent in the initial request, but it just remains hidden until the browser sends payment. I suppose that could work in some cases, but how would you go about sending the monetized content only after verification? Is there a mechanism to send some kind of token to the server for server side checks?
Super cool! I've done a similar project for my entry - it's a web component for revenue sharing!
Would it be okay if I also linked to your repo in my repo's README to direct people to other Web Monetization components (my repo only includes rev-share)?
I'm completely new to this, so please forgive the noob question.
It looks like the monetized content is sent in the initial request, but it just remains hidden until the browser sends payment. I suppose that could work in some cases, but how would you go about sending the monetized content only after verification? Is there a mechanism to send some kind of token to the server for server side checks?