#dev 2019-07-30

2019-07-30 UTC
#
GWG
jacky: Speaking of writing, I had a question for you re feeds
#
jacky
my bouncer's attached - shoot
#
GWG
You made some modifications to the /h-feed How to mark up section
#
GWG
Wondering what prompted it
#
GWG
Still thinking about feeds
#
jacky
yeah around pagination
#
jacky
I think there was discussion about how to do so with h-feed
#
GWG
jacky: Not many people seem to be doing pagination
#
jacky
how did you source that? pagination in this sense is something I've seen on almost any person with a blog
#
jacky
not necessarily with rel={next|prev} but some sort of back/forth
#
GWG
jacky: I just looked at people using h-feed and rel=next|prev
#
GWG
Not as many
#
GWG
Yes.
#
GWG
We are missing a lot of people, but I just analyzed those who posted they had an h-feed
#
Loqi
Shane Becker
#
jacky
that's off the first five from that list
#
jacky
but yeah that's odd
#
jacky
people really just post _whole_ feeds D:
#
jacky
kinda wish this 'Who Uses It' thing was automated
#
jacky
like given said constraints, tell me if I do it
#
[tantek]
sounds like a good feature request for Indiemap!
#
GWG
I spent a while there just looking at markup
KartikPrabhu joined the channel
#
jacky
aaronpk: does watchtower respect nofollow? I get requests to my sign in page from it
#
aaronpk
That's confusing
#
aaronpk
nofollow is a very different layer than http, and watchtower only really cares about http
#
aaronpk
my assumption is that someone subscribed to a URL on your site that is redirecting to your signin page
ichoquo0Aigh9ie joined the channel
#
aaronpk
Oh he left
ichoquo0Aigh9ie and KartikPrabhu joined the channel
#
jacky
but gotcha
#
jacky
interesting
#
jacky
I _think_ I know what that is
#
jacky
(my notifications feed from my site)
#
jacky
I thought I had a thing cleared out for it
KartikPrabhu, [prtksxna], [xavierroy], doubleloop, mblaney, [tonz], [Michael_Beckwit, cweiske and sonniesedge joined the channel; prtksxna left the channel
#
jamietanna[m]
Finally been making good progress on my Micropub endpoint! Got it committing straight to a GitLab repo via the api - need to do some more validation on request, and then hook in tokens, but then it'll be up woo!
KartikPrabhu, [fluffy], [xavierroy], Loqi and [jgmac1106] joined the channel
#
GWG
Rereading the webmention spec and pages on the wiki
#
Zegnat
Coming to any conclusions, GWG? Do you have a goal?
#
GWG
I mentioned it
#
GWG
I have been trying to work on the webmentions plugin but I keep getting sidelined
#
Zegnat
Any specific goal, something you do not like about the current plugin?
#
GWG
Right now, in WordPress, the mf2 processing is done outside of the webmention plugin in a separate plugin called Semantic Linkbacks
#
GWG
I am going to start merging
[frank] joined the channel
#
GWG
There is a merge plan that was discussed
#
GWG
The current code does a lot of things to keep the two pieces separate
#
GWG
But as I do that, looking for other related improvements
#
GWG
For example, per media rules
#
Zegnat
Ah, interesting. My own webmention endpoint actually doesn’t speak mf2 at all.
#
GWG
Oh?
#
GWG
How does it work ?
#
Zegnat
It follows the webmention spec, which doesn’t rely on mf2 at all ;)
#
GWG
So does ours
#
Loqi
[Zegnat] php-linkextractor: Class for finding all resources an HTML document links to.
#
GWG
But the feedback was having it as a separate plugin was confusing
#
GWG
I plan on using ideas from your link extractor
#
Zegnat
I guess it is a usecase thing. I do not currently extract content from pages that webmention me at all. Not in a separate process either.
#
GWG
One of the changes I want is to use DOMDocument instead of regex
#
Zegnat
Most I do (though I have temporarily stopped that at the moment) was feed pages that validated into a full web archiver that I ran. So I had a copy of the full page for future reading.
#
Zegnat
But I guess people who want Webmentions in WordPress will almost always want to combine that with extracting data from those pages. So then merging the processes makes sense
#
GWG
The code uses regex to verify links, then later parses using DOMDocument
#
GWG
I want to move the creation of the DOMDocument up further and pass it between functions
#
GWG
It has to be created for php-mf2 anyway
#
GWG
And php-mf2 supports being passed it rather than just a string
#
Zegnat
That sounds good. Not reparsing HTML to DOMDocument is definitely a win
#
Zegnat
Is there a reason you use a regex first? Performance?
#
GWG
Because the webmention code has used it from the beginning. Pre spec
#
GWG
And it is the mf2 code that used DOMDocument
#
GWG
So, this is me smoothing out the process to merge in the other code
#
GWG
Trying to figure out how to take pieces of the old code out one by one is hard
#
GWG
And there is a data migration piece I am worried about getting wrong
[prtksxna] joined the channel
#
[jgmac1106]
GWG seeing many other webmention platforms seperating the sending and receiving/displaying like you do
#
GWG
They will be separated but within the plugin
#
Zegnat
This is also not about the split between sending and receiving, but between receiving and parsing. I am not sure I have seen many platforms that split receiving and parsing
#
[jgmac1106]
ahh make sense
#
[jgmac1106]
just had another random idea, could social readers be away to think about webmention moderation?
#
[jgmac1106]
I already get notifications of webmentions (in my CMS and from webmention.io)...why not a button for "Display webmention"
#
Zegnat
Sure, you could subscribe to a feed of your own webmentions in your reader.
#
Zegnat
Still just notifications though. I am not sure it makes sense to add moderation tools inside a generic reader. But I am the wrong judge for that, I use an oldschool reader ;)
#
[jgmac1106]
yeah makes more sense in my CMS...just thinking about a "social reader" as a "classroom" for a bit and wanting to give folks control of when or when not to display
#
[jgmac1106]
when using WP it isn't a problem as askimet does the moderation
#
[jgmac1106]
for fall people will have to manually send and receive using telegraph and webmention.io...I bet most won't do that step
[eddie] joined the channel
#
[eddie]
I've thought about webmention moderation from within a reader
#
[eddie]
I came to the conclusion that the feed would need to be private and then I could display links in the "post content" at the bottom for moderation
#
[eddie]
that way the CMS is sending the actual links, and you are just clicking on links within your reader. It would work with both social readers and old school readers
#
[jgmac1106]
yeah eddie I was thinking about that I was copying and pasting a few webmentions
#
[jgmac1106]
oooh neat idea
#
[eddie]
I don't currently moderate my webmentions, but as I've thought about it, I think that's the first thing I'll do towards it
#
[eddie]
I think that's my primary plan. But the other thought I had was in terms of making all webmentions available through some Micropub Query
#
[eddie]
so then a Micropub client could query them and adjust their visibility and status attributes
#
[jgmac1106]
that is what I was wondering could be the "display webmention" action, its held in moderation until published with micropub to your site
#
[jgmac1106]
also want to add a button that would remove the webmention endpoint from any post so I can toggle them on and off
#
[eddie]
ohhh interesting. So while you were creating (or editing) a post, you could essentially "turn comments on or off"
#
[jgmac1106]
yeah just a small script to remove the endpoint, that would be an important feature if I used webmentions in school settings
#
[jgmac1106]
prevent dogpiling on a specific post by bad actors
#
Zegnat
Why would you stop advertising the endpoint rather than a/ blocking on receipt or b/ not displaying?
#
[jgmac1106]
I dunno just seemed like an easier...deleting one line...
#
Zegnat
I think some senders (IIRC, this includes bridgy) will cache webmention endpoints on a per domain basis. So you not advertising it on one post will not affect them, they will continue to send for that post as well as every other post
#
[jgmac1106]
ahhh that makes sense
#
Zegnat
Wow, sebsel, since when do you syndicate long form blog posts to Twitter threads?! I thought you had a bug when your latest post displayed 13 syndication links, but apparently not
[schmarty] joined the channel
#
[schmarty]
Zegnat: caching is only part of the spec insofar as respecting response cache directives. Also, removing the endpoint header prevents new senders from finding it.
#
[schmarty]
It would also reduce load on a webmention receiver to... not receive mentions 😁
#
Zegnat
[schmarty]: oh for sure. And caching-per-domain is probably actually a spec violation. I am just saying that it is how some senders work today.
#
Zegnat
So if you see the majority of your mentions come in from bridgy, just removing the header is not going to do much
#
Zegnat
I’d be in favour of both removing the header in addition to handling it on the backend.
#
[schmarty]
Multiple overlapping approaches
#
[schmarty]
multipleoverlappingapproaches++
#
Loqi
multipleoverlappingapproaches has 1 karma over the last year
#
Zegnat
Also: you probably already have some sort of logic to ignore webmentions that aren’t for your website in the backend. Extend that to also be able to silently drop URLs for specified articles on your domain and you are there
#
[schmarty]
I maintain that it's better not to receive an unwanted webmention than to have to handle bad ones
#
Zegnat
I agree on all points, [schmarty]. Just want to warn people that it may not be the actual way things are set up today :)
#
Zegnat
[Also insert note on how lucky we are we do not have spam problems yet here]
#
cweiske
note to self: build a tool to send spam webmentions to all irc-people
#
[eddie]
what is Chaos Monster?
#
Loqi
Chaos Monster is an opt-in IndieWeb project by Eddie Hinkle that aims to help IndieWeb resiliency similarly to how Chaos Monkey helps Netflix https://indieweb.org/Chaos_Monster
#
[eddie]
Chaos Monster << idea: for those that opt in? Send spam webmentions
#
Loqi
ok, I added "idea: for those that opt in? Send spam webmentions" to a new "See Also" section of /Chaos_Monster https://indieweb.org/wiki/index.php?diff=64034&oldid=63453
#
[eddie]
Chaos Monster << For those that don't opt-in but are obviously part of the IndieWeb, (like irc-people) consider sending a single spam webmention to prompt them to consider their webmention workflow, and then don't send any more unless they opt-in
#
Loqi
ok, I added "For those that don't opt-in but are obviously part of the IndieWeb, (like irc-people) consider sending a single spam webmention to prompt them to consider their webmention workflow, and then don't send any more unless they opt-in" to the "See Also" section of /Chaos_Monster https://indieweb.org/wiki/index.php?diff=64035&oldid=64034
[Jacob_Michelsen, [Rose], [davidmead], eli_oat, [tantek] and KartikPrabhu joined the channel
#
[tantek]
For those interested in IndieWeb issue tracking, starting by owning your own issues that you write!
#
[tantek]
What is an issue?
#
Loqi
issue is a special kind of article post that is a reply to typically some source code, though potentially anything at a source control repository https://indieweb.org/issue
#
[tantek]
And add yourself to the IndieWeb Examples there
[jgarber] joined the channel
#
[jgarber]
IndieAuth `scope` param question:
#
[jgarber]
```EXAMPLE 10
#
[jgarber]
The spec notes that `scope` is “a space-separated list of scopes the client is requesting.” The code example uses `+` as a separator:
#
[jgarber]
state=1234567890&
#
[jgarber]
scope=create+update+delete&
#
[jgarber]
response_type=code```
#
[jgarber]
“Space-separated” in URLs could be the plus sign or `%20`. What’s being used in the wild in this specific case of passing `scope` values to an IndieAuth server? I’m seeing the plus sign used more than `%20`, but should the server attempt to account for both? Or more possibilities?
[kimberlyhirsh] and [jgmac1106] joined the channel
j605 joined the channel
#
[jgmac1106]
[Jacob_Michelsen][tantek] I wonder if people are grabbing different themes and then editing them and losing some mf2. I just checked a few sites hosted on micro.blog and you get correct, some, and none with mf2
#
[jgmac1106]
or the main h-feed doesn't have h-entries unless you click on the link, seen that a few times as well. think folks are just grabbing Hugo themes
#
[tantek]
hmm looks like when I added alt text to my images I broke syndication to micro.blog — none of my photos are making it through: https://micro.blog/t
[KevinMarks] joined the channel
#
[jgmac1106]
Did I do this correct so feed readers will pull in my h-card from my homepage? https://gist.github.com/jgmac1106/ca384f0cbdad33efa5d9828c0850ced6
#
Loqi
Ok, I'll tell them that when I see them next
#
[tantek]
!tell [manton] when you have a moment, it seems we need to better document (or link to where it is documented) how to syndicate /photo posts to micro.blog. E.g. by adding alt text to all my photos it seems like I've completely broken syndicating my photos to micro.blog https://micro.blog/t 😞 — not your fault, I just need to know how to fix it, and I'll document that on /micro.blog too
jackjamieson joined the channel
#
[tantek]
Thanks to [gerwitz] for the heads-up BTW.
#
[tantek]
gerwitz++
#
Loqi
gerwitz has 1 karma over the last year
balupton[m]1, kitt, eli_oat, jjuran and jackjamieson joined the channel
#
[jgmac1106]
[tantek] [Jacob_Michelsen] FYI you are correct I tried two default themes in micro.blog and the mf2 is messed up
#
[jgmac1106]
for example the Arabica theme a post has the correct markup but the h-feed and the h-entries on the homepage are missing
#
[jgmac1106]
already pinged to find out where the repo is for the themes to see if I can fix
#
[tantek]
[jgmac1106] so that should be something we can fix in microblog and then hopefully add tests to make sure they don’t break again
#
[jgmac1106]
yes, I also suggested in the Slack we add a paragraph about mf2 in the theme customization tutorial, many people just grab off the shelf Hugo themes
#
jgmac1106
themes and plugins all the flexibility and all the maintenance….
#
[tantek]
Can you add a link to the IndieWebify.me h-entry validator too?
#
[tantek]
The key is making sure the code repo has continuous integration with tests that pass / fail so breaking changes can be backed out quickly and fixed
#
[tantek]
That significantly reduces the maintenance pain
#
[tantek]
paintenance?
#
Zegnat
!tell jgarber interesting issue with the plus sign. I am not sure those are considered spaces at all by the WHATWG URL spec that IndieAuth refers to. %20 may be mandatory. Open an issue for discussion?
#
Loqi
Ok, I'll tell them that when I see them next
gRegorLove joined the channel
#
Zegnat
Oh, interesting, does any Jekyll/Hugo (whatever microblog was based on) theme work, jgmac1106? I can totally see why people end up picking ones without mf2 then
#
[jgmac1106]
yes technically, but it seems most versions I am checking use the default themes you can choose, going through and testing those now
#
[jgmac1106]
will add what is missing to the wiki and then go back and fix them when I ever I figure out where the repo is
#
Zegnat
I don’t think [manton] made any of that publicly available? Or he may even be using the actual repos of thsoe default themes rather than his own forks? You’d have to ask him
#
jgmac1106
most of the default themes are just open sourced Hugo themes
#
Loqi
Custom templates, categories, new theme, and more
#
Zegnat
Aah, so looks like the themes are there, sknebel, nice
#
Zegnat
In that case PRs could definitely be done to add mf2
#
[schmarty]
"new", since it's been 6 months, but that describes the switch to Hugo, links to the github stuff that sknebel just linked, etc.
#
Zegnat
Good stuff. I have never used m.b so take anything I say with a grain of salt
[snarfed] joined the channel
#
[snarfed]
[tantek] may not have been your alt text that broke m.b images. mine stopped working too, sometime before june 13. eg this one should have an image: https://micro.blog/snarfed#post_div_4024479
#
Zegnat
[jgmac1106]: may be better to document missing mf2 for a theme in an issue on the theme’s repo where people in the m.b ecosystem can find it, rather than on the wiki
#
jgmac1106
yeah…I will do that once I figure out correct repo, really notes for me when I go back and try to fix
[jgarber] joined the channel
#
[jgarber]
Zegnat: Yeah, there’s the double-edged sword of “plus signs aren’t whitespace” and “well crap plus signs are used as whitespace characters in URLs across the Web”… 😭
#
Loqi
[jgarber]: Zegnat left you a message 15 minutes ago: interesting issue with the plus sign. I am not sure those are considered spaces at all by the WHATWG URL spec that IndieAuth refers to. %20 may be mandatory. Open an issue for discussion?
#
Zegnat
[jgmac1106]: check sknebel’s link. I think the repo names will match whatever names you are selecting within m.b
#
[jgarber]
FWIW, looks like several of [aaronpk]’s apps (Aperture, Monocle) use plus signs to pass around scope values (which would be in accordance to the example in the spec, at least…).
#
[jgarber]
Not sure how anyone else is passing scope values around…
#
Zegnat
goes to check how he does it
#
[snarfed]
comma and plus are both common scope separators
#
[jgarber]
snarfed: Oh, goodness. Comma??? Where have you seen that in use?
#
Zegnat
space U+0020 is the official separator in OAuth, IIRC. Comma should not be used here.
#
[snarfed]
silos. can find examples if you need them.
#
sknebel
Zegnat: WHATWG URL spec doesn't say anything about query part of an URL afaik outside of "it's a string, here's a list of characters it can have, everything else must bei percent-encoded"
#
[jgarber]
…maybe I’ll split on every non-alpha character. 🙃
#
Loqi
zegnat has 38 karma in this channel over the last year (120 in all channels)
#
[snarfed]
eh indieauth is specific, i don't mean you should handle all of those separators for just indieauth
#
[jgmac1106]
thx sknebel
#
[jgmac1106]
skenbel++
#
Loqi
skenbel has 2 karma over the last year
#
Zegnat
sknebel: I think it can neither have + nor space, so both of those need to be percent encoded
#
[jgarber]
Current status is I’m splitting on `+` and the literal string `%20`.
#
Zegnat
I did a quick check and I am not seeing the WHATWG URL spec for `parsing` mention that plus signs need to be decoded in any way
#
sknebel
but it also doesn't say that you separate values by = and &, so that's clearly a separate layer?
#
[snarfed]
one comma scope example: disqus, https://disqus.com/api/docs/auth/
#
[jgarber]
snarfed: :thumbsup::skin-tone-2:
#
[jgarber]
For what it’s worth, from the OAuth 2.0 RFC…
#
[jgarber]
> The value of the scope parameter is expressed as a list of space-
#
[jgarber]
delimited, case-sensitive strings.
#
[jgarber]
Of course that’s only as good as what folks are implementing in the wild…
#
Zegnat
sknebel: darn, you are right and I am being dumb. The spec describes how to break out the query part of the URL, but not how this is deserialised into something other than a single string
#
Loqi
[Medium] medium-api-docs: Documentation for Medium's OAuth2 API
#
[snarfed]
i'll stop now
#
[jgarber]
🤦‍♂️
#
Zegnat
It is hard to read the OAuth spec when building an OAuth implementation, I guess ;)
#
[jgarber]
Updated: `/(?:\+|,|%20)+/`
#
Zegnat
Thanks for the extra wormhole [snarfed]!
#
[snarfed]
heh sorry
#
[jgarber]
Zegnat: I WOULDN’T KNOW ANYTHING ABOUT THAT PARTICULAR PAIN WHY DO YOU ASK
#
Zegnat
Don’t do that for IndieAuth, [jgarber]! , is definitely not allowed there
#
[jgarber]
Zegnat: So plus signs only then for IndieAuth things…?
#
Zegnat
I do wonder what URL spec we are supposed to use when the IndieAuth spec writes “adding the following parameters to the query component”. If that is not specified behaviour of the WHATWG URL spec
#
Zegnat
[jgmac1106]: either + or %20. We need to figure out which spec to refer to for encoding the query component -.-'
#
[jgarber]
Trouble is the spec says one thing in prose (“space-separated list”) then demonstrates a different thing (plus signs) in the example…
#
[jgmac1106]
fragmention discussion goes back and forth on this
#
[jgarber]
☝ That’s the recent conversation I was trying to remember!
#
Zegnat
No. The demonstration is *after* serialising into a URL. If the query component serialisation defines plus signs for spaces, the demonstrations in the spec are correct
#
Zegnat
The question is: where are we getting the serialisation algorithm from
#
Zegnat
If it is application/x-www-form-urlencoded from the WHATWG URL spec, then all + signs are specifically replaced with literal spaces (U+0020) as part of parsing: https://url.spec.whatwg.org/#urlencoded-parsing
#
Zegnat
And actually, it wouldn’t surprise me if that is the spec it is taking from. Because we often follow what browsers would do when submitting regular forms.
#
Zegnat
Hmm. Looks like that serialisation standard mandates + signs for spaces rather than %20, am I reading that right? https://url.spec.whatwg.org/#urlencoded-serializing
#
sknebel
seems so. but the parsing half is probably more important
#
Zegnat
[jgarber]: I’d do what the WHATWG spec does there for URL parsing. Take the entire query string, replace all + with literal spaces before percent-decoding, then use only literal spaces as scope separators.
#
Zegnat
But may still be worth a clarification from aaronpk. I need to check on my dinner now, but am happy to file an issue after :)
[fluffy] joined the channel
#
jgmac1106
in the states they have launched commercial free included with youtube music….they are upping the annoyance factor to drive conversion goals me thinks
NinjaTrappeur, [davidmead] and [Jacob_Michelsen joined the channel
#
[tantek]
^^^ [jgmac1106] wrong channel?
#
aaronpk
hello scrollback
#
aaronpk
at one point, the oauth 2.0 spec used commas as a scope separator, but that was back in like 2012. unfortunately a few high profile APIs implemented commas before the separate was changed to spaces, so you still see some of that in the wild
#
aaronpk
but technically OAuth 2 is very clear on space separated scopes
#
aaronpk
but then you have to URL encode them to use them in a query string, and URL encoding allows both + and %20 to represent spaces, so you see both
doodlemania[m] joined the channel
#
[tantek]
standards++
#
Loqi
standards has 1 karma over the last year
#
[jgarber]
When requesting a token in the IndieAuth flow, in the initial POST request, the spec mentions `grant_type=authorization_code` being passed along with the `code`, `client_id`, `redirect_uri`, and `me` params.
#
[jgarber]
Is that `grant_type` param required?
#
aaronpk
it's the only grant type we use in indieauth right now, so technically not needed, but that's required by OAuth 2.0 because there are other grant types
#
[jgarber]
Gotcha. Thought it might be an OAuth thing. So were it missing in the POST, that’d be a 400 error?
#
[jgarber]
Copy that. Thanks!
[Jeannie], [Rose], [jackjamieson] and [KevinMarks] joined the channel
#
[KevinMarks]
Should we have a "add mf2 to all Hugo themes" contest?
#
j605
I tried adding some for the theme I am using. It is still incomplete and in a limbo
#
j605
I have to get to it again later on
#
j605
thanks for making indiewebify. that made the process much easier
#
[KevinMarks]
I made the indie-Tufte one a while ago, and adapted one recently, though I changed it enough visually that it is a fork now. Worth adding to the Hugo themes collection?
#
j605
I don't know but it will great to have references to mf2 implementations
[jgmac1106] joined the channel
#
[jgmac1106]
think we put the author h-card in the post footer and many of the themes will be fixed, I will look at the templating tonight if I get a chance
ORAORAORAORAORA[, [Jeannie] and [Jacob_Michelsen joined the channel
#
GWG
Afternoon
#
jamietanna[m]
[KevinMarks] I'm saving some of my theme conversion PRs for hacktoberfest 😁
#
[tantek]
Yeah so this might apply to a few of us here (ht [gRegorLove]) https://twitter.com/iamdevloper/status/1156151468744818688
#
@iamdevloper
Therapist: And what do we do when we feel like this? Me: buy a domain name for the side project idea we've had for 15 seconds Therapist: No
(twitter.com/_/status/1156151468744818688)
mblaney, KartikPrabhu and [fluffy] joined the channel
#
[fluffy]
[tantek] I literally bought the domain “mermaid.science” on a whim yesterday so I don’t appreciate the callout
[snarfed] and strugee joined the channel
#
GWG
[snarfed]: Does Bridgy cache webmention endpoints?
#
[snarfed]
GWG: yes!
#
GWG
Are the details documented somewhere
#
GWG
We were discussing it re your request for reopening an issue
#
GWG
And would need to understand what the consequences might be
#
[snarfed]
it's per scheme + domain, 2h expiration
#
[snarfed]
technically violates the spec but bridgy is high enough volume that i'm ok with it
#
[snarfed]
my request for reopening an issue?
#
GWG
The. . don't have a webmention header on pages without webmentions
#
[snarfed]
some docs here, we special case home pages. https://github.com/snarfed/bridgy/issues/701
#
Loqi
[snarfed] #701 finer grained webmention endpoint caching
#
Loqi
[dshanske] #75 Remove webmention header if Pings closed
#
[snarfed]
eh, bridgy is the one doing the wrong thing (technically), so i would ignore it when you implement that request
#
GWG
Need to figure out if it would cause an issue for anyone
#
[snarfed]
plenty of other people advertise webmention on some pages but not all
#
GWG
I may just have a disable option
#
[snarfed]
and actually for doing this in the wp wm plugin, it also shouldn't _accept_ wms on those pages, so it doesn't matter if bridgy caches the endpoint, its attempts to send would still fail
#
GWG
It would already
#
[snarfed]
great, so bridgy's caching doesn't matter
#
GWG
I am doing minor bug fixes in webmentions now