Gonna keep a running log of things about #bonfire that I hope get addressed in the future'
1
Discussion
Replies:
24
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
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
The second part is already acknowledged as an issue, at least: https://github.com/bonfire-networks/bonfire-app/issues/1769
#bonfire #bugburning
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
Both reported, finally:
https://github.com/bonfire-networks/bonfire-app/issues/1840
https://github.com/bonfire-networks/bonfire-app/issues/1841
bonfire-app#1840 should be patched in the next release, but 1841 is tougher, considering that other instance software is being inconsistent with how they handle CWs.
#bonfire #bugburning
1
It seems to be impossible to remove a profile photo or banner except by uploading a new one to replace them.
Reported: https://github.com/bonfire-networks/bonfire-app/issues/1842
#bonfire #bugburning
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
Reported and hopefully resolved: https://github.com/bonfire-networks/bonfire-app/issues/1833
#bonfire #bugburning
1
my instance has updated to alpha.34, but I suspect most of the issues above are still present
1
Speaking of which, certain remote activities from certain instance software do not render mentioned users properly. I've observed this in :
- WAFRN
- Iceshrimp
- Sharkey
(This probably applies to all Misskey derived software)
1
The image and video feeds seem to be completely broken on our instance
2
Wow, thought this server was a goner, now we're on 1.0.3.alpha-5!
Thank you admins (though I wish I could contact you out side of here...)
1
Can confirm bonfire-app#1840 is closed, yay.
1
A lot of new visual tweaks. Composer now opens as a full screen with the parent above, and all the post options are at the bottom of the screen.
I'm starting to narrow down the Heisenbug.
2
We're on 1.0.4-alpha-3 now. Visual styling is evolving, and the Groups extension plugs into Social pretty well, on first impression.
New:
- the fancy quick profile switcher has configuration in settings instead of being impossible to change
- We seem to be able to make polls and view other trending polls on fedi. Polls are also a content type you can make in the composer
- Oddly though, Articles are no longer a type in the composer.
1
The bottom bar on mobile now has labels for the buttons. Unfortunately the bar has the pesky overlay issue where it keeps getting in the way of other underlying views, and those views don't have any margin to scroll past for the bar to fit (I seen this on WAFRN web).
2
My initial experience trying to find this thread was quite unpleasant, because my instance somehow forgot the posts I had made??? So I had to go into another instance to pull the link to this thread from their cached activities. Ugh.
On that note, in a long thread like this, the (Show more activities) button does the opposite and shows less.
1
The Heisenbug (what I dub as Bonfire fucking up the navigation order when you click a post or comment from a feed and then go back) seems to be fixed? 🤞
Unfortunately the part when sometimes a reply replaces the parent in a thread is not 😔 #bonfire #bonfirealpha
1
Just remembered I have an account on the test instance, so I can actually tell what bugs are being fixed on live.
They seem to have fixed UI themes not actually saving at all, which alpha-3 on this instance has.
1
Still present seems to be an artifact of some redesigns between 1.0.0 and now: there are 3 separate UI blocks for the search page, which feels very redundant.
1
Also something I need to bring up: the composer needs better text editing and markdown management.
As I tried here campground.bonfire.cafe/pub/...,
by default the composer will escape the symbols put in for Markdown formatting, but there's no option to enable formatting for any particular string or post. Currently you have to post the draft as is, then edit out all the backslashes in the much smaller mini-composer. Also missing is any UI buttons to add that formatting in an easy way, or highlight to format with a mouse or touch.
1
Hmm, that's....interesting.
A bug that I wanted to report but got side tracked because of [bonfire-app#1936](https://github.com/bonfire-networks/bonfire-app/issues/1936) last release was sensitive images having a redundant reveal screen after revealing the content. When you click on "sensitive content" to reveal the image, and then click on the image to make it full screen, you get another "sensitive content" screen you have to click through, again. This produces a hide button on top of the image, which when clicked, reapplies the "sensitive content" screen, except now the button is on the top left corner instead of being centered. Very silly.
2
Speaking of which (Edit: both desktop and mobile), the sensitive warning block can be, uhm....scrolled away without clicking the reveal button.
1
