Thunder App

2794 readers

1 users here now

An open-source, cross-platform Lemmy client for iOS and Android.

This community is intended to discuss features and feature suggestions for Thunder; as well as friendly, respectful talks about Lemmy in general.

Please use the GitHub repository linked below to submit bug reports, so keeping track of them is easier, and make sure to search first if you already can find an issue for your report.

If there are any developers who would like to contribute, feel free to reach out on GitHub!

General Links
Website: Link
GitHub Repository: Link
Matrix Space: Link

Android Releases
IzzyOnDroid: Link
Google Play: Link

iOS Releases
Apple App Store: Link
TestFlight Beta: Link

Related Communities
Nightly Community: Link

founded 1 year ago

MODERATORS

[email protected]

The body of comments that are just text within angle brackets do not render (lemmy.world)

submitted 4 months ago by [email protected] to c/[email protected]

12 comments fedilink hide all child comments

In this example, some commenters are joking around and placing angle brackets (less than, greater than) around their comment's text. As a result, the comment text does not display.

It does display in a web browser or Voyager. Raccoon also does not render the comments, though strangely it does render that last comment in the chain. Perhaps it has something to do with the fact that the comment includes an apostrophe and comma, unlike the others.

top 12 comments

sorted by: hot top controversial new old

[–] [email protected] 3 points 4 months ago

Please refrain from posting bug reports to this community. You should instead post them to the official bug tracker.

[–] [email protected] 2 points 4 months ago

<te,st>

[–] [email protected] 2 points 4 months ago (1 children)

[–] [email protected] 2 points 4 months ago

This one (<test>) does not display

[–] [email protected] 2 points 4 months ago

Sorry for the late reply, and thanks for mentioning this. As others have mentioned, it would be great if you could make a new bug report on GitHub for this issue! It makes it easier to track and ensures that it doesn’t get lost/forgotten.

This is a bit technical, but as for why this may be happening, it seems like it might be trying to parse an HTML tag when rendering to text. HTML tags usually use < and /> to indicate the tags, which seems to be similar to the cases you’ve pointed out.