iasai, [jgmac1106], KartikPrabhu, ben_thatmust, snarfed and [tantek] joined the channel
#GWGDo proposed extensions to the micropub media endpoint go in the Github extensions repo, on the extensions page, on the media endpoint page?
#aaronpkuse github issues for discussions. as things get solidified we'll work them into the wiki page
#aaronpkif you want you can also add a short summary on the wiki and link out to github for the discussion
#[tantek]aaronpk I think that flow needs a bit better documentation / overview. GitHub issues -> Wiki page -> Spec
#[tantek]I think someone mentioned recently having to check three places as a Micropub developer
#aaronpktbh there should be enough documentation that a developer writing a micropub server or client should be reading the spec only as a last resort
#[tantek]whoa I'd almost see it as the opposite, that a micropub developer could read the spec, then work their way through test cases to implement, and not have to reference any side-docs beyond that
#aaronpkeh, I write HTML all the time and I've never read the HTML spec
#aaronpkonce you need to get into the nitty gritty then sure they can go read the spec
#[tantek]e.g. browser implementers *must* read the HTML spec very carefully to implement things interoperably
#aaronpkbut that shouldn't be the entry point. you should be able to write a functional basic implementation from other less spec-like documentation
#[tantek]ok I could accept that for a "getting started" tutorial for minimal basic functionality
#[tantek]ideally the spec *is* that minimal documentation required for interop
#[tantek]anyway the context of the discussion I referenced wasn't a *new* implementation, but rather getting details right for an existing implementation
#[tantek]I think there was some confusion about how "drafts" should work, as a feature, especially across a mix of mp clients and servers that don't all support it
#[tantek]I'm just the messenger in this example, not yet at the point of coding that with Micropub. I'll get there eventually now that I have https. 🙂
iasai, KartikPrabhu, snarfed, [jeremycherfas], gRegorLove__ and [eddie] joined the channel
#[eddie]I think that flow is good, GitHub Issues (discussion), Wiki (coalesce from the issues), Spec after wide enough adoption.
snarfed joined the channel
#[eddie]I think a benefit to that would be once there has been 1-2 instances of people building based on GitHub issues, it should definitely get a stub on the wiki
snarfed joined the channel
#[eddie]That would allow a situation like the one tantek is talking about (essentially someone like manton saying, I want to build a drafts feature, how do I do that?). In that case the person can check the wiki extensions page
snarfed joined the channel
#[eddie]Right now there is a Micropub brainstorm page, a Micropub extensions page, the GitHub issues and the spec. So having a page that you arrive at (Micropub extensions) that lists details for active extensions and stubs for prototype extensions would be great
snarfed, cweiske, KartikPrabhu, barpthewire and [Rose] joined the channel
#@voxpelli↩️ True, I myself wonder what I should do with my IndieWeb WebMention endpoint, https://webmention.herokuapp.com/ It’s great to be able to offer such capabilities as a service, but it opens one up to problems like this and it’s not really feasible to have everyone self-host everything (twitter.com/_/status/1110494524411953157)
#Zegnatvoxpelli: what part of the webmention receiver do you think will be affected by art 13?
#voxpelliZegnat: it’s especially article 11 that’s an issue when it comes to that I think
#voxpelliIn article 13 I guess it could be an issue if one hosts images or other content scraped from those sites - unsure whether that transfers the liability to the WebMention endpoint
#voxpelliBut as article 11 will make it very hard to show any link previews/scraped content at all
#ZegnatI wouldn’t say so, unless that is what the endpoint is actually doing. If you are just validating URLs, that is not a problem.
#voxpelli(The other 50% being validating that the mention is valid)
#voxpelliAnd in doing the link preview an endpoint will host text excerpts, images etc that they have scraped from the sender, to ensure privacy, performance and security
#ZegnatYeah, if your service is being the provider of link previews that may be a problem. hmm
#ZegnatOn the other hand, you could also sell webmentions as a service for those who want to police art 11 ;) You will know when someone has linked to you
iasai, tbbrown, chrisaldrich, jackjamieson, eli_oat, barpthewire, jjuran and KartikPrabhu joined the channel
#@c2dev2↩️ Haha. It isn't like getting Fireballed. :)
I would do:
- basic h-feed support in HTML
- webmention
- indieauth
I don't POSSE anymore really (most of my stuff goes to http://Micro.blog, some also to Mastodon, but that is it). Too much to keep up with. (twitter.com/_/status/1110571740281954305)
[tantek], [Rose], [kenbauer] and [jgmac1106] joined the channel
#GWGaaronpk, if you don't remove the queried last image, it will post, correct?
#Loqi[Greg McVerry] Didn't win @mozilla Responsible Computer Science Challenge makes me $0 out of $1.59 million on the year with another 200k pending....crappy ...
iasai, [Rose], KartikPrabhu, Dmf, [jgmac1106], chrisaldrich, [asuh], [schmarty], [tantek], snarfed, treora and mblaney joined the channel
#jackyjust noticing how "simple" it might be to sync browser bookmarks with one's own site bookmarks
#Loqijacky: Zegnat left you a message 1 day, 8 hours ago: for extracting author (and more) from all sorts of pages you may want to look at some prior art here: https://github.com/zotero/translators - basically extractors for different websites!