mild_deviation

That one might have in the shower

Eh, if you're mostly just consuming/lurking, it's probably better to use Lemmy by viewing all posts on all communities on all instances, then filtering out the communities you don't like. Gonna be like that until it gets more popular, and importantly, stops becoming less popular.

Even on a slow connection, if you've clicked the link, you're there to view the post. The image simply must be visible by default. It would be more interesting to allow clients to choose what image quality to load, but I don't know a good way to do that. Maybe default to low quality, then you can choose high quality after logging in?

Since when do bats speak in monospace?

I feel like most of them haven't used C# in the last decade, let alone .NET since Core.

The misconceptions that persist to this day despite over half a decade of .NET Core are mind-boggling. MS has a steep hill to climb.

I don't like Reddit's approach. It hides nearly all information about the post. You don't get to see the number of upvotes or comments, and you can only see as much of the title as fits on a single line.

I'd rather the image post viewer default to an expanded state, and have a clearer delineation between the image and comments. Right now, there's not even a header saying "Comments". You're expected to just know.

Nice, thanks for the link. That link is about the posting side, whereas I was talking only about the viewing side (apparently covered in issue 808), but the posting side is arguably even more important in reducing fragmentation. Just as it's frustrating to group N communities for viewing, it's equally frustrating to post to N communities, and then have to interact with them separately.

Linking to Lemmy image posts is a bad experience. This use case needs to be much better because content is the main way that non-Lemmy users can be motivated to join Lemmy. I tried to share this with a friend yesterday, and had to explain that the image I actually wanted them to see is locked behind a tiny thumbnail, and that the full size Good Place Janet someone commented is not what I wanted them to see (at least not without the context of the posted image).

There's no way to open a shared Lemmy link in your client of choice. You can manually add URLs on Android, but you have to do that for every Lemmy instance, so that's not going to fly. I don't know if there's any solution at all on iOS.

There's not a good way to control what content I see. It's essentially either "everything" or "a single community". On Reddit, you could already have multiple communities about the same topic on Reddit, but usually one was dominant, and you had multireddits to save you if there truly are a few good related subreddits. Now on Lemmy, you multiply that problem by N instances, and subtract the multireddit feature. This situation simply must be made better somehow.

GitHub recently got merge queues. I desperately want something like it for AzDops.

YouTube is a business with a clearly-defined business model, precisely-tracked direct metrics, and automation up the wazoo. Not a government taking taxes and dealing with human elements for which there are very few direct metrics. They can pay creators based on watch hours or some other usage metric.