• 3 Posts
  • 47 Comments
Joined 3 months ago
cake
Cake day: April 2nd, 2025

help-circle



  • In what way is the search function in Lemmy awkward to use,

    Generally, I find that it requires too many clicks.

    To search for things I’m usually interested in, I have to click a link to reach the search page, wait for the page to load, click a drop-down box, select and click a target type from the list (e.g. “Posts”), click a scope (usually “Subscribed”), click another drop-down box, select and and click a date range from the list, and then enter my search. That’s a lot of steps.

    (I could enter my search before selecting all those other things, of course, but it wouldn’t reduce the number of steps, and it would put extra load on the instance host by triggering multiple extra searches before the one that matters to me.)

    Also, in certain cases like searching for a community by ID, there’s a weird glitch where the search yields no results at first, but clicking the Search button again gets the expected results.

    is there anything specific that can be fixed?

    Yes, I think the user friction could be improved in several ways.

    I haven’t made a list of potential search improvements, but just off the top of my head, it would be convenient to have a simple search box in each community’s sidebar. Reddit had this back when I was using it, and it made checking for duplicates before submitting an article much more convenient than it is here.

    EDIT 2:

    It’s also inconvenient that the Community search field displays them in example.org/community format, rather than the normal !community@example.org format, and fails to recognize input in the latter format. The slash format might be a little easier to type for a minority of people who expect it, but it’s surprising by being unfamiliar to everyone else, confusing by introducing a second format for community links, and counterproductive by defeating copy/paste of a community link from someplace else.

    My suggestion for this would be to standardize on !community@example.org format, and allow omitting the ! on input. It’s a dedicated input field just for community searches, after all, so the software shouldn’t need users to lead with a bang in order to know we’re searching for a community. Side benefit: Since this format places the community name before the domain, users could simply start typing the community name without having to remember what domain hosts it, and they would see useful autocomplete suggestions right away.

    EDIT 1:

    Outside of search, the first thing I would suggest is making Lemmy readable without JavaScript. This would make it usable by people who disable scripts for security and privacy reasons*, and allow more search engines to index it, both of which would expand Lemmy’s reach and utility. And, since we’re talking about Lemmy as forum software for communities beyond the fediverse, this change would avoid imposing new requirements and vulnerabilities on communities whose web sites do not currently require JavaScript.

    *Note that this matters not only for someone’s home instance, which might be whitelisted for scripts, but also when following links to other instances, which is pretty common in my experience.


  • So I’ve been using rootless podman-compose

    when a new folder is created or an existing folder’s contents are modified, it seems to be setting the files and their folder’s owner to “52587”

    Rootless Docker and Podman run their applications within a user namespace. This means most of the user IDs within the container are mapped to a different uid range on the host, often called a subuid. It’s part of how “rootless” mode can allow an unprivileged user to run software that expects to have privileged IDs.

    https://github.com/containers/podman/blob/main/docs/tutorials/rootless_tutorial.md#etcsubuid-and-etcsubgid-configuration

    which does not exist.

    Are you sure it doesn’t exist? Have you looked at the ranges defined in /etc/subuid on the host?

    My first thought is that the uid numbers you see might be some of your host user’s subuids. If so, they will appear as different uids (perhaps with usernames) within the container. Try launching a shell within the container and examining the same files, to see what their owners appear as there.

    If this is what’s happening, it’s normal. As long as the software trying to access the files and the software creating the files are both in the same container, it should be fine. If it doesn’t work, there’s probably another problem in play.

    By the way, Podman almost certainly has a way to map certain container uids to host uids of your choice, which can be convenient when you want to share files between containers or between a container and the host.


  • I’m not aware of any such communities that run their forum on Lemmy.

    I think it could fit, although Lemmy’s design as a link aggregation site gives it some rough edges for the purpose we’re discussing. For example, the search functions are a bit awkward to use, there is no support for subtopics, and file upload support is (from what I’ve seen) very limited.

    On the other hand, Lemmy’s use of Markdown makes it more comfortable for text formatting than BBCode, which is the HTML-like markup used on many forums.



  • Another continual irritation:

    The widespread tendency for JavaScript developers to intercept built-in browser functionality and replace it with their own poor implementation, effectively breaking the user’s browser while on that site.

    And then there’s the vastly increased privacy & security attack surface exposed by JavaScript.

    It’s so bad that I am now very selective about which sites are allowed to run scripts. With few exceptions, a site that fails to work without JavaScript (and can’t be read in Firefox Reader View) gets quickly closed and forgotten.






  • As Lemmy is federated but not fully decentralised, continuation of communities hosted on a dead instance is not currently possible. (Compare this to Matrix, where a room can carry on even if its original homeserver dies, so long as at least one other homeserver participates in it.)

    So that is indeed still a problem here, although not as severe, because I think the posts in those communities will still be available on instances that participated in them. Such communities would be forever frozen, though; carrying on from where they left off would require migrating to (or creating) communities on still-running instances.

    Lemmy does allow you to export your own data and import it into another instance. That includes settings, subscriptions, and links to saved posts/comments. So I guess maybe you could save your own posts, export your data, and import it elsewhere to keep links to what you wrote on the dying instance. I have not tested this to be sure.


  • the amdgpu-pro drivers are only available on LTS releases and on a few selected distros

    Are you sure? I would expect AMD to have their own download & install instructions that could be used on any distro. That would be more work for you than just installing a package directly from your distro, of course.

    Curiously, I just found a comment from last year claiming that amf-amdgpu-pro now works with Mesa’s RADV. So maybe this approach could work without AMD’s proprietary driver?

    Mostly BluRay rips, so movies and TV-Shows

    By rips, do you mean your source media is already in a container, like a .mkv or .mp4 file? Or are you encoding directly from optical discs? If it’s the latter, then using a tool other than HandBrake for the encode might also require finding a disc ripping tool. (Not all encoding tools can decrypt and demux discs.)

    I actually was not. Is it any good? But Handbrake does not support that either, does it?

    I haven’t used Vulkan Video. It’s just an API, so I would expect the video quality to depend on your hardware’s encoder, just as it would with VAAPI or any other API.

    I don’t think Handbrake supports it yet, so until they do, I think you would have to use some other encoding tool.

    for anything involving multiple audio and subtitle streams and stream selection in general it is not an option for me…

    You haven’t said why, but if it’s just that managing lots of streams using command line tools is more hassle than you want to deal with, you might take a look at MKVToolNix. It’s pretty good at muxing, even if the source media is not a .mkv file.







  • I haven’t been following Reddit events since I left a couple years ago, but if there have been recent ban waves for bad behaviour, it wouldn’t surprise me to see corresponding upticks in it here.

    I wish more of us spoke up against rudeness, confidently incorrect ignorance, combativeness, tribalism, brigading, and other such stuff when it rears its head here. If all of us participated in moderation, I suspect it would be more effective and make our mods’ lives easier.