#dev 2017-12-10

2017-12-10 UTC
[miklb], snarfed, John____, chrisaldrich, eli_oat, [tantek] and [chrisaldrich] joined the channel
#
[tantek] Hack ideas for tomorrow
#
[tantek] * improve /pay page with amount
#
[tantek] * improve /pay page with W3C Request Payment API
#
[tantek] * post person tag-of post(s) in reply to aaronpk photo posts
eli_oat joined the channel
#
www.boffosocko.com edited /to-do (+869) "How to IndieWebCamp pages; removed NYC2017 to do" (view diff)
chrisaldrich and renem joined the channel
#
loqi.me created /linter (+83) "prompted by [miklb] and dfn added by [miklb]" (view diff)
#
loqi.me edited /linter (+69) "See Also" (view diff)
snarfed, [eddie] and tbbrown joined the channel
#
[eddie] aaronpk: Should Watchtower have some type of environment variables file? (https://github.com/aaronpk/Watchtower) I’m not seeing any example environment file or anything but I know it’s supposed to have an API key
#
Loqi [aaronpk] Watchtower: a minimal API for watching web pages for changes, roughly speaks the WebSub protocol
snarfed, [miklb] and tantek joined the channel
#
loqi.me created /SB (+146) "prompted by tantek and dfn added by tantek" (view diff)
tantek_ joined the channel
#
tantek.com edited /SB (+0) "typos" (view diff)
#
tantek.com moved /SB to /SL "typo"
#
tantek.com deleted /SB "was typo"
#
aaronpk [eddie] it's lib/config.template.php
#
aaronpk oh sorry, the api key is the `token` column in the user table in the DB
tantek, tantek_, snarfed and [eddie] joined the channel
#
[eddie] aaronpk: ahh, gotcha. I’ll take a look there. Thanks!
tantek, tantek_, raretrack and petermolnar joined the channel
#
gregorlove.com edited /safety_status (+146) "/* IndieWeb Examples */ +me" (view diff)
tantek and jeremycherfas joined the channel
#
Zegnat !tell aaronpk Why does IndieAuth have the response_type parameter? There doesn’t seem to be a way to check if the auth code is being checked by the client (for ID) or by a token endpoint (for authz), to from the authorization endpoint there really is no difference between `id` and `code` requests. Or am I missing something?
#
Loqi Ok, I'll tell them that when I see them next
calumryan joined the channel
#
loqi.me edited /payment (+136) "sknebel added "[https://www.candyjapan.com/behind-the-scenes/candy-japan-hit-with-credit-card-fraud some notes on credit card fraud from CandyJapan]" to "See Also"" (view diff)
jonnybarnes joined the channel
#
aaronpk good morning
#
Loqi aaronpk: Zegnat left you a message 3 hours, 21 minutes ago: Why does IndieAuth have the response_type parameter? There doesn’t seem to be a way to check if the auth code is being checked by the client (for ID) or by a token endpoint (for authz), to from the authorization endpoint there really is no difference between `id` and `code` requests. Or am I missing something?
#
Loqi guten morgen
#
aaronpk Zegnat: that's a good point, perhaps we need to add a parameter here https://indieauth.net/spec/#authorization-code-verification-0
#
aaronpk although the absence of scope might be enough information
#
Zegnat But scope isn’t required.
#
aaronpk can you issue a token with no scope?
#
Zegnat I wouldn’t do it, but I don’t think the spec as is requires scope?
#
Zegnat Does OAuth require scope?
#
aaronpk ah it's subtle
#
aaronpk https://tools.ietf.org/html/rfc6749#section-3.3
#
Zegnat You could on verification have the authorization endpoint say for what type it issued its code. If it isn’t `code`, but `id`, a token endpoint could refuse to issue a token. Was my first thought.
#
aaronpk if the client doesn't request a scope, the authorization must set a default or reject the request
#
aaronpk so the token endpoint should not issue a token if the auth code verification step returns an empty scope
#
Zegnat Yeah, that last paragraph of that section really sneaks up on you, ha
#
aaronpk and response_type=id vs code tells the authorization server whether or not to include a scope in the auth code
#
Zegnat Yes, seems fine now. So auth endpoints for response_type=code always set a scope, and token endpoints for no scope on code verification should not issue a token.
#
aaronpk yep, those notes seem worth adding to the spec
#
aaronpk can you file an issue for each of those?
#
Zegnat Those two requirements are pretty simple to understand, but only become clear upon reading the OAuth spec. And only that one paragraph.
#
aaronpk yep haha
#
Zegnat Happy to. Do you have an issue tracker for the spec?
#
Loqi haha
#
aaronpk https://github.com/aaronpk/indieauth.net/issues
#
Zegnat I’m about to get something to snack, when I get back to the keyboard I’ll file these as separate issues.
#
Zegnat This was one of those things that came up working on my token endpoint :) I was wondering how to make sure I wasn’t issuing tokens for authentications.
#
aaronpk awesome
[miklb] joined the channel
#
raretrack.uk edited /User:Raretrack.uk (+50) "New 'completion' and general tidy-up" (view diff)
snarfed joined the channel
#
Zegnat aaronpk: issues filed, I hope they make sense as written.
#
Zegnat Hope I got all my code/token/auth/auth nomenclature right :P
tbbrown and tantek joined the channel
#
raretrack.uk edited /User:Raretrack.uk (+67) "Micro-blog itch scratched" (view diff)
#
kaja.sknebel.net created /User:Kaja.sknebel.net/test (+4) "Created page with "test"" (view diff)
snarfed and tantek joined the channel
#
tantek.com edited /reacji (+35) "/* How to markup */ link to specific section" (view diff)
cgrayson and snarfed joined the channel
#
tantek as promised, ownyourswarm delete support feature request: https://github.com/aaronpk/OwnYourSwarm/issues/36
#
Loqi [tantek] #36 support PESOSing delete updates from Swarm to your own site
#
eddiehinkle.com edited /Indigenous (+573) "added some micropub post examples for people attempting to ensure support" (view diff)
[eddie] joined the channel
#
[eddie] manton I added the current micropub posts sent from Indigenous to the project page for you and others who might attempt to add support: https://indieweb.org/Indigenous#Examples_of_Micropub_Posts_Sent
#
blog.storycards.net edited /IRC_People (+128) "added myself (cgrayson)" (view diff)
#
[eddie] manton The current build I’m working on adds publishing “notes” which follow the standard micropub `content=` (https://indieweb.org/Micropub#New_Note) So that I’m assuming to work with micro.blog out of the box
[manton] joined the channel
#
[manton] eddie Excellent, thank you. And if you were watching the stream, apologies for completely mispronouncing Indigenous. 🙂
#
[eddie] haha, no worries. I change the pronunciation every time I say it 🙂 Which isn’t often since most my discussions happen on the internet 😄
#
Loqi rofl
#
herestomwiththeweather.com edited /IRC_People (+131) "tbbrown" (view diff)
#
[manton] Notes should definitely work with Micro.blog now. I'm working on mapping bookmark-of to Micro.blog favorites today... It's not all a perfect mapping but I think it's the place to start.
tantek joined the channel
#
Zegnat How are Micro.blog favourites different from Micropub/mf2 bookmark posts?
[jeremycherfas] joined the channel
#
[jeremycherfas] What is together?
#
Loqi Together is a reader that was initially conceived at the 2017 IndieWeb Summit in Portland by Jonathan LaCour and several others during the Putting it all together session https://indieweb.org/together
#
[eddie] manton awesome. Yeah I think bookmark and favorites is a pretty good pairing.
#
[eddie] Zegnat: favorites aren’t public ally displayed
#
[eddie] So a favorite is a visibility private bookmark
#
[eddie] I think the purpose of both is identical
#
[manton] That sounds right. I may end up renaming Favorites to Bookmarks. Although then the "star" icon makes less sense, so I'm not quite ready to do that.
#
Zegnat Google Chrome uses a star for bookmarks.
#
Zegnat Unless they changed that and I never noticed.
#
Zegnat Firefox uses a star for bookmarks too.
#
tantek Flickr favorites are publicly displayed btw
#
[manton] Cool. Maybe it wouldn't be too confusing to keep it, then.
#
tantek I feel like Google Reader had the ability to privately *star* items
#
tantek but I can't quite remember. maybe if someone has screenshots
#
tantek maybe Kevinmarks blogged about favoriting things in Google Reader
#
Zegnat I think Google Reader’s starring was much like Gmail’s starring.
#
Zegnat If Gmail still has that…
#
[manton] Something like this is what I was thinking this morning if we wanted a way to discover types and have them adapt to whatever names a Micropub endpoint used... The concern raised is that it could become kind of too abstract and complicated. https://gist.github.com/manton/bc51805cf421ba45b13cd7214f48a034
#
sknebel reader hat star and like
#
sknebel star was private
#
Zegnat My RSS reader, Reeder on macOS, still has an option to “star” feed items.
#
Zegnat It is basically private bookmarking.
#
[manton] Yep. In the case of Reeder they actually call them "Starred Items".
#
aaronpk [manton]: the trick with that is those properties depend on the vocabulary, so those actually are saying which h-entry properties the server supports. if a server supports h-event, then you also want to know that, and also which properties in h-event are supported. so this quickly gets out of hand.
#
[manton] Hmm, yeah... I'm coming at this from the simpler actions (really from just thinking about what the user sees), but that's a great point.
#
tantek there's a big difference between /response posts and others like /note vs /article vs /event etc.
#
tantek the former typically have actions associated with them, perhaps even /webactions
#
aaronpk if you look at all the kinds of posts Quill supports, it'd be a natural extension of this idea to want to try to discover support for each of those as well, some of which are top-level h-* objects https://media.aaronpk.com/Screen-Shot-2017-12-10-11-13-14-keHdpBM0d4.jpg
#
aaronpk e.g. events, reviews, itinerary
snarfed and tantek joined the channel
#
loqi.me edited /social_media (+143) "tantek added "2017-05-17 [https://www.thecut.com/2017/05/social-media-friendship-impact.html When You Love Your Friend But Hate Her Social-Media Presence]" to "See Also"" (view diff)
#
[eddie] manton if through brainstorming you are able to come up with a good potential solution to the posting type discovery, and make micro.blog a publisher, I’d be happy to make indigenous a test consumer, because while complicated I do think that information is an important next step in our tools as more Gen 2/3/4 come into IndieWeb tools and it becomes difficult to explain why Quill or Indigenous has all these interface options that break or donâ€
#
[eddie] Like tantek said when talking about photo person tags, brainstorming and then testing is the only way to find out what works and what doesn’t
#
[eddie] I think the key would be making sure the consumer (the Micropub app) if it doesn’t find the mp types configuration, it defaults to everything being available.
#
Zegnat I wonder if there is some way to specify the post types (as per https://www.w3.org/TR/post-type-discovery/) that are supported by the Micropub endpoint, rather than specifying the exact properties it expects.
#
Loqi [Tantek Çelik] Post Type Discovery
#
tantek Zegnat - I think you have that backwards
#
tantek or did you mean to cite PTD as a way of determining the post type?
#
Zegnat As a way to have a list of standardised names, basically
#
tantek names of types?
#
Zegnat yes
#
tantek interesting
#
tantek those are from /posts
#
Zegnat Instead of what [manton] showed where he used “repost-of” (which is a property), or exposing what root h-* objects are supported, just tell the client what types the endpoint can create.
#
Zegnat Though not sure how useful that would actually be.
#
tantek yeah that's kinda the problem, it goes down the type discovery rathole
#
tantek what is ws-deathstar?
#
Zegnat Just a random thought I had. Was reading the chat backlog while waiting for dinner.
#
Loqi The monoculture antipattern is best described as, if only everyone would install and run this one open source project then we will be good https://indieweb.org/WS_Deathstar
#
tantek.com edited /silo-quits (+606) "add a couple of future silo quits, @tmcw, Eddie Hinkle, both Goodreads" (view diff)
leg joined the channel
#
[eddie] Yeah, it’s tough. But I think ultimately h-roots and properties are really what the Micropub clients need to know in order to know what to send and what not to send
#
[eddie] I think h-entry is really the biggest fluctuating h-based item, so I wonder if you somehow define the h-types and then just the h-entry properties and assume all properties for anything not an h-entry?
#
tantek [eddie] there are different levels of stability explicitly in the h-entry spec, take a look: http://microformats.org/wiki/h-entry
#
Loqi [Tantek Çelik] h-entry is a simple, open format for episodic or datestamped content on the web. h-entry is often used with content intended to be syndicated, e.g. blog posts. h-entry is one of several open microformat standards suitable for embedding data in HTML. ...
#
aaronpk if something like this were to happen, which i'm still not convinced it should, this would be more like how i'd expect to see it https://gist.github.com/aaronpk/37354ab728f1a3115411d1e94d4f18dd
[manton] joined the channel
#
[manton] Yeah, I see the slippery slope to WSDL if we go down that path... I was really just thinking about what the user sees, e.g. "Does this server allow me to bookmark something?"
#
tantek manton, is it so bad if the server only allows the fallback behavior?
#
tantek the interesting thing is, in practice the fallback summary text is unique enough per existing response type that their simple fallback reply posts could get upgraded in the future
#
tantek (user) bookmarked (URL)
#
tantek is unlikely to match any false positives that were not intended as /bookmark posts
#
[manton] I hadn't thought about it until today... If Indigenous (for example) will eventually show 5-10 different options for the user, what would they expect to happen if they choose "RSVP" or some of the less common ones. Not sure.
#
Zegnat Yeah, that's what gRegorLove does for his read posts. Makes sure to have a fallback value for the post in the content property
#
[manton] Aaron proposed that "summary" might be better for a fallback in some cases. I just checked and Micro.blog actually ignores summary at the moment, although that's easy to change.
#
Zegnat https://gregorlove.com/2017/11/martijn-asked-if-i-had/ uses an html key within the content property as "fallback".
#
Loqi [gRegor Morrill] Martijn asked if I had documented the micropub request I make for read posts. I had not yet, so decided to make some quick notes while it's fresh in my mind. Currently, it sends an h-cite object with properties: status, url, name, author, and isbn....
snarfed and chrisaldrich joined the channel
#
tantek.com edited /tag-reply (+651) "/* Facebook */ Facebook notifications of person-tag replies, Facebook POSSE" (view diff)
snarfed joined the channel
#
@jackysee @adactio written a response ( https://jacky.seezone.net/2017/12/10/9977/ ) to your article ( https://adactio.com/journal/13187 ) but seems cannot send webmention to the article using the form below. (twitter.com/_/status/939934024079884288)
#
Zegnat webmention++ the original mention on https://gregorlove.com/2017/11/martijn-asked-if-i-had/ never reached me, but I could just send it to me myself! Truly decentralised.
#
Loqi webmention has 1 karma in this channel (3 overall)
#
Loqi [gRegor Morrill] Martijn asked if I had documented the micropub request I make for read posts. I had not yet, so decided to make some quick notes while it's fresh in my mind. Currently, it sends an h-cite object with properties: status, url, name, author, and isbn....
#
vanderven.se martijn uploaded /Special:Log/upload "uploaded "[[File:facebook-select-destination-web.png]]" https://indieweb.org/File:facebook-select-destination-web.png"
#
GWG I can call my PR... Support my Indiewebcamp Austin 2017 hack day project, can't I?
#
tantek of course
#
vanderven.se martijn edited /destination (+495) "/* Facebook */ Web interface for chosing a destination." (view diff)
[miklb] joined the channel
#
tantek.com edited /tag-reply (+138) "/* Facebook notifications */ screenshot of when someone person-tags you in a photo" (view diff)
#
tantek.com edited /tag-reply (+91) "/* Facebook notifications */ person-tag reply notification text from email" (view diff)
#
gRegorLove Zegnat: Oh yeah, thanks for the reminder to check my URL discovery. I think it trimmed the trailing slash off your URL for some reason, so found the wrong endpoint
#
Zegnat If you need me for any debugging, ping me
#
tantek what is an edit
#
Loqi An edit (AKA diff, change) is a special type of reply that indicates a set of suggested changes to the post it is replying to. A collection of (presumably related) suggested edits in open source is often called a patch or pull request https://indieweb.org/edit
#
tantek what is a location tag
#
Loqi location-of is a response to post that indicates location information for the post https://indieweb.org/location_tag
#
tantek edit << tag-of
#
Loqi ok, I added "[[tag-reply]]" to the "See Also" section of /edit
#
loqi.me edited /edit (+16) "tantek added "[[tag-reply]]" to "See Also"" (view diff)
#
tantek edit << location-tag
#
Loqi ok, I added "location-tag" to the "See Also" section of /edit
#
loqi.me edited /edit (+15) "tantek added "location-tag" to "See Also"" (view diff)
#
tantek edit << location-of
#
Loqi ok, I added "[[location-of]]" to the "See Also" section of /edit
#
loqi.me edited /edit (+18) "tantek added "[[location-of]]" to "See Also"" (view diff)
#
tantek better
#
tantek what is a location-tag
#
Loqi location-of is a response to post that indicates location information for the post https://indieweb.org/location_tag
#
tantek.com edited /edit (+442) "Special Edit Posts" (view diff)
#
tantek tag-of << edit
#
Loqi ok, I added "[[edit]]" to the "See Also" section of /tag-reply
#
loqi.me edited /tag-reply (+11) "tantek added "[[edit]]" to "See Also"" (view diff)
#
tantek location-of << edit
#
loqi.me edited /location-of (+11) "tantek added "[[edit]]" to "See Also"" (view diff)
#
Loqi ok, I added "[[edit]]" to the "See Also" section of /location-of
#
tantek.com edited /tag-reply (+63) "tag-reply is a special edit post" (view diff)
#
tantek untag << edit
#
Loqi ok, I added "[[edit]]" to the "See Also" section of /untag
#
loqi.me edited /untag (+28) "/* See Also */ new section" (view diff)
#
tantek edit << untag
#
Loqi ok, I added "[[untag]]" to the "See Also" section of /edit
#
loqi.me edited /edit (+12) "tantek added "[[untag]]" to "See Also"" (view diff)
#
tantek.com edited /untag (+191) "expand dfn, edit post, use case as a list of steps" (view diff)
#
tantek ok now that I've loaded into my head how /tag-of (including /person-tag reply) posts could/should work, and deduced that they really are a special variant of an /edit post, I've documented what I figured out to hopefully make more incremental progress on that next time
#
tantek that's too much to try to implement in less than two hours, but definitely glad I worked through a bunch more of the details (added to research on /tag-of silo examples and brainstorming) and made the connections between /edit /tag-of /location-of and /untag
#
tantek so that's it for that attempted new feature (for today), back to the "easier" problems
#
tantek.com edited /Falcon (+123) "/* one-off person-tag response to photo */ example aaronpk check-in I could try person-tagging with manton" (view diff)
#
tantek.com edited /tag-reply (+114) "/* person tag reply */ interested in implementing, link to Working On subsection with details there" (view diff)
#
tantek you're safe for today aaronpk, you won't be getting any person-tag reply posts from me just yet. but I have uncovered more of the key details in how to do so, including how to implement it in /Falcon in particular, so next time I may have better luck
#
aaronpk *whew*
#
sknebel hm, untag would also somehow contain hiding the /untag post
[manton] joined the channel
#
[manton] eddie One thing I ran into while testing Indigenous... I had to add NSAllowsArbitraryLoads to the Info.plist for the share extension. The OS was never letting the app hit Micro.blog's Micropub endpoint.
#
sknebel either by using /private-webmention or other ways of hiding it
#
sknebel (e.g. not including it in feeds, and receivers not linking it)
#
sknebel (^^^ tantek)
#
tantek sknebel - presumably if it works correctly it can self-destruct :)
#
tantek and yes - good point about not including it in feeds
#
tantek that's worth adding to /untag - please go ahead!
#
www.svenknebel.de edited /untag (+366) "privacy/deletion" (view diff)
#
www.svenknebel.de edited /User:Kaja.sknebel.net (+35) "document new /live functionality" (view diff)
#
sknebel true, if the tag-post is gone there is no need to keep the untag rquest around. added that
[jeremycherfas] and KartikPrabhu joined the channel
#
gRegorLove For micropub /citations, thinking about what the q= should be to return a list of status options ("Want to read", "Reading", etc.)
#
gRegorLove q=citation-statuses?
#
aaronpk start with what you'd publish on the post, and how you'd mark it up in h-entry
#
sknebel so not post types in general, only cites? and the client would know that it should offer to create those properties with h-cite?
#
gRegorLove It's not marked up in the h-entry currently, just text prefixed to the h-cite, and included in the e-content / summary properties so the fallback is human friendly.
#
gRegorLove The options exist in the forked Quill form already, they're just hard-coded.
#
sknebel hm. sort of like templates for different post types
#
gRegorLove It gets sent in the mf2 as property 'status'
#
aaronpk is this like https://indieweb.org/Micropub-extensions#Post_Status ?
#
gRegorLove Here's an example post: https://gregorlove.com/2017/06/want-to-read-testing-3/
#
Loqi [gRegor Morrill] Want to read: Testing 3
#
gRegorLove checks that out
#
gRegorLove Similar, but this property affects content that appears in the post, isn't about the status of the post itself / where it should or should not appear.
#
gRegorLove It's like the action you're indicating on the thing you're citing.
#
gRegorLove I want to read x, I'm currently reading y, I finished reading z
#
gRegorLove So maybe q=citation-actions
#
aaronpk something about this doesnt seem right
#
aaronpk I don't think it's right to call these "citation" posts
#
gRegorLove I'm definitely open to alternatives. Still pretty new to micropub
#
aaronpk they happen to include a citation of a book, but that's not the primary purpose
#
aaronpk they are "read" posts, right?
#
tantek finds a citation for limiting US payment amounts to $14k: http://enwp.org/Gift_tax_in_the_United_States#Non-taxable_gifts
#
gRegorLove what is read?
#
Loqi To read or reading is the act of viewing and interpreting posts or other documents; on the IndieWeb, a read post expresses that something has been read, like a book or section thereof https://indieweb.org/read
#
gRegorLove Yeah, I think they're /read posts
#
gRegorLove So q=read-actions, or does the querying idea itself seem off?
#
aaronpk the query idea isn't necessarily wrong, but I am somewhat skeptical that it's necessary
#
aaronpk it seems like there will likely be a set of terms agreed on by people who are posting read posts, and a client can just hardcode those
#
aaronpk the idea with the query API is it's for things that *can't* be hardcoded in a client, like the list of syndication endpoints
#
gRegorLove Hm, yeah. i18n was the initial thought process behind it.
#
aaronpk what you're seeing is the problem with trying to start at the Micropub level rather than starting at the Microformats level
#
aaronpk if you start with microformats and define a vocabulary and publishing and consuming use cases, then it becomes more straightforward in micropub
#
gRegorLove Well, I had plenty of /read posts before I started with this. Called them citations since it was using h-cite.
#
gRegorLove So publishing uses cases were there, not consuming though
#
aaronpk checks /read for consuming use cases
#
aaronpk "...to notify the author of a document that you have read it"
#
aaronpk so in that case, you'd want the book URL to understand the difference between "have read" and "want to read", so those are good consuming use cases for read posts
#
gRegorLove /read is heavily worded towards reading URLs, not so much books.
#
aaronpk in order for that to work, there needs to be a common vocabulary of those terms
#
aaronpk if there is a common vocabulary, there is no need for querying the list of options
#
gRegorLove And currently the URLs are my local isbn redirects, so notifying them doesn't seem important to me.
#
aaronpk you see where I am going with this though, right?
#
gRegorLove I did recently start consuming the h-cites in my /read posts to generate https://gregorlove.com/reading/
#
gRegorLove Kind of. Not sure.
#
gRegorLove I'm definitely using it for the first use case there "to share books, etc. with followers" and eventually to track metrics for myself, like # of books read.
#
aaronpk okay so imagine there was an aggregator that collected /read posts from a bunch of people
#
aaronpk it would want to group them based on "have read" or "want to read" and other variations
#
aaronpk so you also want that common vocabulary of statuses for that purpose
#
gRegorLove Sure, that makes sense. It seems odd that I need to work backwards from an aggregator that doesn't exist, though.
#
tantek.com edited /tag-reply (+424) "/* person tag reply */ multiple URLs" (view diff)
#
gRegorLove I understand working through the consuming use-cases, but not sure what to do if I want to start using mp for this today (or soon)
#
gRegorLove Other than keep posting them manually, which I guess is fine :)
#
aaronpk well, i'd say start by marking them up with microformats
#
aaronpk so that you force yourself to define the h-entry and h-cite properties
#
gRegorLove The statuses?
#
aaronpk all your read posts
#
gRegorLove They are. That's what I'm saying.
#
aaronpk I just see text
#
aaronpk "name: Want to read: Testing 3"
#
aaronpk no mf2 property on "want to read"
#
gRegorLove Ah, gotcha. Yeah that's why I asked "the statuses?" The rest is marked up. Ok, I'll brainstorm
#
aaronpk once you do that, does it make sense to let every site define its own list?
#
aaronpk i'm guessing the answer is no, that wouldn't be very useful
#
gRegorLove i18n could still be an issue, until sites processed the mf2 directly. My own doesn't; it's using the fallback e-content
#
aaronpk localization of the text is for display purposes, not for processing purposes
#
aaronpk we don't translate mf2 properties like dt-published
#
gRegorLove Right. But since my site doesn't process the micropub h-cite, it falls back to the e-content generated by the Quill fork.
#
aaronpk wait a sec now you've lost me completely. your site doesn't even interpret this property itself?
#
aaronpk at that point isn't this micropub client just letting you pre-select text for a post?
#
gRegorLove Yes, exactly.
#
gRegorLove Don't worry, not pursuing the q= option currently.
KartikPrabhu joined the channel
#
aaronpk so if I take your example post, i'd imagine seeing something like <div class="e-content"><data class="p-read-status" value="want-to-read">Want to read</data>: <em class="h-cite"> ...
#
gRegorLove At IWS since my site didn't process h-cite properties and neither did Jack's WP site, we wanted a useful fallback so people could start using it. More details: https://gregorlove.com/2017/11/martijn-asked-if-i-had/
#
Loqi [gRegor Morrill] Martijn asked if I had documented the micropub request I make for read posts. I had not yet, so decided to make some quick notes while it's fresh in my mind. Currently, it sends an h-cite object with properties: status, url, name, author, and isbn....
#
gRegorLove Which sounds like it isn't quite the right way to proceed.
#
gRegorLove Yeah, I'm thinking mf2 values: reading, want-to-read, finished-reading as a starting point.
#
aaronpk yeah I would expect that you're posting an h-entry, so that you get the regular post properties published/author/content/etc. then like a bookmark-of adds additional data, you're adding additional info about the thing you're reading and your read status. so your h-entry could include a "p-read-of" property that is an h-cite that describes the thing you're reading.
#
gRegorLove p-read-status on the h-cite, then? or on the h-entry?
#
aaronpk on the h-entry. h-cite is just describing the thing you're reading
#
gRegorLove !mf2 https://gregorlove.com/2017/11/want-to-read-typewriters-iconic/
#
Kaja https://php.microformats.io/?url=https%3A%2F%2Fgregorlove.com%2F2017%2F11%2Fwant-to-read-typewriters-iconic%2F
#
Loqi [gRegor Morrill] Want to read: Typewriters: Iconic Machines from the Golden Age of Mechanical Writing
#
gRegorLove Progress!
#
aaronpk look at that Loqi fallback!
#
gRegorLove aaronpk++ thanks for helping me through all that
#
Loqi aaronpk has 93 karma in this channel (1503 overall)
[eddie] joined the channel
#
[eddie] manton ohhh yeah. Thanks for flagging that. Definitely let me know if you run into anything else. That bug is fixed in the new build: https://github.com/EdwardHinkle/indigenous-ios/commit/b29153c0ba11566b4671e20db097b485ae3d7615
#
Zegnat Huh. Loqi seems smarter than the PHP Microformats parser? It added a space between “Want to read:” and “Typewriters:” that I am not seeing on microformats.io
#
gRegorLove Darn whitespace collapsing around <data> in the parsed p-name though.
#
gRegorLove Heh
#
aaronpk oh yeah looks like microformats.io has an older version
#
Zegnat BTW, you probably want I and not EM, gRegorLove. You are not putting spoken emphasis on the book title.
#
Zegnat <I> the element, that is.
#
gRegorLove Oh really? Huh, I just thought <em> was the recommended way for all italics these days. Interesting.
#
gRegorLove the-more-you-know.gif
#
Zegnat Nope. EM is specifically for emphasis. I, B, and U, are still all around for marking text to be visually different :)
#
gRegorLove Went with <cite>, actually.
#
Zegnat The spec also gives descriptions for use-cases for all three, but I tend to forget those specifics. For I it still mentions books I believe.
#
aaronpk !meme the-more-you-know.gif [the more you know meme]
#
Zegnat CITE seems fine too. Though I am not sure how CITE is currently described, I recall some sort of web-dev petition in the early HTML5 days about its usecases.
[manton] joined the channel
#
[manton] eddie Actually it needs to be added to the Info.plist for the sharing extension, too, not just the main app.
#
[eddie] manton ohhh. Well in the new build you can also post from the main app, so I’m guessing it’ll be needed then?
#
gRegorLove Ok, updated that previous book link to use cite.
#
[manton] Oh cool, I didn't realize that. Yeah, I think it should be in all Xcode targets.
#
[eddie] Ohh I see what you mean. I don’t think it’s in the Share ext at all, so I do need to add it there
#
[manton] As aaronpk commented to me, I need to fix whatever is weird with Micro.blog's SSL certs so that Apple accepts them, but I think this Info.plist change is good until more people support https.
#
[eddie] Definitely good to support http for now
#
aaronpk 🙉
#
[manton] Heh.
#
[eddie] So yay, that’s totally an open bug. Thanks, I’ll put that into the next build.
#
[manton] Cool, thanks!
#
[manton] I'm thrilled with the way Apple handled this... I wish there was some feedback to the user when it's not https or there's an issue with the cert.
#
[manton] Er, _not_ thrilled.
#
Zegnat gRegorLove++ for semantic HTML <3
#
Loqi gregorlove has 35 karma in this channel (193 overall)
snarfed joined the channel
#
kaja.sknebel.net created /User:Kaja.sknebel.net/upcoming-hwcs (+1620) "update from /Events" (view diff)
#
www.svenknebel.de edited /Main_Page () "(-554) /* Homebrew Website Club */ upcoming via Kaja, remove if it gets in the way :)" (view diff)
#
@rMdes_ ... Get a webmention like ping that push your new address to their system and voila. You want to vote? ID with your NFC phone + a paper vote uniquely generated for you, login, vote, you can choose to make your vote public in the ledger or not and stay anonymous but authentified (twitter.com/_/status/939982249386225664)
tantek joined the channel
#
gregorlove.com edited /read (+135) "/* gRegor Morrill */ +p-read-status" (view diff)
[miklb] and oodani joined the channel
#
www.svenknebel.de edited /Posting_from_mobile_devices (+192) "/* Posting from your mobile device */ add app used by GWG" (view diff)
#
tantek.com edited /payment (+37) "/* How */ note cash.me is different from SquareUp!" (view diff)
#
tantek.com edited /Square (+219) "Square Up section, note Square Cash is different!" (view diff)
#
www.svenknebel.de edited /Main_Page (+5) "/* Upcoming IndieWebCamps */ BALTIMORE" (view diff)
#
aaronparecki.com edited /User:Aaronparecki.com (+296) "/* to do */" (view diff)
#
grant.codes edited /trakt.tv (+239) "Add info on trakt.tv to micropub scipt" (view diff)
John____ joined the channel
#
grant.codes edited /watch (+307) "Add Grant Richmond examples" (view diff)
#
tantek and I just got Square Cash setup on my /pay page as well!
KartikPrabhu joined the channel