Introducing a new way to monetize your writing: via micropayments and the Web Monetization protocol 💰
Read the full story on @blog: https://write.as/blog/monetize-your-writing-with-micropayments
Enabling Web Monetization on your blog lets Coil.com members (and subscribers to any other Web Monetization provider in the future) automatically send you micropayments as they read.
See this in action as a Coil subscriber on blogs like Sim Show: https://sim.show
We still need to add support for exclusive content, but we're waiting to see if users need it. There's much more infrastructure needed for this feature in order to verify payments, including additional backend applications out of our control. But if users will find it useful, we'll include the feature and fully document everything.
Dino, would you consider changing your page to allow changing the hard coded Write.as address for the instance account?
I would love to create an index, it's my Tech blog's first annivesary this week, and I have many pages which were a pleasure to write and publish.
If you can do that, it would be greatly appreciated -- and I would put the word out in the Fediverse.
@rgx is my main account.
Main blog is : https://write.tedomum.net/rgx/
@rgx @write_as Hey guys, I've got the new app running at https://wf-archive.dinobansigan.com/. However, I'm running into issues when using it with a WriteFreely instance. It works fine when I pass in `Write.as` as the instance name, but won't work when I pass in `write.tedomum.net` as the instance name and `rgx` as the alias. It looks to be some kind of CORS issue, probaby a server setting?
I created a thread for the issue here:
Appreciate your effort, hope we can get it working. I tried with my two write.freely accounts, one being the tedomum.net one, and it did not work. Same with the second one.
It did produce the output with my write.as account, but that one only has a single post atm.
Thank you for working on this. Happy New Year!
@write_as I really wonder whether it's possible to do something like Flattr with this:
I really like that approach as it keeps content available in the open for everyone, but sets up an automated tipping jar where everyone with the Flattr extension throws in a fraction of their budget when interacting with the content.
WM as you describe it looks more close to the "maybe paywalls become less bad if we automate them? " approach.
@schmittlauch I think this is actually close already -- the paywall is totally optional. Just adding the "monetization" meta tag to a site means visitors automatically start "tipping" when they arrive, so you can keep content completely open if you want.
I do like the idea of explicitly tipping, though (whether through WM or another way). I think we need a combination of ways to pay. But I believe that part of the tech is still in development.
@sean Definitely! Already imagining what it would be like if you could add a payment pointer on your fedi profile, and then you could automatically stream payment to whoever you're interacting with. Seems like a great fit for the fediverse and social media in general.
And more importantly as an end user, would I end up needing multiple subscriptions to payment providers if my host (in this case write.as) doesn't support other providers?
Bit of a noob question. But valid ones I think :)
@sexybiggetje All good questions! Yes, Coil is a payment provider (the only one at the moment). But they're interchangeable behind the Web Monetization standard -- as long they work with WM and we support that standard as a platform, end users get the same experience.
From what I've read, I think the big differentiators between providers would be how much they charge / pay out and how they treat privacy. (For example, this discussion: https://discourse.wicg.io/t/proposal-web-monetization-a-new-revenue-model-for-the-web/3785/2)
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!