That happens to me regularly. Plus it will have different read statuses in the channel list, pins, and notifications.

Physical controls were a primary reason I went with a 2023 Mazda 3. I didn’t want a touch screen as the primary input device. The rotary dials for menus and volume have been great. I find the screen is just in a better position too; it doesn’t need to be within reach so it just blends into the dash better and is at an easier angle to see.

Before I updated my car I used the headphone jack regularly for playing music there. Otherwise it was relegated to a couple situations a year like air travel.

Now that I’ve got a newer vehicle I just have all my music on USB there.

Less engagement is exactly what I would want. Show me my new chronological content and then I’ll get the hell out of there.

Not having a touch screen was a pretty sizeable component of my decision making process when I bought my 3.

https://www.youtube.com/watch?v=HLWY7fCXUwE

This is one of my favorite GDC talks and it’s about this subject with a sizeable segment devoted to the second paragraph in this article comparing Video Games to the availability of classic Movies.

The level of unity has been awesome. At first I thought this might only really spread through tech minded subreddits, but it really caught on broadly.

Feels very early. The site design needs quite a bit of work.

• The usual confusion on fediverse domain boundaries and usage. Seems very easy to accidentally route to another server rather than viewing that content within the current server (community/user links).
• Doesn’t retain sort/filter options on the home feed. I get that the default is local to promote some growth, but when I switch to subscribed I want it to stay that way.
• Excess visual space, cluttered design with avatars and community icons and excess padding. It falls into some of the traps that make me despise the reddit redesign.
• Strange prioritization of elements; visual emphasis on features that seem pretty niche or obvious (crosspost, tooltip text post preview, comment language, usernames), while more important elements get dwarfed or lost in the noise (timestamps, comment delineation + nesting).
• Live reloads are confusing and would be nice to be able to disable.
• There’s a real lack of dom class tagging that would make it easier for me to remedy some of those issues with custom css and the number of !important definitions doesn’t inspire confidence.
• Ultimately the above are all things that can be worked out. If the core systems work well enough then the design is something that can be augmented. I’ve had some navigation issues (including a page that wouldn’t load because it received a malformed json response from internal service), but the core functionality seems to be mostly there. Whether it’ll hold up to more load we’ll have to see.