Micro.blog

My new standing desk is finished! So excited to come back to this after next week's crazy travel! Check out the second photo for my super obsessive under-the-desk cable management! #standingdesk #flexispot #homeoffice #productivity #deskporn #cablemanagement aaronparecki.com

@eli It’s actually only half the pixels of a 4K display, so my 12” MacBook can drive it fine. It’s 3440x1440.

@eli Yeah that’s my main machine. I also have a 13” pro that I use for video editing and audio work. It handles final cut better than the 12” tho I can do video on the 12” in a pinch. It’s also nice to have a computer without all my normal distractions.

@amit My replies are all sent via webmention from my website, not created in micro.blog. I’m guessing that’s where the discrepancy is.

@eli Why have two monitors when you could just have one really really wide one instead!

@aaronpk that monitor is bananas

@aaronpk do you need to do anything special to push that many pixels?

@aaronpk is ther 12" MacBook your everyday driver?

@aaronpk very intriguing. Thanks for the lowdown. 😀

@aaronpk why should this conversation be all broken? I see Aaron’s replies first and @eli’s questions. 🤔 cc @manton

@amit Looks like it got confused about the timezone?

@aaronpk @amit dueling Portlands. Maine v Oregon

@amit Not only that, but @aaronpk’s initial post is shown as being 3 hours after his first reply to @eli!

I agree with Aaron that the time zones are wonky; at first, I thought it was ordering based on the literal local time and not accounting for UTC offset (since Aaron is in Portland, Oregon PDT/UTC-7 and Eli is in Portland, Maine EDT/UTC-4), but that doesn’t explain everything in this conversation, let alone in the full Timeline 😕🤔 /cc @manton

@smokey Guess number two is that more than one Micro.blog server has gotten its time or timezone out of whack.

@smokey @aaronpk @eli must be some feed then? I think as long as the timezone is taken care of in the feeds, it should not be an issue for the reader, especially if the responses originated at Micro.blog?

@aaronpk Yep that’s the issue. Your posts are still shown out of sync with current time.

@amit The fact that it’s also happening to replies, within a single conversation, leads me to believe that it’s something on Micro.blog itself, not a/the feeds (although in this case @aaronpk’s replies are posts on his site, which makes it less than a slam dunk hypothesis; however, the main Timeline…). That and the fact that many people’s posts in the main Timeline are sorting all out of order (and @Burk and @macgenie’s posts from this afternoon are still at the top of the Timeline, 6 hours later); I find it hard to believe that a whole bunch of people’s feeds on multiple platforms all went bad at once :-) It’s also possible that a bunch of people’s feeds on multiple platforms, including some, but not all, M.b-hosted microblogs, were bad already and a change on M.b just exposed the problem, but to me the simplest explanation is that something related to timezone handling in Micro.blog itself is broken right now ;-)

(This reminds me of attempting to figure out what was wrong with a website that wouldn’t work for a user in Camino when we had no access to the website in question…lots of shooting flaming arrows in the dark based on the limited information the user was providing us ;-) )

@smokey Yeah, possibly. Aaron’s post are fine in other feed readers.

@aaronpk Looking nice!!! 👍

@smokey @amit I haven't corrected the older replies yet, but I have this fixed for the future now. Sorry about the confusion it caused.

@manton 👍🏽👍🏽

@manton 👏👍🙏😃

It was disconcerting how disorienting it was for me—and really brought home how much of a “happy place” Micro.blog is, and when that is upside down, the whole world is spinning crooked! Thanks again for wrangling those timezones back into linearity!