LoqiIt looks like we don't have a page for "pot type" yet. Would you like to create it? (Or just say "pot type is ____", a sentence describing the term)
[jgmac1106]how could this work for a building block logo: <a class="u-in-reply-to" href="https://indiweb.org"><img class="u-photo" src="https://indieweb.org/images/thumb/3/3c/webmention-logo.svg/320px-webmention-logo.svg.png"></a>
[jgmac1106]yes but @chrisalrich and (I have no idea to mention you) Jacky what if the social reader as a micropub client published a following post everytime you added someone to your reader? If it was on the same database,like Aperture, though the polling sounds intense, could a site say hey "three people you followed read this"
[jgmac1106]would be nice but I don't know how that is possible unless all read post get syndicated to some kind of aggregator...but they out of single-tenant
tantek__such a simple change but such a nice feeling to know I have ~10min to edit (retract!) a blog post before it goes to the Atom feed to all the old-school feed readers that cache aggressively
[jgmac1106][chrisaldrich] back to your read post I think this is where a group property in an h-card could work as semi-public way. Could a reader then parse something like you NYT example with 1,000s of webmentions and only display those who were also in your specified group for the query?
[jgmac1106]step one in the badgemaker is stripping away all namespace IDs and stuff packed into the 1.0 badging spec without touching the badge making parts, then rewriting the functions for the HTML....I really think we are going to be able to take the tools that are required for this massive badging spec and reduce it them to 55 lines of html and a tinybit of javascript
Loqi[chrisaldrich]: jgmac1106 left you a message on 2018-09-02 at 1:34pm UTC: I am not sure if it happens to you as well but on this page: https://boffosocko.com/about/following/ it never totally loads because of a data transfer to ma.tt
j12t, ben_thatmustbeme, cweiske, jjuran and [kevinmarks] joined the channel
[jgmac1106]@zegnat when you are free would love a second eye on how I am thinking about marking up my badges: https://github.com/jgmac1106/webmention-badges eventually want p-criteria and p-evidence but will wait until I have a teacher dashboard to consume this
[jgmac1106]thx, once I get those somewhere close I need to start on the javascript functions in the badge builder......just need to go through code with a chainsaw first to strip away Open Badges stuff
[jgmac1106]I tried to capture the thinking on the indiemon gam use case but around the more common use case of a conference attendance badge with a check in badge but still think it would be a reply post type sent to the checkin or rsvp rather than anything new.
@benlkeith↩️ Hey Greg! Webmention functionality would be better implemented as a WordPress plugin that integrates with the site's comment provider, whether that's WP's native comments, Coral Project Talk, Disqus, Facebook, Jetpack comments, or something else. (twitter.com/_/status/1047886931357589504)
@benlkeith↩️ Every single concern that applies to trackback spam and pingback spam also applies to webmentions, so sites will need to moderate webmentions. And thus, like comments, whether or not to accept webmentions becomes an editorial decision at the per-site and per-post level. (twitter.com/_/status/1047887832457666560)
[jgmac1106]not sure who the fediverse advocates and dev folks are in the community but Stefan Bohacek is trying to build fediverse bots that play with #indieweb sites
ZegnatI probably do not have a lot to say about fediverse bots, other people will know more about that. He can always come here and get the best of the hyve mind
LoqiIt looks like we don't have a page for "exact text of the error message" yet. Would you like to create it? (Or just say "exact text of the error message is ____", a sentence describing the term)
aaronpk"This allows clients which are not able to keep information confidential (such as an API token), to still authenticate with the API using a client_id and client_secret"
[manton]As I said in the other channel I haven't been following closely, but my understanding is that this API has not changed at all in at least a couple of years. When asked to support any kind of posting API standard, the lead developers haven't shown much interest. My guess is that it was an incomplete first attempt and has not been touched much since.
[manton]I've discussed this with Daniel Jalkut before too, because he's heard from MarsEdit customers that it would be nice if Ghost was supported. If Ghost has a completely new API, of course that's a bunch of extra work to support.
aaronpkwell considering ghost is about to change their API, but Micropub has been around for years, it seems reasonable that MarsEdit could add Micropub support, and then leverage that to get Ghost to support Micropub because that’s what MarsEdit uses
aaronpki’ve also been around Micropub/IndieAuth/OAuth for so long that I kind of forgot how horrible things can get when you start making things up yourself
aaronpklike really, the whole industry has been working on oauth for 10+ years to prevent the exact problems ghost is about to create for themselves with their new API