Aaron Parecki

Tuesday, February 20, 2018

• 
• 

  9:16pm

  Asleep

  4:39am

  Awake

  7h 23m

  Slept

  19m

  Awake for

  

  Portland, Oregon, USA

  Tue, Feb 20, 2018 4:39am -08:00
• snarfed https://github.com/snarfed   •   Feb 20

  ...also, of course, i've now realized that while this mf2py feature is great, it doesn't actually quite fix this issue, since this is on the consuming side, where i don't control the parser.

  @aaronpk, depending on your usage, you might consider asking granary for format=mf2-json instead of format=html, since that won't have this problem! i'm guessing you reported this on behalf of someone else who's seeing granary html output in a feed reader, though, so you don't have that luxury either.

  adding blank p-name is totally reasonable. will do.
  

  That's great news! And yes, I was specifically asking for the blank p-name property to be added to the HTML so that parsers that haven't updated for the new implied name parsing rules will still get a result that looks good.

  Portland, Oregon, USA

  Tue, Feb 20, 2018 6:53am -08:00
• Jon Mitchell https://jonmitchell.net/micro/?author=50537478e4b0e1565e12dbbe

  Sorry for talking about the thing on the thing, but Micro.blog not having follower counts might be the sanest product decision in social web history.

  Portland, Oregon • 31°F

  Mon, Feb 19, 2018 12:00am +00:00 (liked on Tue, Feb 20, 2018 7:33am -08:00)
• manton https://github.com/manton   •   Feb 20

  @aaronpk I'm glad you mentioned Post Type Discovery, because to me that is the part to focus on. It seems too complicated to require spelling out every property, like category or photo. If an endpoint doesn't support accepting a category on a new post, no harm done.

  What can we borrow from the Post Type Discovery spec that will help here? At the very least it seems like the Microformats class names should be consistent.

  In my example (https://indieweb.org/Micropub-brainstorming#Query_for_supported_vocabulary) I included what I view as the common actions from an app like Indigenous: like-of, repost-of, and bookmark-of, but bookmarks aren't actually mentioned in Post Type Discovery. I wonder if they should be, or are they not different enough from a regular post to list separately?
  

  Interesting, I didn't actually realize bookmark wasn't in Post Type Discovery. It looks like it was mentioned under "Other Types Under Consideration" before it was moved to the W3C repo. Now the W3C note links to the Kinds of Posts section on the IndieWeb wiki for that.

  The way we were adding things to the list of types in the algorithm was roughly based on how well-established the markup was in the wild. I am kind of surprised bookmarks didn't make that cut, but oh well.

  The one potential confusion here is that post types are not the same as h-* types, e.g. there is no h-reply because you use the in-reply-to property on h-entry to create a reply post. I think that just means we need to be explicit about what to call this. To build on your previous example, this could be a solution:

  {
    "post-types": [
      {
        "type": "note",
        "name": "Note"
      },
      {
        "type": "article",
        "name": "Blog Post"
      },
      {
        "type": "photo",
        "name": "Photo"
      },
      {
        "type": "video",
        "name": "Video"
      },
      {
        "type": "reply",
        "name": "Reply"
      },
      {
        "type": "like",
        "name": "Like"
      },
      {
        "type": "repost",
        "name": "Repost"
      },
      {
        "type": "rsvp",
        "name": "RSVP"
      },
      {
        "type": "bookmark",
        "name": "Bookmark"
      }
    ]
  }
  

  Clients should assume that if it's not in the list, then the server doesn't support it? Of course there needs to be some sensible behavior for servers that don't return this info at all.

  Would it make sense to omit note from this list since that's kind of a baseline? Or keep it in the list because it allows the client to customize the name of the button still?

  Portland, Oregon, USA

  Tue, Feb 20, 2018 9:22am -08:00 #micropub
• EdwardHinkle https://github.com/EdwardHinkle   •   Feb 20

  Yep, exactly. Or a specialized app like Teacup that sends ate and drank posts. Those should still go through regardless.

  As you said, @manton, it's more of a suggestion but especially a suggestion for generalized Micropub application, as opposed to specialized.
  

  That makes sense, and also fits nicely with the idea of this as an extension rather than part of the base spec.

  Portland, Oregon, USA

  Tue, Feb 20, 2018 10:16am -08:00 #micropub
• Every Month Portland’s Infill Rules Aren’t Changed, the City Looks More like This | Sightline Institute (www.sightline.org)

  Tue, Feb 20, 2018 2:15pm -08:00 #pdx #housing #construction
• Dan Malouff http://beyonddc.com

  Is your child texting about transit? Know the signs.
  BTW—Bus/Trolley War
  GTG—Get Transit, Girlfriend
  FML—Fund My Light-rail
  IMHO—If Metro Had Operated
  ICYMI—In Case Your Mode-share Increases
  TLDR—Transit Loves Dedicated Right-of-way
  LOL—Love Of Locomotives
  BRB—Big Rapid Bus

  Portland, Oregon • 33°F

  Mon, Jan 29, 2018 3:12pm -05:00 (liked on Tue, Feb 20, 2018 2:20pm -08:00)
• Emoji Builder (phlntn.com)

  Tue, Feb 20, 2018 6:30pm -08:00 #emoji
• EdwardHinkle https://github.com/EdwardHinkle   •   Feb 20

  #121 Add support for mp q=config destination
  

  This is exciting. This will motivate me to work on the multiple destination support I have in mind for my website!

  Portland, Oregon • 32°F

  Tue, Feb 20, 2018 6:41pm -08:00
• Nicolás Álvarez https://twitter.com/nicolas09F9   •   Feb 21

  @aaronpk where can I report errors in http://oauth.com?
  

  Feel free to send me an email https://aaronparecki.com/contact

  Portland, Oregon, USA

  Tue, Feb 20, 2018 8:04pm -08:00