61°F

Aaron Parecki

  • Articles
  • Notes
  • Photos
  • Eddie Hinkle https://eddiehinkle.com/   •   Dec 4
    Yeah, you're right again! I did think "I'd have to tweak my channels" but thought it was the closest match.

    I think I might be leaning towards an mp- command rather than a new endpoint. But there are some pros and cons.

    The pros for a new endpoint that is at the same url as the GET for the data is that someone who hasn't built Micropub or wants to use an external service for their stories would make that possible. By de-coupling it, it provides more flexibility.

    The cons for a new endpoint is that the authentication layer, the set up of a new endpoint can be a technical hurdle that might prevent more people form getting involved. For those that already have a Micropub endpoint, the addition of the stories feature becomes a pretty simple add on. It also means there's a new communication layer that people would have to understand, whereas Micropub with an mp- command is pretty simply understood.

    Either solution would be pretty simple for me based on my set up, but I'm trying to think what would be more difficult for: a) Wordpress Users b) Static Site Users, anyone else that is building their own tech stack it's probably not a huge difference.

    That said, I use an external Micropub library in my Node.js server that does the authentication against my token endpoint automatically. So if I were to add a new endpoint, I would have to write the code to handle the verification of my token endpoint. While my token endpoint is on the same server, for other people in similar situations, they might have juggling the authentication process.

    Aaron Parecki
    One of the advantages of a completely new endpoint is that it'd be possible to set up a service to handle stories separate from the rest of someone's content, even with a Wordpress site or other CMS. I looked at my code and i actually implemented the read and writing of story data in a single file just for organizational purposes. I guess the question is whether this kind of content is different enough that someone might want to not mix it in with their micropub or media endpoint handling.

    I also do actual async reencoding of videos that i upload to my story whereas the micropub video files don't get re-processed, so I think that's a sign that a totally separate endpoint makes sense.
    Chicago, Illinois • 31°F
    Tue, Dec 4, 2018 5:54pm -06:00
    2 replies
    • Eddie Hinkle eddiehinkle.com
      If we used a new endpoint, I’m assuming we would just send the same JSON objects that we expect back?
      Tue, Dec 4, 2018 8:35pm -05:00
    • Eddie Hinkle eddiehinkle.com
      Yeah using a completely separate service for stories does make sense as the use case for a separate endpoint. The benefit of the separate service would definitely help people on static sites so that’s a big win.

      That’s really interesting that you handle the videos differently between your stories endpoint and your Micropub Endpoint. Is that for size? Browser compatibility? What’s the thought behind that?

      Makes sense, I’m good with starting the stories experiment with it being a separate endpoint.

      Tue, Dec 4, 2018 8:30pm -05:00
Posted in /replies using monocle.p3k.io

Hi, I'm Aaron Parecki, Director of Identity Standards at Okta, and co-founder of IndieWebCamp. I maintain oauth.net, write and consult about OAuth, and participate in the OAuth Working Group at the IETF. I also help people learn about video production and livestreaming. (detailed bio)

I've been tracking my location since 2008 and I wrote 100 songs in 100 days. I've spoken at conferences around the world about owning your data, OAuth, quantified self, and explained why R is a vowel. Read more.

  • Director of Identity Standards at Okta
  • IndieWebCamp Founder
  • OAuth WG Editor
  • OpenID Board Member

  • 🎥 YouTube Tutorials and Reviews
  • 🏠 We're building a triplex!
  • ⭐️ Life Stack
  • ⚙️ Home Automation
  • All
  • Articles
  • Bookmarks
  • Notes
  • Photos
  • Replies
  • Reviews
  • Trips
  • Videos
  • Contact
© 1999-2025 by Aaron Parecki. Powered by p3k. This site supports Webmention.
Except where otherwise noted, text content on this site is licensed under a Creative Commons Attribution 3.0 License.
IndieWebCamp Microformats Webmention W3C HTML5 Creative Commons
WeChat ID
aaronpk_tv