Aaron Parecki

Tuesday, February 13, 2018

• 
• 

  9:02pm

  Asleep

  4:35am

  Awake

  7h 33m

  Slept

  11m

  Awake for

  

  Portland, Oregon, USA

  Tue, Feb 13, 2018 4:35am -08:00
• $15k/mo running a productized service and step-by-step guide to start yours – Vinrob – Indie Hackers (www.indiehackers.com)

  Tue, Feb 13, 2018 5:27am -08:00 #business
• Bluetooth controlled Bescor MP-101 Pan Tilt Head modification - Mobile Modding (mobilemodding.info)

  Tue, Feb 13, 2018 8:08am -08:00 #ptz #video #arduino
• RSS Invaders: A novel approach to managing information overload in syndicated feed readers | C i b o M a h t o . c o m (www.cibomahto.com)

  Tue, Feb 13, 2018 9:03am -08:00 #rss #reader
• grantcodes https://github.com/grantcodes   •   Feb 13

  #19 Non https content
  

  That would be an interesting feature that the microsub server could provide to clients. It does seem like this will always be a problem.

  Portland, Oregon, USA

  Tue, Feb 13, 2018 9:07am -08:00 #microsub
• grantcodes https://github.com/grantcodes   •   Feb 13

  Working on implementing this in together now, I'm sure there is a valid reason, but I'm just wondering why the _id is different from the paging before and after values, could they not be the same?
  

  The before and after values are meant to represent pages of data, not necessarily individual records. In my case, the after value refers to an item that isn't in the current page. I could return a string for _id that looks more like the before and after strings, but that's just an implementation detail of my server. Alternately I may switch my before/after strings to look more like the current _id value. Either way, this difference doesn't seem important to the client.

  Portland, Oregon, USA

  Tue, Feb 13, 2018 2:52pm -08:00 #microsub
• 

  at StreamPDX

  Portland, Oregon • Tue, February 13, 2018 5:48pm

  45.542637 -122.661012

  

  Portland, OR, United States • 47°F

  38 Coins

  Tue, Feb 13, 2018 5:48pm -08:00
• https://micro.inessential.com/2018/02/13/say-youre-writing.html
  

  Here's the current recommendation: https://indieweb.org/h-feed#multiple_h-feeds_in_the_same_page
  
  tl;dr: use only the first h-feed unless there is a fragment identifier on the second
  
  fwiw I haven't actually encountered this case in the wild yet when I was writing all my h-feed consuming code

  Portland, Oregon, USA

  Tue, Feb 13, 2018 6:27pm -08:00
• jsorge https://micro.blog/jsorge   •   permalink

  @aaronpk @brentsimmons Thank you! Why would anyone put more than one feed on a page?
  

  I don't think they do, but gotta cover all the cases when you're writing code!

  Portland, Oregon • 41°F

  Tue, Feb 13, 2018 7:11pm -08:00