Type of issue
Other (issue in content formatting, broken link or image, non-working widget)
Problem description
In the blog, a tooltip is used to render terminology explanations when content is viewed directly in a browser. But feed readers traditionally don’t support styles, and so the content is broken up by the <span class='terminology-tooltip'> elements’ content being shown mid-sentence. For instance, this paragraph in the 2026.11 release post
<p>Targets are a great way to keep your <span class='terminology'>automations<span class='terminology-tooltip'>Automations in Home Assistant allow you to automatically respond to things that happen in and around your home.<a class='terminology-link' href='/docs/automation/'> [Learn more]</a></span></span> and <span class='terminology'>scripts<span class='terminology-tooltip'>A script is a saved list of steps that runs when you start it, for example, from a dashboard, with Assist, or from an automation. Unlike an automation, a script has no triggers, so it doesn’t start by itself.<a class='terminology-link' href='/docs/script/'> [Learn more]</a></span></span> up to date. Point one at an <span class='terminology'>area<span class='terminology-tooltip'>An area in Home Assistant is a <a href="/docs/organizing/">logical grouping</a> of devices and entities that represents a room or space in your home, such as the living room, kitchen, or garage.<a class='terminology-link' href='/docs/organizing/areas/'> [Learn more]</a></span></span>, a <span class='terminology'>floor<span class='terminology-tooltip'>A floor in Home Assistant is a <a href="/docs/organizing/">logical grouping</a> of areas that are meant to match the physical floors in your home...
is basically unreadable in my feed reader (Tiny Tiny RSS):

Suggested solution
IDK what CMS the blog runs on, but it needs to render those terminology explanations in the feed in a way that doesn’t break the content, or not at all.
URL
https://www.home-assistant.io/atom.xml
Version
2026.11.0
How do you know the suggested solution is correct?
No response
Additional information
I’m re-reporting this; I posted #35042 two years ago, but it went ignored, and this is still an issue.
Using a supported version?
- I have searched open and closed issues for duplicates.
- I am using Signal-Desktop as provided by the Signal team, not a 3rd-party package.
Overall summary
I’ve set notes to self to disappear after 1 day. I chose one message to be pinned, was prompted to select the time to pin the message for, and selected 7 days. I was shown the message in the title.
I’m now unsure whether the message will be unpinned and removed after 1 day or 7 days. My guess would be 7 days, but either way, I think the message should make this explicit, or at least unambiguous wrt. which timer takes precedence.
Steps to reproduce
- set notes to self to disappear after 1 day
- send a note to yourself
- choose to pin the message
- select to pin the message for 7 days
Expected result
Any of these, in order of preference:
- ”This disappearing message will be unpinned and removed from the chat after 7 days.”
- ”This disappearing message will be unpinned and removed from the chat after 1 day.”
- ”Disappearing messages will be unpinned and the removed from the chat when the pinning timer expires.”
- ”Disappearing messages will be unpinned and the removed from the chat when the disappearance timer expires.”
Actual result
”Disappearing messages will be unpinned when their timer expires and the message is removed from the chat.”
Screenshots
No response
Signal version
8.7.0
Operating system
Ubuntu 24.04
Version of Signal on your phone
8.6
Checks
- I have read the FAQ section, searched the open issues, and still think this is a new bug.
Describe the bug you encountered:
After the app has been updated, the next time it’s opened it shows the changelog (version history).
(See #2852)
Describe what you expected to happen:
I expect opening the app to have it authenticate me to give me access to my passwords. The changelog is a needless detour.
I appreciate the work that goes into developing the app without seeing the changelog. I can find the changelog myself, should I feel the need to read it.
What version of Keepass2Android are you using?
1.12-r5
Which version of Android are you on?
15
I was initially going to report this as a bug, but then I realized I’m in the beta program, so the issue could be specific to that. The unprompted version history at startup is an irritating interruption to using the app, and I could leave the beta program, if I knew that doing so gets rid of the interruption. (I’ve had no other issues with the beta AFAICR.)
What version of Keepass2Android are you using?
1.12-r5
Ah, apparently ”Show content warnings” on the app is the opposite of what’s ”Always expand posts marked with content warnings” in the web UI. I was confused because the former refers to the warning, whereas the latter refers to the content. There may be minor usability issue there, but I’ll leave it out of this one.
Sorry for the noise. To make up for it, #290 looks like a duplicate of this one and thus could possibly also be closed.
Leveä lumipalle liikennevalonappipurnukoiden edessä tässä risteyksessä.

Hi @amyblais,
I could post this on the feature idea forum, but I can’t figure out how the signup on the site works. When I click on ”Create an account”, I get a prompt to verify my email address, and having done that, a page saying ”Go back to Production to finish logging in”. I don’t know what ”Production” is, and at no point was there any actual way to set up a password, so I can’t log in.
Summary
A ”Mark read” choice in push notifications about new messages, as seen in many IM apps, would be handy in Mattermost Mobile too. Currently the message can only be marked read by tapping the message to open the app (which is slow).
Environment Information
- Device Name: Samsung Galaxy A9
- OS Version: Android 10
- Mattermost App Version: 2.11.0
- Mattermost Server Version: 9.3.0
Steps to reproduce
- Receive a message notification on the Android app.
- Pull down the notifications.
- Expand the received notification.
Expected behavior
Have a ”Mark read” option underneath the expanded notification.
Observed behavior
No ”Mark read” option, only ”Reply”.
I was on my Android device, saving URLs pointing to individual comments in threads at Ubiquiti’s Unifi forums, but later returning to them on my desktop realized that the hash (fragment) portion had been dropped, so that the URLs only pointed to the opening post. Hence, just one link (pointing to the first post) had been saved. This is pretty useless for threads spanning multiple pages, where finding an individual comment is tough without the exact link.
Here’s a (random) example of a URL pointing to the second comment on the third page of one thread. Sharing it from any of Android, iPhone or desktop results in a link pointing to the first post instead.
Näyttää selaimessa vanhaa selkeämmältä ja paremmalta, mutta tästä puuttuu reseptiyhteenvedon tulostaminen, joka on yksi minulle tärkeimmistä toiminnoista vanhassa (ruukaan tulostaa yhteenvedon PDF-tiedostoon, jotta voin tarkistaa jäljellä olleet määrät ilman, että tarvitsee kirjautua). Se ei haittaisi, jos tämä uuden näkymä olisi tällaisenaan nätisti tulostuva, mutta tässä ei ilmeisesti ole tulostusta ajateltu vielä ollenkaan, vaan tulosteeseen tulee valikkoa ja muuta turhaa roskaa.