Hey! There’s currently no way to keep the taglines expanded but that can definitely be added as an option.

Thanks for the response and for the additional information! We’ve had some other users experiencing this issue as well (not always, but periodically) so I would like to get a fix out for this if possible.

I’m glad you’re having a good experience otherwise!

Thank you for the detailed response and for the additional information! As you mentioned and have likely seen, it’s been difficult for me to properly reproduce this issue on my end (given that I don’t have access to a physical Android device, and it seems to be working as expected on iOS devices)

I have just released a nightly build of Thunder v0.6.0-1 that might have a potential fix for the issue but I’ll have to confirm with others to see if the potential fix actually resolves the issue. If you are okay with running a nightly (and perhaps less stable build) of Thunder to test it, that would be greatly appreciated!

Side note: If you do plan to run the nightly build and are worried about losing your settings/information, you can always export the setting/database configuration and re-import it when you install a fresh version. This can be found under Settings -> General -> Import/Export Settings

Edit: This is the link to the nightly version: https://lemmy.world/post/21791907

Hey! This is likely due to some of the updates with our theming dependency that had some breaking changes which needed to be addressed. If you’re noticing any specific visual issues that are making it difficult to read, please open up a GitHub issue for it.

As noted in the post, we are aware of some of the visual issues present and will try to fix them (if possible) in the next nightly build!

Thanks for highlighting that feature, and I’m glad you find it useful! It’s a super simple addition, but one that adds some value to know how active a specific user has been.

If you do have any additional statistics you would like to see, feel free to create a feature request for it on our GitHub.

As a sidenote, I’m a bit concerned about your battery there 😰

Hey there! Just wanted to follow up on this - I’m trying to re-create the issue on my end to see if I can figure out the cause and fix it.

Unfortunately, I’m not able to re-create the error you’re describing. Could you let me know some more details on which particular posts/communities you’re experiencing problems with?

Also, does this issue happen when you’re creating a post or a comment?

Hey, thanks for mentioning this - I commented on a different post regarding cross-posts implementation that might be relevant: https://lemmy.world/comment/12719015

Thanks for the feature request - as others have mentioned, a workaround for this is to use your OS to limit app usage if your OS supports this. Also, it would be helpful if you could create a new feature request on GitHub so that we can track this easier. Thanks!

Just wanted to chime in here! I think the implementation of cross-posts is up for interpretation (and can definitely be changed if one is preferred over the other). Generally speaking, there are two types of implementations:

Cross-posts only copy over the title and link of the original post

• This is what Thunder currently does, unless it’s a text-only post (in which case, it copies over the text content of the original post since that’s the only relevant part of the post)
• The idea here is that we typically want to change the contents of the cross-post to be relevant to the community that we post to.

Cross-posts copy all content of the original post (title, link, body)

• This is what Lemmy UI does, but it injects “crossposted from” into the body of the post
• This can be useful if you want to post the same post across multiple-communities with the same body

From this discussion, I do think that it could be valuable to add an easier way to inject the original body of a post into a cross-post. If you would like this to be a feature, please create a new feature request on GitHub!

A side note on cross-posts:

I believe that Lemmy considers any posts with the same link as a cross-post. There’s no distinction (from the API) on which post was the “original” post, or whether a post was crossposted “from a community” vs “to a community”. This is also the reason why there is additional metadata for each “cross-post” in Thunder. The additional metadata allows you to figure out when a given post was created to find the “original” post.

If you’re curious about specific implementation detail, @micahmo@programming.dev might be able to answer them!

Thanks for the report, this is definitely a weird one. I’ve created a PR with a fix for this issue here: https://github.com/thunder-app/thunder/pull/1572!

For some additional context: Thunder automatically performs encoding on URLs. However, in this specific scenario, the URL was partially encoded (the brackets were encoded, but the non-ASCII characters were left behind). This partial encoding caused Thunder to incorrectly encode the already encoded brackets (%28 and %29)

Hey! Sorry for the delay in response. It would be helpful if you could create a new GitHub issue on this so that we can track it better.

This happens since about three or four Thunder updates have passed. Before that it worked fine.

Have you tried clearing app data/cache for Thunder? That might help “reset” things and might resolve the issues you’re facing.

Hey! Thanks for reporting this and sorry for the delay in response.

Unfortunately, its quite difficult to implement local-only notifications because of how restricitve Android is with regards to background tasks. The notifications feature is heavily dependent on the specific OS version that you have (different manufacturers do different things to help with power saving, but as a result, breaks/restricts background tasks from running)

The only thing I can suggest is to turn off battery optimizations for Thunder. After that, disable and re-enable notifications in the settings. If you go to Settings -> Debug, you should also see an option to test out notifications to see if Thunder can trigger them.

If none of that works, please let me know (ideally on Matrix) and I can help troubleshoot further!

Thank you for the kind words!

That’s interesting - could you submit a new issue on GitHub for this? Thanks!

Thanks for mentioning this, there will be a fix out for this shortly! This is the related PR: https://github.com/thunder-app/thunder/pull/1536

Just circling back to this - there was a potential fix for this issue in this PR: https://github.com/thunder-app/thunder/pull/1524

This potential fix was released in v0.5.0 of Thunder. If possible, please let me know if you’re still encountering this issue on the latest version. Thanks!

I know this was posted a while ago, but I do have an update on this issue. This bug was only affecting instances running on 0.19.4 and higher that had image proxying enabled (e.g., lemm.ee)

Fortunately, this issue should now be resolved with v0.5.0 of Thunder! If you’re interested in the details, check out the following GitHub discussion: https://github.com/thunder-app/thunder/issues/1448

Just providing a quick update on this - v0.5.0 fixes one of the two issues mentioned in the markdown report (table alignment not being respected)

The other markdown issue is not yet released, but should be fairly easy to fix! (just need to take some time to make sure the fix doesn’t break anything else). If all looks good there, then this fix will be released as part of a nightly build soon!

Thanks for the instructions. I’ve updated my information on GitHub to now include Monero as a viable option for those who would prefer that.

Though it still lacks the mod actions

Are you referring to mod actions for comments? If so, that is something I’ll be working on next!

and reports don’t have the name of the reporter.

For this, it would be good if you could submit a new feature request on GitHub to make it easier to track.