68°F

Aaron Parecki

  • Articles
  • Notes
  • Photos

Tuesday, December 4, 2018

← Older → Newer
plane
3 hr 47 min
 
taxi
40 min
 
bus
11 min
 
1779.2 miles
 
plane
22.7 miles
 
taxi
1.5 miles
 
bus
  • 11:37pm
    Asleep
    6:48am
    Awake
    7h 11m
    Slept
    42m
    Awake for
    Los Angeles, California, USA • 54°F
    Tue, Dec 4, 2018 6:48am -08:00
  • Aaron Parecki
    at Waypoint Kitchen
    Los Angeles, California • Tue, December 4, 2018 7:34am
    33.94579 -118.392815
    Los Angeles, CA, United States • 54°F
    3 Coins
    Tue, Dec 4, 2018 7:34am -08:00
  • Aaron Parecki
    at H Hotel Los Angeles, Curio Collection by Hilton
    Los Angeles, California • Tue, December 4, 2018 9:01am
    33.946061 -118.392729
    Los Angeles, CA, United States • 59°F
    19 Coins
    Tue, Dec 4, 2018 9:01am -08:00
  • Bus
    1.49mi
    Distance
    10:47
    Duration
    9:04am
    Start
    9:15am
    End
    Los Angeles, California • 61°F
    Tue, Dec 4, 2018 9:15am -08:00
  • Aaron Parecki
    at Los Angeles International Airport (LAX)
    Los Angeles, California • Tue, December 4, 2018 9:16am
    33.943324 -118.405602
    Los Angeles, CA, United States • 61°F
    11 Coins
    Tue, Dec 4, 2018 9:16am -08:00
  • Aaron Parecki
    at Terminal 6
    Los Angeles, California • Tue, December 4, 2018 9:16am
    33.942007 -118.402094
    Los Angeles, CA, United States • 61°F
    7 Coins
    Tue, Dec 4, 2018 9:16am -08:00
  • Aaron Parecki
    at TSA Pre Check Terminal 6
    Los Angeles, California • Tue, December 4, 2018 9:19am
    33.942173 -118.402162
    Los Angeles, CA, United States • 61°F
    10 Coins
    Tue, Dec 4, 2018 9:19am -08:00
  • Aaron Parecki
    at Alaska Lounge
    Los Angeles, California • Tue, December 4, 2018 9:26am
    33.941197 -118.401707
    Los Angeles, CA, United States • 62°F
    15 Coins
    Tue, Dec 4, 2018 9:26am -08:00
  • Eddie Hinkle https://eddiehinkle.com/   •   Dec 4
    Also, thinking through this a bit more deeply, obviously someone could get data into their json file anyway they wanted, but the easiest way for most people would be a Micropub app that just allows you to snap a photo and upload it without asking for all the normal Micropub stuff. We would need some way to inform the person's server that the post is intended to be a "story". One option would be to send something like channel: ['stories'] or you could make a specialized Micropub app like that have a config screen where you define what additional metadata it sends and then people could use whatever method they wanted, a channel property, a tag property, etc. I definitely don't think a new attribute would be right, and I know channel isn't really used anywhere except your and my sites, but we also can't do tag as a default or else the posts would automatically show up on people's websites as a normal post (unless they configured posts with a specific tag to be routed somewhere else). So this is tricky, but I definitely think something like this would be required for me to use it routinely. My default for my site would probably be to use a 'stories' channel and then to be able to set an audience on each photo/video so that some things I could provide to a subset of people.
    Aaron Parecki
    hm I don't think `channel` is the right terminology for this, also because stories exist completely outside of my own concept of channels.

    Maybe it's just a new `mp-` command in the request?

    Right now I have an iOS Workflow that just uploads a file to a specific endpoint. I guess that's the other way to handle it, create a new endpoint for it? Maybe the same endpoint that the story can be read from can also be POSTed to by the owner to create a story?
    Los Angeles, California • 62°F
    2 replies
    Tue, Dec 4, 2018 9:30am -08:00
  • Eddie Hinkle https://eddiehinkle.com/
    I went and started playing with instagram stories again. I see what you mean about mf2 (and even jf2) potentially being too heavy.
    Los Angeles, California • 62°F
    Tue, Dec 4, 2018 12:00pm -05:00 (liked on Tue, Dec 4, 2018 9:30am -08:00)
  • Los Angeles (LAX) to Chicago (ORD)
    December 4, 2018 from 11:45am (-0800) to 6:00pm (-0600)
    Alaska Airlines Flight 104
    Chicago Ohare Intl in Chicago
    permalink #okta
  • Aaron Parecki
    Contributions from: Japan, Russian Federation, United Kingdom, United States
    Tue, Dec 4, 2018 1:10pm -08:00
  • Plane
    1783.16mi
    Distance
    227:12
    Duration
    11:52am
    Start
    5:39pm
    End
    Chicago, Illinois • 31°F
    Tue, Dec 4, 2018 5:39pm -06:00
  • Aaron Parecki
    at Chicago O'Hare International Airport (ORD)
    Chicago, Illinois • Tue, December 4, 2018 5:42pm
    41.977072 -87.901182
    Chicago, IL, United States • 31°F
    16 Coins
    Tue, Dec 4, 2018 5:42pm -06:00
  • 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
    2 replies
    Tue, Dec 4, 2018 5:54pm -06:00
  • Lillian Karabaic https://twitter.com/anomalily
    "Why didn't you respond to my email?"
    "Well, I have received 1,419 emails in the past 72 hours. This is why."
    If I answered every email, I would not actually be able to do the work (writing/radio/etc) that makes me worth emailing.
    Chicago, Illinois • 31°F
    Tue, Dec 4, 2018 7:41pm +00:00 (liked on Tue, Dec 4, 2018 5:55pm -06:00)
  • Taxi
    5.25mi
    Distance
    8:32
    Duration
    6:22pm
    Start
    6:31pm
    End
    Schiller Park, Illinois • 30°F
    Tue, Dec 4, 2018 6:31pm -06:00
  • Aaron Parecki
    at Mantra
    Schiller Park, Illinois • Tue, December 4, 2018 6:33pm
    41.954677 -87.862729
    Schiller Park, IL, United States
    63 Coins
    Tue, Dec 4, 2018 6:33pm -06:00
  • Eddie Hinkle https://eddiehinkle.com/   •   Dec 4
    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.

    Aaron Parecki
    I guess I mainly post videos to my site that are already encoded either by Instagram or by my video editing software. But with stories it's usually straight from my camera.

    I think I'm on board with a separate endpoint as an initial experiment.

    I also just realized the reader is going to need a bit more information than I currently provide in that JSON. I'd want Monocle to show the author name and photo too of course. Not sure if that should be included in the endpoint response or if we should rely on h-card discovery from the page the endpoint was discovered from. In any case that's something the Microsub server will deal with, and it'll normalize that data for the reader app.
    Schiller Park, Illinois • 30°F
    Tue, Dec 4, 2018 8:15pm -06:00
  • Ruth [☕️ 👩🏻‍💻📚📖✍🏻🍵] https://glammr.us/@platypus

    Good evening, I have some thoughts that are kind of meta to the fediverse and apply into society more broadly. One public toot, then I'll thread 🔓

    So... I get torn between two principles & I think they're a reason why shared solutions like masto are so important.

    Principle 1: own your shit / pay for the shit you use

    Principle 2: there should be plenty of low-barrier & "free" spaces for people to congregate in some way.

    This is tied to my being a librarian tbh.

    Maywood, Illinois • 31°F
    Wed, Dec 5, 2018 12:40am +00:00 (liked on Tue, Dec 4, 2018 8:27pm -06:00)
  • Taxi
    17.47mi
    Distance
    31:07
    Duration
    8:10pm
    Start
    8:41pm
    End
    Chicago, Illinois • 32°F
    Tue, Dec 4, 2018 8:41pm -06:00
  • Aaron Parecki
    at Palmer House - A Hilton Hotel
    Chicago, Illinois • Tue, December 4, 2018 8:49pm
    41.880631 -87.62694
    Chicago, IL, United States • 32°F
    1 reply 13 Coins
    Tue, Dec 4, 2018 8:49pm -06:00
  • Aaron Parecki
    at Lockwood Restaurant and Bar
    Chicago, Illinois • Tue, December 4, 2018 9:24pm
    41.880582 -87.626955
    Chicago, IL, United States • 32°F
    42 Coins
    Tue, Dec 4, 2018 9:24pm -06:00
  • Cocktail
    Chicago, Illinois, USA • 31°F
    Tue, Dec 4, 2018 9:26pm -06:00
  • Aaron Parecki
    at Palmer House - A Hilton Hotel
    Chicago, Illinois • Tue, December 4, 2018 11:50pm
    41.880631 -87.62694
    Chicago, IL, United States • 31°F
    1 reply 2 Coins
    Tue, Dec 4, 2018 11:50pm -06:00
← Older → Newer

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