Hey there! Are you running v0.8.0-1? Just verifying to see if this is isolated to the nightly build.

Hi! This is a known issue with the nightly build. It should be fixed in the next nightly build.

Thanks for the report, this is likely due to some of the custom markdown logic related to subscript/superscript text. I’ll add this as an example into this GitHub issue

That’s the plan! PieFed-specific features will eventually be available to those with PieFed accounts, and the same will apply for Lemmy-specific features.

For the initial rollout, the main focus is just enabling PieFed compatibility.

Glad to hear that!

Thank you for all the support!

Hey! Unfortunately, I’m not able to reproduce this issue on my end after adding some filters and refreshing the feed page. Do you think you can give a more detailed step-by-step reproduction of this issue? For example:

• Added “xyz” to keyword filters through Settings -> Filters
• Navigate back to feed page and refresh feed
• See the following post show up on the feed (link to the post in question)

This should help me better reproduce the issue and figure out a fix for it!

See this comment for more information!

Right now, our focus is mainly on PieFed and Lemmy as they’re quite similar in nature. We may consider Mbin but that would be after PieFed support!

Thanks for the feature request! It would be helpful if you could submit this to our GitHub page so that we can better track this.

Hey there, I would suggest creating a new feature request for this issue with some additional information. This will help us keep track of this better!

Hey there!

Can you provide some more details on the issue? The filters should apply to URLs, post titles and the post body. If you could provide a step-by-step reproduction, that would be helpful (e.g., what filters are applied and what posts still show up regardless of the filters)

It would also be helpful if you could submit this issue on GitHub so that we can track it better!

Just a quick update - v0.7.2 should now be released which fixes this issue! Please let me know if you’re still encountering issues with this.

Just a quick update on this - I’ve released v0.7.2 which should improve this issue! Please let me know if you’re still seeing cases where information is pushed off the screen.

Thanks for the video! I think I understand the issue better now and should be able to reproduce it. I’ll keep you updated when the fix rolls out.

Hey there!

Could you open up a new GitHub issue on this and provide some more details/screenshots on the issue? Thanks!

Thanks for the bug report! As you mentioned in another comment, this issue tends to appear for users with longer usernames. There’s already an open issue tracking a similar overflow problem where the scores overlap with other information.

I’ve created a PR which applies some fixes such as limiting the width of the username if its too long. If you’re interested in the details or would like to provide some additional suggestions, you can check it out here: https://github.com/thunder-app/thunder/pull/1890

If everything looks good, this fix will likely land in the next minor release (0.7.2)!

Thank you for contributing towards localization!

I was able to reproduce the issue and will have a fix for this in the next version (which should hopefully be coming soon). For some additional information, here is the PR that resolves the issue!

Hey there!

Thanks for bringing this up. I do have plans to support PieFed in the future - I can’t promise when it will happen, but I’m working on laying down the groundwork to better support other APIs (whether it be Lemmy, PieFed, or possibly another platform that shows up in the future).

Doing this will take some time though, as Thunder’s internal logic was (and is currently still) heavily tied to Lemmy’s APIs. The good news is that the upcoming v0.7.0 release will bring us a step closer to this goal. My (optimistic) goal is to have basic support for PieFed and the upcoming Lemmy v1.0 API by the end of the year.

Hey!

If you’re specifically talking about marking private messages as read, you’ll have to use the latest nightly build (v0.7.0-1) in order to do it as it was just added recently.

If you’re running v0.6.1, it won’t be possible to mark an individual message as read unfortunately 😅