1123
results for "fail"
-
which makes it fail my verification _every_ time lol
jacky
at
2021-02-18 19:18
-
should I make that request fail?
jacky
at
2021-02-14 05:26
-
I kinda wanna just fail out altogether
jacky
at
2021-02-08 19:49
-
nightpool: one problem I have is that when working locally... when running in production, have to use a hosted service and sometimes requests to user actors will just fail
cwebber2`
at
2021-02-06 16:35
-
there is no "fail", there is only "not yet succeeding"
aaronpk
at
2021-02-03 02:29
-
like ideally the card validation wouldn’t fail because of a single “malformed” optional attribute, but also the attribute isn’t malformed.
[fluffy]
at
2021-02-02 18:50
-
seems weird that it would fail on the whole thing for a property that isn't usually used in the display of webmentions
aaronpk
at
2021-02-02 01:13
-
fluffy, that URL encoding seems fine to me. it shouldn't cause an HTML parser to fail
[tantek]
at
2021-02-02 01:11
-
Hmm, so, in my h-card I purposefully overly URL-encode my email address to e.g. “mailto:fluffy%20beesbuzz%2ebiz” because it’s an easy way to defeat noncompliant things like spam harvesters from getting my address, but allows worthwhile user-agents like web browsers to work right. But I’m noticing that having that causes my webmentions to fail validation on some endpoints, such as Barry Frost’s site. Does anyone have any opinions on be
[fluffy]
at
2021-02-02 01:08
-
[tantek] one way I think about those things is to try to drive toward a contradiction. Like "If I imagine that the instance admin is 100% responsible for blocking / unblocking, can I think of an unambiguous-ish situation where that would fail badly?"
[Raphael_Luckom]
at
2021-01-31 19:30
Sort by:
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