

Hmm, that’s not expected. This should only happen for users who don’t have a profile picture. Are you noticing this for all users?
In the example picture, neither of us actually have a profile picture, so it defaults to the first letter!
Hmm, that’s not expected. This should only happen for users who don’t have a profile picture. Are you noticing this for all users?
In the example picture, neither of us actually have a profile picture, so it defaults to the first letter!
Hey there, thanks for the report!
If you are able to submit a new GitHub issue for this, that would be helpful as it allows us to keep track of these easier.
Hey there, thanks for the report!
If you are able to submit a new GitHub issue for this, that would be helpful as it allows us to keep track of these easier.
Hey again! Thanks for the report - it would be helpful if you could submit this as an issue on GitHub so that we can track it better.
While I do try to keep track of issues and feature requests submitted here, it often gets lost if there’s no associated GitHub issue 😅
Hey there, thanks for the report!
This is a known issue and has been fixed (but not yet released) See here: https://github.com/thunder-app/thunder/pull/1738
Hey there! Thanks for the bug report.
It would be helpful if you could create a GitHub issue for this so that we can keep track of it!
Hey there!
The good news is that there’s no outstanding issues or technical limitations preventing this feature from bring implemented!
The main thing is allocating time to implement this in. I’m currently backed up working on some under-the-hood changes for the next version of Lemmy. Once that’s done, I’ll have more time to work on the existing feature requests.
Hey again!
From the very beginning, my goal with Thunder has been to make it highly customizable. Everyone has their own vision of the ideal experience, and I want Thunder to be flexible and feature-rich enough to make that possible.
Have you ever considered potentially incorporating some of the highly-praised UX elements, theming capabilities, and overall user experience from Sync for Lemmy into Thunder?
Thunder’s UX has been influenced by a number of apps, including Sync. That said, it was never meant to be a copy of another app. While I draw inspiration from many of the existing apps out there, my goal is for Thunder to stand out on its own. I know there’s always room for improvement, which is why I rely on community feedback to improve Thunder’s experience.
Given Thunder’s open-source ethos and active development, do you see an opportunity to potentially fill this gap by bringing some of Sync’s most loved features to Thunder, while maintaining your commitment to transparency and regular updates?
I do intend to keep building and improving Thunder while staying fully open-source. I don’t expect it to replace Sync, but rather to serve as a community-driven, open-source alternative for those who value transparency and open-source software.
That being said, development takes time. There are still many features I’d love to implement, but since Thunder is something I can only realistically work on in my free time, progress is naturally slower. Right now, there are only a couple of active maintainers (shoutout to @micahmo@programming.dev!) who work on Thunder. Additionally, I also have to balance feature development with moderating Thunder’s community spaces (e.g., Lemmy, GitHub, Matrix), which can complicate things further.
I’m not sure if this fully answers your questions, but I hope it does provide some insight on my general thoughts!
Hey there! Thanks for bringing this up.
Right now, I’m not sure if adding another communication channel (e.g., Discord) for Thunder would be useful. We currently have three different channels for different purposes:
Adding a Discord server (or something similar) would likely just increase the overhead for me, as I’d have to moderate yet another space. That being said, if there’s ever enough demand, I’d be open to creating one!
I believe so! Lemmy will try to generate a thumbnail from the link field whenever possible. You can try this by creating a post with a link and see what shows up after you make that post.
If you don’t see a thumbnail after creating the post, then it’s likely that Lemmy wasn’t able to automatically fetch the thumbnail for it. If this happens, you can specify a custom thumbnail for Lemmy to use using the Thumbnail URL field (as long as this points to a proper image)
The posts have images in their body of the text too.
You can have images within the body of the text, but Lemmy won’t use those images for the thumbnail (if I recall correctly) - it’ll only look at the URL field to determine what thumbnail to use.
Thanks for the kind words!
will be patiently watching for future updates. :)
If you’d like, you can keep an eye out on !thunder_nightly@lemmy.world for any nightly updates (these are updates that happen more frequently, but might contain some more bugs than usual)
Hey there! I just tested it myself and there might be some confusion here on how this works so I can explain a bit further. Feel free to let me know if you still have any other questions.
The thumbnail URL only works when you’re creating a link post (e.g., when the URL field is filled in). This is used when you want to show a different thumbnail image than the one that Lemmy fetches from the original link. If you try to fill in the thumbnail URL for a image or text post, it won’t end up doing anything (this might be where the confusion comes in).
If you want to create a post with an image, you can simply upload the image (the button beside the URL field) and Lemmy will automatically generate the thumbnail based on the image you uploaded. Hope this helps!
Thank you!
Hey there! For videos, there should generally be a back button at the top left of the screen that allows you to exit out of them.
If you’re not able to see it, then it might be a bug with tablet sized devices. Feel free to submit a new bug report on GitHub with some more details on how to reproduce the issue/screenshots so that we can track this easier!
Thanks for the feedback and for the kind words!
Would it be possible to make pinned posts all compact in card view?
I think that makes a lot of sense! If you’re able to, can you create a new GitHub issue for this? This allows us to track feature requests more easily. Thanks!
Hey there! Thanks for the feedback - I recently started to notice this as well so I’ve been putting more focus into improving overall performance and scrolling! This is still a big work in progress so it might take a while before all these improvements make it out into a release.
For a bit of background, most of my time developing Thunder has been through an iOS device (as that was the only device I had access to). On iOS, I would say the experience is generally pretty smooth. Only recently did I gain access to an Android device where I finally started to notice some of the stuttering that you’re mentioning.
Hey there!
Thanks for bringing this up - I’ve created a PR to handle this issue here: https://github.com/thunder-app/thunder/pull/1709. Feel free to take a look at the demo video in that PR and let me know if this is what you meant!
Hey there, thanks for the feedback! I agree that it would be useful to have a way to enable or disable keyword filters.
I would suggest creating a new GitHub issue on this so that we can track it better.
Thanks for mentioning this issue as well! This behaviour is generally intended for iOS devices since thats the primary way to navigate back.
I can disable the swipe gesture for this specific case on Android devices in the meantime, and perhaps add a setting which enables or disables this navigation gesture globally in the future (this would take a bit more time as there’s a lot of pages to consider)
Like the other issues, I would suggest creating a new GitHub issue so that we can track this better. Thanks!
Thanks for checking this!
If possible, I would suggest creating a new GitHub issue with some more details on the bug (e.g., instance, version, reproducible steps, etc.) This helps us better keep track of all the issues/feature requests so they don’t get lost.
I would also suggest creating a feature request for this on our GitHub!