It’s a visual bug. You should be subscribed.

Yeah, that sounds like a good solution. So if someone wanted everything except sports, they could get that.

Would you be interested in having different versions of this? I briefly scrolled the list of communities, and they seem very developer/tech-focused, which I suppose lemmy is. But I think it would be neat to have a tech/Linux/developer seeder, a humor seeder (memes, comics, funny, etc.), a sports seeder, a cute seeder (cats, puppies, animals, etc.), a gaming seeder, etc. Then the admin could decide what type of seeder they want instead of just getting everything, potentially with tons of things they aren’t interested in having on their instance.

I say this because I am interested in sports communities and don’t see enough of it, but the number one complaint I see on lemmy regarding content type is that there’s too much sports content. I moderate a sports community, but I wouldn’t feel right adding it to the seeder since so many people complain about seeing it.

Oh, that’s probably the app. So, the way Android does infinite scroll, it takes a lot of resources to create a “view” (the thing that holds the details of a post), so as you scroll, when a view goes off screen, it gets reused instead of destroying it and creating a new one. This is called a recycler view. When a view gets recycled, it is supposed to replace the details that are unique to each post (title, image, etc.) and keep any other detais (any text that might be common to all posts, any sub views like upvote and downvote, etc.). But if your logic isn’t right, sometimes something might get kept instead of replaced when the view is recycled.

I remember making this mistake the first time I used a recycler view back when I was working on my senior project in college, many years ago now. I don’t remember how I fixed it or the exact details around why it happened, but I know that I did fix it at one point.

Thank you for doing these regular updates. I find them very insightful. This is turning out to be a great release, and I’m very excited.

Is there a timeline for instance-agnostic linking to posts and comments? Link to GitHub issue tracking this.I moderate a small sports community, and the lack of this feature is really impacting the user experience. We have threads for each game, but we can’t sticky a post with links to the ongoing games. Or rather, we can, but anyone not on the same instance that the link is pointing to will not be logged in after clicking it, and can’t comment or interact at all with the thread.

I think this feature should be a candidate for the next major release, as it severely impacts new users who aren’t fully aware of how federated/instanced services work and that they are being redirected to another instance that may look the same but their account isn’t on.

I see three options for support. Do you know if the developers have a preference? For example, does any platform keep more or less of a percentage than any other.

Yes, this is exactly what I had trouble with. The Nvidia container runtime seems to not support my distro. But even when I tried running it on my Ubuntu machine, I was getting tons of dead links using Nvidia’s instructions. And even when I fixed the links. I was getting issues like the apt repository was throwing errors. IIRC, it was some kind of signature issue, and I’m not sure I want to ignore that, especially considering I had to fudge the URL.

I’m thinking the best option is to build from source, but I don’t think that’s easier than just running this in a non-container.

I’ll take a look at that later when I’m off work. I think not needing to modify my nginx config is ideal.

Uhhhh, I’ll need to double check that. I commented out the whole pictrs section in docker-compose.yml, then I commented out the depends on pictrs lines for the lemmy and lemmy-ui containers.

Honestly, I’m a little sick of needing to make a venv for each python script, which is why I’m trying to put all my python scripts in containers. I already got db0’s project to the point where anyone can run it with one single command line that you can just copy/paste (assuming you have docker installed already). It is just running on the CPU, which is painfully slow.

Running anything in a container isn’t necessary. It just makes it easier to run, as it comes with all the dependencies. And if you decide you don’t want it anymore, you can just remove the container and it and all its dependencies are gone, which is really clean. It also makes the environment extremely repeatable, so people on all distros can run it with the exact same steps. And you don’t need to worry about what version of python you have and if it’s compatible with the dependencies. For example, the dependencies for this script require python 3.10 exactly. You can’t use 3.9 or 3.11.

So really the only reason was I wanted to make it easier for everyone.

I set up mine manually using docker, and it gave me a site-wide error message when I simply completed our the pictrs container and dependencies. I made a post on !selfhosted@lemmy.world and someone suggested that I 404 it. I made that change, and now it works.

Oh, I see. I only use command line on my server, so I didn’t realize they were actual photos. Thanks!

I tried getting this to run in a container, but I was unable to access my GPU in the container. Does anyone have any tips on doing that?

It didn’t work that easily for me. I had to redirect all pictrs traffic to 404 in my nginx config.

'm an instance administrator, what the fuck do I do?

Check your pictrs images (good luck) or nuke it. Disable pictrs, restrict sign ups, or watch your database like a hawk. You can also delete your instance.

How? I have checked, and there doesn’t seem to be any way to see the photos on my server.

I actually shut down pictrs entirely on my instance. Running pictrs in its current state is criminally negligent imo.

The link worked fine for me on Voyager.

Well, that’s probably a problem with the bot, not Lemmy. You can probably report the issue to the bot creator.

Video is simply the most superior type of media there is, and I think that not having easy access to it on Lemmy is hurting it.

I could not possibly disagree with this more. If it has sound and no subtitles, it is easily the worst type of media for me.

I saw a few weeks back it was added then reverted in the git log. I wonder what the story is there.