Or the comment sections could just be merged together in the client view. Each thread of comments would belong to one (and only one) instance, so it shouldn’t be difficult to merge those lists together when presenting the aggregate view to the user.

That’s unfortunate.

Instead of requiring an insurance selection or defaulting to one specific instance, perhaps they could have a handful of moderate/large instances that the app randomly selects between when a user signs up. That would spread out the signups from people who don’t understand the instances.

We could always move Veteran’s Day to September but then establish Armistice Day on 11 November, which is what the rest of the world calls that day. Net result would be one more federal holiday (just with some renaming).

Or, we could mess things up by leaving Labor Day and Veteran’s Day alone and adding “Armistice Day” in May. :)

It would be very beneficial to have clients that support aggregating equivalent communities from multiple instances. When viewing a post from the aggregated community there could be a section at the top saying “Viewing comments from:” and then a dropdown to choose between “all instances”, “lemmy.world”, “lemmy.ml”, etc. When viewing all comments, they would be in one combined feed, without the user needing to care about which underlying post holds the specific thread they’re looking at.

Similarly, when users post something to an aggregate community, they could select whether it’s posted to all the included communities, only one, or some specific subset.

I freaking hate Shorts, and the persistence with which YouTube attempts to shove that crap down your throat is absolutely infuriating.

YouTube also recently made the thumbnails larger, which is also really bad as it makes it more difficult to see what videos are in your subscription feed (even moreso with all the shorts clogging it up).