webmonetization VS Servo

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.

Servo, the embeddable, independent, memory-safe, modular, parallel web rendering engine

> Is there any easy to use/hack HTML layouting engine where I could experiment with custom CSS attributes and bridge that gap? Would anything from Servo be suitable?

Servo could be used for this. You'd want to add support for parsing the CSS properties themselves to the style crate in https://github.com/servo/stylo and then the layout implementation to the layout2020 crate in https://github.com/servo/servo. You do effectively get a whole browser though.

I'm currently working on building a lighter weight / hackable layout engine based on a combination of https://github.com/servo/stylo (for css parsing and selector resolution), https://github.com/DioxusLabs/taffy (for box-level layout) and https://github.com/pop-os/cosmic-text (for flow/inline layout). I expect to have something decent in around 6 months

Neither of these setups currently have any support for pagination though.

Great to see some competition still alive in browser engine development. See also Servo (previously part of Mozilla) https://servo.org/ - that and Ladybird are still very underdeveloped compared to every day browsers.

It's a huge shame that there are no nightly builds of ladybird to try out but I assume that's because they just don't want the bug reports (if everything doesn't work it's pointless getting random bugs filed).

I haven't messed with it yet but from looking into it, this should absolutely work.

https://github.com/servo/servo/wiki/Building-on-ARM-desktop-...

don't know, there was a downtime in 2021 and 22 but since 2023, contributions look back to where it was before .. https://github.com/servo/servo/graphs/contributors

The world has moved on though to opinionated tools, and Rust isn't even the furthest in that direction (That would be Go). The equivalent of those two lines in Cargo.toml would be this example of a basic configuration from the jacoco-maven-plugin: https://www.jacoco.org/jacoco/trunk/doc/examples/build/pom.x... - That's 40 lines in the section to do the "defaults".

Yes, you could add a load of config for files to include/exclude from coverage and so on, but the idea that that's a norm is way more common in Java projects than other languages. Like here's some example Cargo.toml files from complicated Rust projects:

Servo: https://github.com/servo/servo/blob/main/Cargo.toml

rust-gdext: https://github.com/godot-rust/gdext/blob/master/godot-core/C...

ripgrep: https://github.com/BurntSushi/ripgrep/blob/master/Cargo.toml

socketio: https://github.com/1c3t3a/rust-socketio/blob/main/socketio/C...

1. Servo

It won't don't worry. There already are forks, for the worst case scenario. And Servo is on its way. Not yet ready, but it will be. Originally, from Mozilla kitchen.

To pain broad strokes, the layout phase (~= take the HTML, take the CSS, determine the position and size of boxes) is largely sequential in production browser engine today. Selector matching (~= what CSS applies to what element) is parallel in Firefox today, via the Stylo Rust crate originally developed in the research browser engine Servo. Servo can do parallel layout in some capacity (but doesn't implement everything), https://github.com/servo/servo/wiki/Servo-Layout-Engines-Rep... is an interesting and recent document on the matter.

Parallel layout is generally considered to be a complex engineering problem by domain experts.

https://hacks.mozilla.org/2017/08/inside-a-super-fast-css-en... is a really cool article that is related, that is a few years old but what it says is largely correct today.