I’m pretty sure I’ve found these on Amazon before. It might be either a newer or older batch though? I’ve also seen clear top with beige housing, once inside a build they should behave identically. I understand if you’d rather not buy from Amazon though.

The idea of what content is "normal" at this point is the wrong way to look at it. The content feed is so slow across all but the most active communities on the most active instances, that treating them as though they've already carved out their niches is just incorrect.

This can be that, there's no reason it can't - it's just the tiny number of posts you're seeing don't have the same representation you might be used to seeing on e.g. /r/mechanicalkeyboards.

If you're just going to lurk and have no interest in posting you might as well just go to instagram and search for keyboard related tags. The content you post doesn't even need to be your own boards, it could just be stuff you like.

This is the biggest keyboard community in the Fediverse right now (but still very small). You can influence it a lot by just posting what you want to see. Boards you have, questions you have, GBs or whatever.

The downtime is causing an issue with posting content from other instances - I've seen this a handful of times from kbin. I post something to a lemmy.world community, and kbin thinks it's there, but lemmy.world doesn't see it. But, the delete request seems to need to go through lemmy.world, which doesn't agree that the content exists. So my profile is filled with posts people on kbin can see, but no one else can, and I can't delete them. Is there any kind of catch-up mechanic for instances to try to agree on what content should be present if content was altered during downtime? I can see this becoming a lot more confusing as people look at a community from multiple different instances and see different content, not realizing this is unintended behavior.

The biggest misconception I've seen on Reddit and elsewhere is that you need an account on every single instance if you want to interact with content on that instance, and it's not supposed to be true but while this bug continues, it kind of is true.