Mews Profile is a working draft. The format, the stylesheet and this - site are all version 0.1, which is to say I am still changing my mind - about parts of it, and the spec admits as much in its first paragraph. - What a given version promises is written down at - mews.page/spec/0.1, and it stays - there once published.
- -Anyone can submit an address. The page is fetched and put through both - of the checks in section 9.1: it has to validate against the Mews DTD, and - it has to follow the handful of rules a DTD can't express, like keeping - your images on your own site and the markup under 256 KB (and preferably - under 64). Pass both and - your site is listed at once, by nobody's leave but the checker's.
- -Listed sites are looked at again every week, and one whose page stops - conforming is dropped; since I hold no contact details there is nobody to - warn beforehand, so submit the fixed page and it is listed again - immediately. A site the checker simply can't reach gets a few days of - retries before it goes, because being down over a weekend isn't the same - as being wrong.
- -The checks say nothing whatsoever about what a site publishes, and they - can't: a page about anything at all can be flawless XHTML. So if a listing - here points at something abusive, write to me and it comes out.
- -A submission stores the address you gave, the domain it belongs to, - what the checks found, and a salted hash of your IP address so that the - rate limits work. The salt is replaced every month, so last month's hashes - stop matching this month's, and raw addresses are never written down at - all.
- -Submissions and results are deleted after ninety days. No cookies, - nothing loaded from anywhere else, and no analytics, which given the - subject matter would have been embarrassing.
- -The format rests on XHTML Mobile Profile 1.2, which the - Open Mobile Alliance finished in - March 2008 and which is still perfectly good. The stylesheet asks first - for Atkinson - Hyperlegible, made free for anyone to use by the Braille - Institute of America, and then for - Source Code - Pro by Paul D. Hunt. Neither is loaded from anywhere: if you have - them you see them, and if you don't, Verdana is waiting.
- -Bug reports, arguments about the spec, and sites that ought to be - listed and aren't:
- hello@mews.page - -I would rather this stayed small: a format one person can implement in - a weekend, a directory you can read in a single sitting, and pages that - still open in 2046. If it grows much past that, something has gone - wrong.
-Mews - · Check a page - · The directory
- - diff --git a/site/check.html b/site/check.html index 00d39ba..d58cec7 100644 --- a/site/check.html +++ b/site/check.html @@ -11,10 +11,10 @@Paste an address below. The checker fetches that page, validates it - against the Mews DTD, reads your copy of - the stylesheet and up to twenty of your images, and then lists every rule - the page breaks together with the section of the spec that explains it.
+Paste an address. The checker validates the page against the + Mews DTD, reads your stylesheet and up to + twenty images, and lists every rule it breaks with the section of the spec + that explains it.
-Check page tells you what it found and keeps nothing. - Check and list does the same and then, if the page passes, - puts your site in the directory. - Either way it can take up to a minute, and there is no progress bar, - because a progress bar wants JavaScript and that is the one thing a Mews - page can't have. Leave this page open and go and put the kettle on.
+Check page reports and keeps nothing. + Check and list also puts your site in the + directory if the page passes. + Either way it takes up to a minute, with no progress bar, because that + would want JavaScript. Leave this page open and put the kettle on.
The same checks run on the command line, which is far less tedious - while you are still fixing things:
+The same checks run on the command line, which is quicker while you + are still fixing things:
uv run mewslint.py https://example.com/-
It reads local files too, so you can check a page before anyone else - sees it, and I run it on this site as well: the build refuses to produce - mews.page at all if one of its own pages stops conforming. That seemed - only fair.
+It reads local files too, so you can check a page before publishing + it. This site's own build refuses to produce mews.page if any of its pages + stops conforming. That seemed only fair.
One page per site, the one you hand me, and nobody reviews it: if the - page passes it goes in, and that is the whole of the trust model. A listed - site is checked again every week, and one whose page stops conforming - comes out of the directory without being asked twice.
- -Fix it, submit it again, and it is back in straight away. I keep no - address to warn you at, which is the trade (no account, no password to - forget, and no warning either).
+One page per site, the one you submit, and nobody reviews it: it + passes or it doesn't. Listed sites are rechecked every week, and there is + no address to warn you at. No account, no password to forget, and no + warning either.
If the checker turns your page down over something the spec doesn't - actually say, that is a bug in my validator rather than a fault in your - page, and I would like to hear about it.
- +A page turned down over something the spec doesn't say is a bug in the + validator, not a fault in your page. Report it to the address on the + home page.
+