Tuesday, July 18th, 2023
🌟 New
- We’ve renamed the “Include stuff in your orbit” dashboard setting to “Include posts liked by the blogs you follow”. It still controls the same behavior: whether or not you’ll see posts liked by blogs you follow in your Following feed. Also, reminder that you can hide your own likes from this feature in your blog settings.
- On web, on the mobile layout of the site, we’ve shuffled the order of the items in the navigation drawer slightly.
🛠 Fixed
- We fixed an issue with the activity graph on web that could cause your browser to cache an outdated copy of the data. Now your browser should refresh with the latest data every time you visit that page.
🚧 Ongoing
- Nothing to report here today.
🌱 Upcoming
- Starting tomorrow (July 19th), some of you will see a new navigation layout for the desktop website that we’re experimenting with.
Experiencing an issue? File a Support Request and we’ll get back to you as soon as we can!
Want to share your feedback about something? Check out our Work in Progress blog and start a discussion with the community.
Hello, devs! I respect the idea behind the new layout (I assume the intent was for clarity, with the navigation links always visible and labelled), but sorry, the desktop site just looks ugly now. You’d think with the navigation now on the left instead of in a header, the dashboard would be more visible, but in practise, the dashboard feels so much more cluttered with Things To Look At, between the radar and the recommended stuff and so on, with just a tiny little area left for the actual dashboard content. A header with a row of icons is much more elegant. Are the icons so esoteric that new users might be confused by them? I really doubt it.
(Please don’t think this is a knee-jerk rejection of Twitter, either; even if it wasn’t circling the drain, I’ve always thought Twitter’s modern layout was also ugly, for all the above reasons. But I’m echoing everyone else that trying to court Twitter users by mimicking its layout and alienating your existing userbase is really not the way to go!)