Everything boils down to preferences, but Lemmy defaults is not necessarily keeping up with the trends. Small thumbnails were more useful back when internet traffic was slow and/or expensive, today it’s more of an acquired taste.

I wish different instances dared to have more different defaults, so that one instance would look significantly different from another beyond just colour scheme. I still haven’t seen a single instance run something like Alexandrite or Photon by default, and while I guess there are good reasons for that I think it would have been a welcome addition.

deleted by creator

In the case of Mastodon, I think an even bigger problem might have to do with age. Whenever I see an age poll on Mastodon it seems most of the user base there is older than the internet itself. It’s hardly surprising that they are not very up to date on pop culture. That it’s largely white and male of course adds to the problem.

It’s fascinating that when a social media is created without algorithmic boosting of content, pop culture suffers.

I guess it’s the kind of content we are very happy to consume, but we don’t care much about spreading. Had I seen a video of Lamar from the Superbowl boosted by one of the people I follow on Mastodon I would probably have watched it, but I wouldn’t have boosted it. I imagine some people would leave comments if they saw it, but that doesn’t affect visibility in Mastodon. The entertainment industry is geared towards a passive spreading of content, and that’s not what is happening on the Fediverse.

That might be a problem, it might be a good thing. But it’s at least not very surprising that the Fediverse looks very different during the super bowl.

Lemmy devs tend not to be very proactive when implementing interoperability with other fediverse services. I would expect support to pop up in Mbin and/or PieFed first, and possibly Lemmy later.

That said, I would be surprised if they were not aware of the possibility, I just doubt it’s a priority at the moment.

No doubt they’re taking their sweet time with it. Then again, knowing the Mastodon user base, whenever it is implemented people will probably go crazy and think it’s the biggest invasion of privacy since the gestapo.

By the way, here’s from Monday’s development update:

The team also made significant progress on the specification for Quote Posts. It needs a few minor changes, but we expect to publish it for comment in February, and start implementation right away. The current plan is to publish Mastodon 4.4 with support for displaying Quote Posts, and then add authoring in Mastodon 4.5.

Mastodon users can post to the Threadiverse by tagging a community, but since we don’t have “quoted boosts”/quote posts, there’s no way of including an existing thread or post when doing so.

For sure! But considering Mastodon has most of the content that would be quote posted this way and most of the users who would be subject to it, and they are working on it (at their own pace), I think it would be tactile to see how it is implemented in Mastodon first and then proceed from that.

It could for example be that Mastodon users will be able to opt out of quote posts in general or in specific posts. If so, this should be respected in other implementations as well. And in general, it’s just nice to have things consistent, and when it’s taking the Mastodon team so long to implement I suspect it’s because they’re devoted to making sure they do it right. :)

Hopefully whenever mastodon gets quote posts we’ll see something similar pop up over here.

I feel like this is part of what makes @fedify@hollo.social one of the most important fediverse projects at the moment - it aims to keep everyone from having to do the same, overly complicated job of activitypub integration over and over and over again.

It’s frustration that nobody wants to dig into old code, but I get frustrated having to re-work my own code from a year ago. So I guess I sympathize.

I think often people find it easier to write their own code than to make changes to other people’s projects, so it’s not necessarily very easy to change the Bluesky app to work with the Mastodon API rather than the Bluesky one.

That said, I don’t think it’s a dumb idea. Bluesky has a lot of money to pump into UX development, so making sure Mastodon users could benefit from this wouldn’t be a bad thing. Personally I am perfectly happy with the alternatives already out there (Phanpy is better than anything else that has ever existed), but it’s all about choice. :)