Aaron Parecki

Friday, April 6, 2018

• 
• 

  9:56pm

  Asleep

  5:45am

  Awake

  7h 49m

  Slept

  13m

  Awake for

  

  Portland, Oregon, USA

  Fri, Apr 6, 2018 5:45am -07:00
• https://github.com/indieweb/wordpress-indieauth/pull/20#issuecomment-379251649
  

  It worked for me, but of course I had to set the authorization endpoint in the settings back to https://indieauth.com/auth.

  If you have the authorization endpoint set to the built-in one, then it would be kind of stuck in a weird state. Which brings me to another point. How do I know what the URL for the built-in authorization endpoint is? Right now if I change it to indieauth.com, then I have no way of knowing what to change it to to make it go back. Blanking out the value just stores a blank value which breaks it. Can you make it revert to the default built-in URL if a blank value is saved?

  Portland, Oregon • 53°F

  Fri, Apr 6, 2018 6:41am -07:00
• https://github.com/indieweb/wordpress-indieauth/pull/20#issuecomment-379257448
  

  @pfefferle what authorization server is it set to use in that case?

  Portland, Oregon • 53°F

  Fri, Apr 6, 2018 6:45am -07:00
• Matt Raible http://raibledesigns.com

  Maybe I should get a MacBook Pro with a Touch Bar after all. Nice hack @aaronpk!

  Portland, Oregon • 53°F

  1 mention

  Fri, Apr 6, 2018 7:28am -06:00 (liked on Fri, Apr 6, 2018 6:51am -07:00)
• https://github.com/indieweb/wordpress-indieauth/pull/20#issuecomment-379259318
  

  Yeah I don't think that makes any sense, since you'd have to be logged in before you can log in. It only makes sense to sign in to wordpress using your domain if you're using an external authorization server.

  Portland, Oregon • 53°F

  Fri, Apr 6, 2018 6:54am -07:00
• https://github.com/indieweb/wordpress-indieauth/pull/20#issuecomment-379259318
  

  I'm not really sure how to solve the UI around this. tbh I think it would make sense to pull out the "log in to your wordpress" feature into a separate plugin, preferably called RelMeAuth or IndieLogin (to match the upcoming indielogin.com that I'm working on), since logging in to wordpress with your domain isn't actually doing IndieAuth.
  
  I'm worried that having both in the same plugin is going to continue to confuse people.

  Portland, Oregon • 53°F

  Fri, Apr 6, 2018 6:57am -07:00
• https://github.com/indieweb/wordpress-indieauth/pull/20#issuecomment-379264089
  

  Not sure what you mean, how does that change anything?

  Portland, Oregon • 53°F

  Fri, Apr 6, 2018 7:08am -07:00
• https://github.com/indieweb/wordpress-indieauth/pull/20#issuecomment-379265037
  

  @pfefferle Yes, that's what the built-in authorization server is for. You can log in to indieweb.org using your domain, where you authenticate at your own wordpress.
  
  Authenticating *into* your wordpress using Twitter/GitHub/other-rel-me things is a totally separate thing, which is why I'm suggesting pulling that out into a separate plugin.

  Portland, Oregon • 53°F

  Fri, Apr 6, 2018 7:20am -07:00
• https://github.com/indieweb/wordpress-indieauth/pull/20#issuecomment-379270896
  

  I don't see this IndieAuth plugin installed on pfefferle.org: https://pfefferle.org/wp-login.php There's only an OpenID option there. Can you clarify exactly what you are expecting to happen?

  Portland, Oregon • 53°F

  Fri, Apr 6, 2018 7:38am -07:00
• https://github.com/indieweb/wordpress-indieauth/pull/20#issuecomment-379275257
  

  So to clarify, you installed this plugin on both sites, and you were trying to log in to one as the other? It would be nice to get more information about the error you're having so we can try to reproduce it.

  Portland, Oregon • 53°F

  Fri, Apr 6, 2018 7:51am -07:00
• https://github.com/indieweb/wordpress-indieauth/pull/20#issuecomment-379281456
  

  Which site was this plugin installed at? Both? And which site was configured to point to indieauth.com?
  
  Technically we shouldn't need to end up on indieauth.com for this use case, though that might need to be a separate set of changes to the plugin.

  Portland, Oregon • 53°F

  Fri, Apr 6, 2018 8:08am -07:00
• https://github.com/indieweb/wordpress-indieauth/pull/20#issuecomment-379314994
  

  indieauth.com should never have been involved in that flow if both wordpress plugins are set to use the internal authorization endpoint. I think your idea that an old options entry is being used is right.

  Portland, Oregon • 56°F

  Fri, Apr 6, 2018 10:24am -07:00
• Jonathan LaCour https://cleverdevil.io/profile/cleverdevil

  The writing has long been on the wall: Twitter is going to destroy its third-party ecosystem. Why? To focus on controlling the entire experience for their proprietary platform. If you haven’t considered the #IndieWeb, now is the time. With services like Micro.blog available, it’s now easier than ever to participate in the open social web.

  Portland, Oregon • 56°F

  Fri, Apr 6, 2018 5:22pm +00:00 (liked on Fri, Apr 6, 2018 10:43am -07:00) #IndieWeb
• singpolyma https://github.com/singpolyma   •   Apr 6

  #152 Diffing for HTML with <article>
  

  We wanted to avoid needing to spell out diffing mechanisms for every conceivable format in the core spec.

  The trick around this to technically remain spec compliant, while also not surprising consumers of the WebSub API, is to say that your WebSub-enabled URL returns only the latest item. That way you can send just the one <article> or whatever, and it still counts as "sending the full contents of the URL". In practice, it's fine to do this as long as the page you're sending has a concept of multiple items in a list, and if your consumers are ready to handle arbitrary numbers of items.

  Portland, Oregon • 60°F

  Fri, Apr 6, 2018 1:47pm -07:00
• An Introduction to the IndieWeb (boffosocko.com)

  1 mention

  Fri, Apr 6, 2018 2:29pm -07:00 #indieweb
• singpolyma https://github.com/singpolyma   •   Apr 6

  We wanted to avoid needing to spell out diffing mechanisms for every conceivable format in the core spec.

  I get this, but why not just allow for format-specific diffing without specifying it? Show the atom one as an example and leave the specifics up to implementation.
  

  I don't remember the exact reasoning anymore, but believe me there was a *lot* of discussion about this. You can probably dig up some of the past threads here if you're so inclined https://github.com/w3c/WebSub/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aclosed+diff

  Portland, Oregon • 62°F

  Fri, Apr 6, 2018 2:46pm -07:00
• 

  Contributions from: Russian Federation, United Kingdom, United States

  Fri, Apr 6, 2018 3:16pm -07:00
• Jeff Atwood http://blog.codinghorror.com   •   Apr 6

  One thing we don’t do but I would like to is tombstoning a forum as static HTML pages (no vulns)
  

  Totally! I did exactly that for all my old startup's websites. Forums, event calendar, blog. I want the content to stick around, but there's no way anyone would keep all that software updated. Flat files ftw. https://github.com/aaronpk/spiderpig http://community.geoloqi.com http://geoloqi.com/blog/

  Portland, Oregon • 68°F

  1 like 2 reposts

  Fri, Apr 6, 2018 5:02pm -07:00
• 

  151.4lbs

  Weight

  16.1%

  Body Fat

  Portland, Oregon • 67°F

  Fri, Apr 6, 2018 6:34pm -07:00
• Eddie Hinkle https://eddiehinkle.com/

  How did you do this??? I need to know! That looks like you edited the global items???

  Portland, Oregon • 62°F

  permalink (liked on Fri, Apr 6, 2018 10:09pm -07:00)