Won't, or can't?
Do you have a good article about how to set up a paywall or tip jar for small transactions, with a clear description of what percentage goes to middlemen and (mainly in the case of proof of work) how much externality cost it incurs?
I would like to be able to pay $cents or even $dollar for instant access to an article, but only if X% actually goes to the recipient (I don't know what X is, yet), and I would lead by example on my own content. (though most likely tip jar, not paywall)
So for context, we built a lightning paywall(now defunct). All you had to do was add a single line of js to your site, as easy as Google analytics/ads. The cost was 0.01% of transaction. You could even move to self hosting and not pay us. Finally, we even built an "auto payer" so users could approve a site and auto pay a few cents with limits. Anyways, our experience is content publishers said they wanted to monetize their content but when it came down to it, were extremely reluctant to add a paywall and would maybe think of adding tipping.
Anyways I think our solution was great but no product market fit. I was especially proud how private the whole thing was but users didn't seem to really value that
Both are similar in that they hold the HTTP connection open and have the benefit of being simply HTTP (the big plus here). SSE (at least to me) feels like it's more suitable for some use cases where updates/results could be streamed in.
A fitting use case might be where you're monitoring all job IDs on behalf of a given client. Then you could move the job monitoring loop to the server side and continuously yield results to the client.