webmonetization VS ts-odd

From https://webmonetization.org/ :

> Web Monetization provides an open, native, efficient, and automatic way to compensate creators, pay for content, and support crucial web infrastructure.

> Why Now?: Until recently, there hasn't been an open, neutral and cost-efficient protocol for transferring money. Interledger provides a simple, interoperable, and currency-agnostic method for the transfer of small amounts of money.

> Web Monetization is being proposed as a W3C standard at the Web Platform Incubator Community Group.

W3C Interledger Protocol works with any type of ledger.

From "Anatomy of an ACH transaction" (2023)

Coil tried to do that for a couple of years.

https://www.coil.com/

There's even a micro payments api in the works.

https://webmonetization.org/

W3C Web Monetization: https://webmonetization.org/ :

> The Web Monetization API allows websites to automatically and passively receive payments from Web Monetization-enabled visitors.

From https://interledger.org/faq/ :

> Web Monetization is being proposed as a W3C standard. Using the Interledger Protocol, the Web Monetization proposed standard aims to make it easier for web creators to generate income from their work without relying on advertising, site-by-site subscriptions or tracking models.

Interledger was contributed to W3C and has undergone significant major revision. FWIU, W3C Interledger Protocol is a W3C spec but by producing IETF-style numbered RFCs, their process differs slightyl from the W3C WG Working Group model (with a page, a mailing list; and one or more git Repositories with Issues: github,com/orgname, github,com/orgname/readme, github,com/orgname/orgname.github.io ).

It's been a couple years since Dev.to hosted the Grant for the Web hackathon, a month-long sprint to develop innovative projects with Web Monetization. Web Monetization is a proposed JavaScript API that allows browsers to create payment streams directly to websites, allowing for micropayments and unlocking exclusive content on a pay-per-use basis. It's still being incubated at the Web Incubator Community Group, but it's an active project and an exciting technology.

To support the open content creators there could be a sister site where authors can post or list the link to their openly-licensed content listed with donations or web monetization to give to Wiki. I put an offer on the Reward board in line with Safe Harbor#2_important_topics) paid-article policies. The upcoming grants of the 2030 Movement Strategy go toward sustainability, accessibility, and bridging content gaps. There are risks in introducing monetization. I see it as worthwhile to experiment with as there might be extensive potential benefits. What are your thoughts?

Web monetization - People can help creators by just reading their content.

To enable more developers to build open, transparent, and impactful payment systems for the world, opportunities for rapid prototyping and an enabling environment for rapid prototyping are key. That is why Coil will be a many Hackathons this year. In partnership with Major League Hacking (MLH), Coil will support developers to brainstorm and build payment solutions that connect existing and future rails so that no one is left behind, regardless of their location. Developers participating at 30+ MLH Weekend Hackathons will have an opportunity to build with Interledger, Rafiki, and Web Monetization. They will also get mentorship from developers at Coil, Interledger, and the broader Interledger, Web Monetization, and Grant for the Web communities.

Check https://webmonetization.org that's actually a perfectly fine solution. You like something and want to support people who work hard to make it? Why not pay them? Doesn't sound crazy to me.

Interesting!

Seems to have a fair bit of crossover with what the Fission team is doing. Yesterday I stumbled upon a web page re: a presentation[1] that a key Fission dev/founder (former Ethereum Core Dev) will be making in late September:

I ended up spending some time playing with Fission Drive[2] and looking at their Guide[3], and just generally reading their dev[4] and marketing materials[5].

Anyway, looking at the Web5 site, it seem to strike some of the same notes.

I'm not affiliated with or participating with Fission in any way, but am working as part of a team developing a decentralized storage protocol focused on durability.

[1] https://www.thestrangeloop.com/2022/a-distributed-file-syste...

[2] https://drive.fission.codes/

[3] https://guide.fission.codes/

[4] https://github.com/fission-suite

[5] https://fission.codes/

Currently, I work at fission.codes, and I have to say, it’s right up my alley. I wasn’t expecting to get the job. In fact, I didn’t really take the application seriously. But to my surprise, the CEO reached out to me to schedule a call, which I missed. I was really tired that day, so I slept off. I reached out to the CEO apologizing for missing the call, and trying to reschedule. Thankfully, he did. The interview went smoothly, and I got the job.

Note that the Filecoin network (which was designed to be the incentive layer for IPFS storage) has been operational for some time. If you look at the current status at https://file.app/ , you can see that storage costs there are extremely low for large amounts of data. f you can get your data verified as open, public data by applying for datacap with a Filecoin+ notary, it's currently free. See https://plus.fil.org/ (you can get 32GB of free datacap to play with just for having a github account).

If you want to use the Filecoin network as a "provider of last resort" for IPFS data, there's https://estuary.tech which will mark your data as verified, sort out the deals with storage providers, and then mirror it to IPFS.

There's also third-party tools like https://fission.codes/ , https://docs.textile.io/powergate/ , https://web3.storage/ and https://www.pinata.cloud/ for making this easier.

(Disclosure: I work at the Filecoin Foundation.)

There are several technical affordances to this at the moment. Local-first or edge apps enable the whole experience to take place in the security of one's own device and can continue offline without internet connection. Zero Data protocols like remoteStorage, Fission, and Solidobviate the need to create accounts (because people bring their own data storage) and also enable apps as swappable lenses—"software is the principles of an experience" (as Steve Jobs might have said) and your data becomes the details. Sharing content via URI fragment stores data in the link itself so that no 3rd-party server is necessary to hold the data (for example, a multi-platform music playlist).

You have to encrypt your own files. But there are solutions in the works! In the Filecoin Ecosystem check out https://fission.codes

Check out https://fission.codes they have a private drive

Or check out and the Webnative SDK that we've built all this into: https://github.com/fission-suite/webnative