Lemmy shouldn’t have avatars, banners, or bios

  • 0 Posts
  • 18 Comments
Joined 1 year ago
cake
Cake day: July 3rd, 2023

help-circle



  • The browser solves the problem of not having any open API. Each platform wants to handle things in its own way, and the browser is the perfect way to do that. Each service, including both the open and the proprietary ones, can present the feed in the way that they decide is right. The browser already does handle rudimentary account management via form auto fill, as well as a unified notification system.

    But as for a unified feed… I think the best example is the issues with that come from Lemmy/Mastodon integration. Mastodon posts have a different mentality than Lemmy posts do, not to mention with structure of responses. I just don’t think it does us any favors to have them share the same feed. Now we have replies that have a clear structure of who they are responding to, but Mastodon users come in adding the user tag into the comment, which is messy at best, and bordering obnoxious at worst.

    But I get it, I’m not the audience you’re looking to cater to. I don’t particularly understand the value of RSS readers at all, because I just go directly to the services I want to see the feeds from. Hell, I don’t even use bookmarks. I type in the web address for my services every time






  • From my limited perspective, it seems like the community wants mod support, but they were mad about some combination of these things:

    • Updates and hot fixes don’t come quickly enough
    • Updates sometimes break a large number of existing mods
    • Not enough new features or explicit support for certain mod features being promised
    • Things they promised not working as well as people hoped

    This isn’t everything, but it’s what I observed for myself. As you can see, there’s some contradiction here, and some of that comes from different people in the community, and some of it comes from people who just want to be mad at everything

    For whatever it’s worth, most people seem to be just enjoying the game and are excited for anything new coming for it.




  • I think there should be tags for communities and separately, tags for posts within a community.

    But I am thinking of Reddit’s style of tags, where they are not used like Mastodon, they are just used to identify a general topic or classification of a post within a community.

    The idea would be to give end users more information they can use to filter posts or communities, rather than to help people discover posts.


  • A couple of main points:

    • You are reading tutorials to help you get it up and running. Most of the time these are designed to walk you through setting things up on a fresh node, and most often just VMs on an isolated (trusted) network. When you are providing a guide to just get someone up and running, the first thing to do is establish a known baseline configuration to start from.
    • Kubernetes is a complex distributed application, and as such, the audience is generally expected to be relatively experienced. Meaning if you don’t know how to configure your firewall, people assume you aren’t going through this tutorial.

    Still, I feel your pain. When trying to get into these technologies, most people who have done the work are engineers, and we stink at writing documentation. I’m sure you’re familiar with it, we automate the solutions for issues we encounter, and then those tools or automatic configurations fail to make it to the end user.

    And I’m probably biased, but don’t use a video guide for this sort of thing. It’s just the wrong medium for a technical tutorial.