voxpelliI do think that something like JSON Feeds should have a generic link-property on both feed and item level though, to enable extensions like WebMention, payment etc to be easily and independently injected in there
miklbpfefferle those functions in semantic linkback are great, I use them for my facepiles, but colinwalker was trying to get replies that came in as webmentions but loose the the type as they are now standard comments along with other webmentions
[colinwalker]Just had a thought (I know, careful) - as webmention replies have comment_type removed can't we just use semantic_linkbacks_type to check if a reply and then rewrite the value to the table?
ben_thatmustbemesigh, its a little disturbing to see people worried about backcompat for a spec so early in its infancy. But thats what happens when you publish something and give it a version and make it look like you are expecting it to be implemented before anyone outside of the editors have had a chance to review it
[manton]voxpelli and aaronpk: The way I read Julien's comments was that WebSub's Discovery section in particular might need to be updated. Not sure if there was something else... But I think the "Publishers _must_ implement" could be relaxed a little to "_should_ implement", giving room for something like JSON Feed's "hubs" (or the proposed "links"). I plan to write up an issue for this.
[manton]aaronpk I totally get that. My first thought was "links" as well. But my view is that WebSub is critical to improving feed readers, and so kind of promoting it to a core part of the spec will give it more attention.
aaronpk[manton]: my only problem with "links" is that it's almost too generic of a term. that's why "rels" is nice because it's specifically just the links with a rel attribute. otherwise it could be misinterpreted that you're supposed to put *all* links in that array
[manton]It's really a trade-off with how generic something should be. There are many fields that could be abstracted to more of a type/value format, to be more flexible, but then you make the document more verbose. I don't think it's always clear. (I'm sure many folks would want next_url to be moved to links/rels too.)
[cleverdevil]I mocked out JSONFeed on my site last night and struggled a little bit with mapping different types of posts. I ended up adding in an extension to each item that contains some extra metadata. https://cleverdevil.io/?_t=json
dougbeal|iOSI have a post from instagram via OYG and syndicated to Facebook. Facebook likes find the post fine, but the instagram ones say no webmention targets (via bridgy https://brid.gy/instagram/murderofcro.ws#)
tanteksharing this here from chat channel because I think the person that said it would be ok with me doing so (i.e. not written by me) -----> "A hands-on conference focused on making your own website and connecting it to social media - so you don't have to store everything you make on Facebook"
schmartyit was! a bunch of local baltimore podcasts brought together in a big 4 hour block of live shows. there's more tomorrow but the venue tonight was where my improv group plays and i volunteered my recording equipment.
schmartysounds like folks are already locking places down. i'd be up for sharing an AirBNB out along the rails to make things more private + affordable but I don't know the area enough to trust myself with the planning.
asuhThis section explains that as long as you've installed the IndieWeb plugin, you should be able to go to the Profile section and add your social profiles which will then show in new link elements in the header of the site. I'm not able to make this work.