Gonna keep a running log of things about #bonfire that I hope get addressed in the future'
1
Discussion
Loading...
As of 1.0.2-alpha.21:
1
Unlisted should be part of the default Boundaries, if for nothing else but parity with other Fedi software
1
Markdown formatting seems to be escaped in arbitrary cases, but shows up (fails to show up really) when replying to remote users
1
The web app (the defacto client) refreshes at any opportunity it detects a loss of connectivity. This becomes a problem on mobile because Chromium breaks active connections if the screen turns off, focus switches to another tab for long enough, or the browser changes UI state doesn't reason. The mobile UX is constantly losing state, making it near unusable.
2
`Read more` shows up inconsistently on long posts in timeline view, forcing people to click through to see the rest.
The Vanity Metrics toggle seems to be broken on my instance, because it only counts replies and no other activities
Also annoying: the list of interactions (Liked by, Boosted by, etc) is not interactable or queryable
1
Critical: content warnings are not processed properly from certain software, leaving their content to be completely exposed. This has been observed in
- GoToSocial
- Akkoma
Also, content warnings also do not hide Quoted Activities, which leads to disaster with the trend of using quotes to add warnings to content that does not have warnings
1
~2 more replies (not shown)
It seems to be impossible to remove a profile photo or banner except by uploading a new one to replace them.
1
Heisenbug: clicking on an activity in a feed that's pulled from a thread has a chance of replacing the root post in a thread, rendering the thread incoherent.
The linked activity will show up fine in its thread position as well, though.
1
Bonfire processes Pixelfed hashtags as link cards as well as regular tags when it should only do the latter