"test" search results - search chat.indieweb.org

10333 results for "test"

edited /test (-5) "aha"
Loqi at 2024-02-29 21:26
edited /test (+8)
Loqi at 2024-02-29 21:25
edited /test (+241) "testing comments"
Loqi at 2024-02-29 21:25
capjamesg - location /test-plain { default_type text/plain; try_files $uri $uri/ $uri.txt =404; }
to2ds at 2024-02-28 19:33
capjamesg - location /test { if ($WANT_PLAIN_TEXT = 1) { rewrite ^/test/(.*)$ /test-plain/$1 last; } try_files $uri $uri/ $uri.html =404; }
to2ds at 2024-02-28 19:33
capjamesg - It uses separate subdirs under document root: /test for .html and /test-plain for .txt.
to2ds at 2024-02-28 19:33
capjamesg, that will be a good test of whether such blogs allow for per-post authors or not
[tantek] at 2024-02-28 18:32
[tantek]: I'm not sure I would qualify that as "major" flaws, but yes, it bothered me as well that the sites are clearly not identical, and I definitely agree with Mario that it would be great to have a standardised test site to actually measure this stuff against. I remember Zach Leat did something at least a little fairer comparing different framework build times etc. but I've not seen anything comparable around CSS strategies
[Murray] at 2024-02-28 18:19
ok, I added "^ problems with the Tailwind vs Semantic CSS comparison article: https://mariohamann.com/test-quality-vs-bashing-tailwindcss" to the "See Also" section of /Tailwind https://indieweb.org/wiki/index.php?diff=93509&oldid=93489
Loqi at 2024-02-28 18:11
Tailwind << ^ problems with the Tailwind vs Semantic CSS comparison article: https://mariohamann.com/test-quality-vs-bashing-tailwindcss
[tantek] at 2024-02-28 18:11

Sort by:

Relevance Date

Filter results by:

Tag

Query took 0s.

Search tips

Exclusion: +foo -bar
Logical OR: foo OR bar
Exact phrase: "foo bar"
Partial words: foo*
Particular fields only: title:foo; domain:example.org; nick:somebody; after:2016-11-23; before:2016-11-23; date:2016-11-23