#dev 2018-08-25

2018-08-25 UTC
#
tantek__ hmm looks like /in-reply-to could be improved to cause less confusion
TripFandango joined the channel
#
tantek__ e.g. this https://chat.indieweb.org/dev/2018-08-24/1535131286146100
#
Loqi [[scottgruber]] Not sure where to put the in-reply-to property. I tried this “a href=“https://webmention.rocks/test/1” rel=“u-in-reply-to” in an anchro tag and read this documentation which I’m probablyt misunderstanding how to format properly. https://i...
AngeloGladding joined the channel
#
tantek.com edited /in-reply-to () "(-1072) further remove legacy rel=in-reply-to support from algorithms etc - no one is consuming it and remaining docs here were confusing people" (view diff)
#
tantek.com edited /rel-in-reply-to (+54) "was, further discourage consuming" (view diff)
#
tantek__ hopefully that helps the next person that comes by
#
tantek__ what is ptd
#
Loqi Post Type Discovery specifies an algorithm for determining the type of a post by what properties it has and potentially what value(s) they have, which helps avoid the need for explicit post types that are being abandoned by modern post creation UIs https://indieweb.org/PTD
#
willnorris (moved from #microformats) what does Post Type Discovery mean by "valid URL"? Just syntactically valid? Absolute URL (as proposed by microformats/microformats2-parsing#10)?
#
tantek.com edited /post-type-discovery (+46) "updated links, note w3c note snapshot" (view diff)
#
tantek__ good q willnorris. Looks like PTD needs a normative reference to the URL standard for that
#
tantek__ https://url.spec.whatwg.org/
#
tantek__ probably https://url.spec.whatwg.org/#concept-basic-url-parser
#
tantek__ though since PTD assumes you've already parsed the properties, it's likely up to the mf2 parser
#
tantek__ in particular http://microformats.org/wiki/microformats2-parsing#parsing_a_u-_property
#
Loqi [Tantek Çelik] microformats2 parsing specification
#
tantek__ willnorris: could you comment on https://github.com/microformats/microformats2-parsing/issues/10 ? I think your perspective as parser developer is particularly helpful here
#
Loqi [Zegnat] #10 u- parsing should always do relative URL resolution
#
tantek__ I feel like we're close to resolving on that to make the spec change and if it looks good to you (and implementable), we can do so. Maybe you already do this in the Go parser?
[kevinmarks], renem and snarfed joined the channel
#
willnorris tantek: comment and implemented in go parser (in separate branch for now)
#
tantek__ wow awesome
#
tantek__ willnorris++
#
Loqi willnorris has 3 karma in this channel over the last year (6 in all channels)
iasai, koddsson and AngeloGladding joined the channel
#
tantek.com edited /XML (+259) "page logo XML for dummies book modeled by Håkon Lie inventor of CSS" (view diff)
[kevinmarks], AngeloGladding, jeremych_, barpthewire, KevinMarks_ and KevinMarks joined the channel
#
www.romanzolotarev.com edited /design (+1) (view diff)
AngeloGladding and romanzolotarev joined the channel
#
@dimlau 为什么完全没有看到中文世界有关于 webmention 的讨论？ https://www.w3.org/TR/2017/REC-webmention-20170112 来自 Telegram 频道：https://t.me/kaix_in/123 (twitter.com/_/status/1033313566470942720)
nesthib, miklb__, miklb, barpthewire, KevinMarks and wagle joined the channel
#
@AngeloStavrow Shipped a couple of design updates for my Hugo theme to my personal site, separating menu items at the top of the page from previous/next article pagination (now at the bottom of any article). Next step: look into adding/displaying Webmentions. (twitter.com/_/status/1033387381855072258)
KevinMarks, leg, TripFandango, KartikPrabhu, miklb, AngeloGladding, KevinMarks_, wagle, wagle_, michagogo7, [kevinmarks], Gentle, [asuh], barpthewire, [pfefferle], trip_ and [keithjgrant] joined the channel
#
[keithjgrant] Well, this is turning into nearly a complete rewrite of Omnibear 😲
#
[keithjgrant] Want to add Bookmark support -> need to restructure the UI -> might as well rework the overall design -> let's introduce MobX for state management -> oh look, I've redone nearly every file
KartikPrabhu and wagle joined the channel
#
miklb if I'm understanding the docs for Indiepaper, logging in with my URL should redirect to my microsub which is Aperture. However it is just registering my micropub address as the location to publish. Where in that chain should I look for the issue?
#
sknebel > Enter your Microsub server url into the IndieAuth form.
#
sknebel not your homepage
#
KartikPrabhu should it not detect the microsub url with rel=microsub or something?
#
miklb logging in with aperture corrects the problem, but indiepaper.io reads home page.
#
miklb "Login with your website"
tantek__, ChasedSpade, tantek___ and wagle joined the channel
#
tantek.com edited /Digg (+529) "more blockquote - interesting instance of a mass silo quit" (view diff)