Alright should be fixed now, try again and let me know
Hmm, it’s working on my end and the SSL certificate is valid. Can you try the backup domain and see if it works for you?
Ah ok thanks, obviously you’re not the only one seeing this. I created a bug report for you guys and will get this fixed asap
@bappity@lemmy.world
This is not possible on the official Lemmy UI and as far as I know no third-party apps or clients support this either. What some third-party apps do support is hiding content based on keywords. If the content that annoys you has some words in common, maybe you could use those keywords in a third-party app to filter it that way?
Media is likely what’s taking up the most space. Pict-rs supports object storage, at the least that would be more cost-effective (usually around $4 per month for 250gb) than scaling up your machine’s disk space
Mastodon accounts automatically add the @
Cool, glad one of them was helpful!
Thanks, I totally agree—just added this to the roadmap for Lemmynade
Ah, I wasn’t fully understanding, I see what you’re saying now. There’s no way to know the number of comments on a single level/depth as of now without some extra fetching. I think your best bet at this point would be preloading the next page of comments on the top level, and if no comments are return you then know not to show the “load more” button.
Then, each time the next page of top-level comments is fetched, you can also fetch the children of each comment. This will prevent unwanted layout shift and ensure all children are fetched. If you don’t do this, I’ve noticed sometimes child comments go missing when I try to fetch multiple levels of comments in one request from a larger comment tree (100+ comments)
Lemmy is not very developed in this area. As far as I can tell, JWTs do not expire and there are no refresh tokens. I think instance admins can manually revoke JWT tokens globally, but otherwise they are valid indefinitely. I’m hoping this will be improved, because JWTs are already not the most secure—especially without ttls, 2fa, and refresh tokens
Yes—I'm working on a Lemmy client and seeing the same behavior. What is showing in the Lemmy web app UI is exactly what's being returned from Lemmy instances/servers at the moment. Trying to figure out how to display it better to users, but not a whole lot we can do about it right now.
This is fixed now. ✨