Pimp your native HTML players

There are various cases where you would want to publish content from zim to the web. Typically you edit you content in zim, and than convert it to HTML to publish it when you feel you are done

desktop cms for static sites

3D DOM viewer, copy-paste this into your console to visualise the DOM topographically.

Yeah the rate-limit approach makes sense! I've been using Nginx's req-limit (http://nginx.org/en/docs/http/ngx_http_limit_req_module.html) and fail2ban to do so. Importantly it accounts for the "burstiness" of a lot of HTTP traffic and allows you to set thresholds yourself. Can recommend! So you built it in as part of the forum software @cblgh?

The ngx_http_limit_req_module module (0.7.21) is used to limit the request processing rate per a defined key, in particular, the processing rate of requests coming from a single IP address. The limitation is done using the “leaky bucket” method.

The script looks through the page for any images with the class "low", and if found, reveals a button on the page and attaches the image swapping function to it. The function swaps out the source, and doubles the width/height.

The half size low-res image does two things: it greatly reduces the file size, and shows the pixels better (when enlarged by CSS). By using "image-rendering: crisp-edges;" in the CSS, the enlarged pixels are kept sharp.

"A whole website as a single HTML file with CSS cleverness to show different things as you click around."

a 1998 page by the creators of Storyspace

<svg xmlns="http://w3.org/2000/svg" viewBox="0 0 100 100">
<text y=".9em" font-size="90"></text>
</svg>

All of GitHub's menus & dialogs work without JavaScript. The brilliant
@muanchiou
figured out that <details> elements could make popover menus work without JS

https://github.com/muan/details-on-details
https://github.com/github/details-menu-element
https://github.com/github/details-dialog-element