I don’t think your comparison to Framework is justified since 1) they made a headphone jack expansion module that’s available along with all the other ports and 2) the Framework 16 has 6 expansion bays instead of 4. If you need a headphone jack you get a 25% increase in configurable ports, and if you don’t need one you get a 50% increase in ports. Plus, you can easily switch between those two cases.

I’m always frustrated when a game or service says to check out their Discord for information. Discord is a confusing mess of chat channels, and while it can certainly be useful in (near-)realtime interactions, I can’t imagine trying to look up longer-lived information, like what they’re trying to use it for. Make a forum, or a blog, or use a subreddit, but not Discord.

I think the most recent case of this was the game Terra Invicta, where I saw a tangential reference somewhere to some coming updates to the game, and a game rep said to check their Discord for more details. No thanks.

Adding more light rail wherever it makes sense is definitely a good plan (and should happen), but improving bus networks gives a lot more bang for the buck than focusing only on light rail. Features like off-board fare collection (paying at the bus stop, not on the vehicle), bus signal priority (extending greens and shortening reds as buses approach traffic lights), and dedicated bus lanes all improve the overall speed of buses and therefore the overall rider experience. Expanding the prevalence of these features should be a priority everywhere, particularly on higher-ridership routes.

“Artificial General Intelligence” (AGI) seems to be the new term for what used to be considered AI.

I’m sure they’ll move the goalposts once again whenever “AI” stops bringing in the money and the VCs/Wall Street get ridiculously focused on “AGI” startups and scammers.

What is Tiblur? There’s no explanation given in the post and the link is to a sign-in/amount creation page, also with no explanation.

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.

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.