This is gonna sound silly, but in a best-effort attempt at making computers and the internet more accessible, I'd like to suggest making the alt text editor edit directly the image metadata ("notes" field), and then use the metadata as the alt field

What do y'all think? #a11y #accessibility

@BonfireBuilders #bonfire_feedback

On Code of Conducts ❤️ Image: archbudzar

Kinda unrelated and I don't want to see Twitter implement crowdfunding, but maybe we could define:

• features that Facebook, or Twitter, won't be able to implement, making their users migrate here,
• features that Facebook, or Twitter, will be forced to adopt, and
• features that improve our life experience (e.g. enabling mutual aid).

Hello? Is this thing on? Hello? Hey ho let’s go!

I have a suggestion for Bonfire:

@BonfireBuilders #bonfire_feedback

not sure if this a duplicate but:

reproduce:

1. scroll down down down the feed
2. click a post
3. go back to feed

expected:

1. be in the same place in the feed; maintaining context

actual:

1. be at the beginning of the feed; losing context

some preliminary feedback, in no particular order

• animations that happen on page change - talking specifically about the user mini-profile above the textbox and the buttons inside - are distracting and not on elements that attention should be drawn to. in the instance of the buttons, it just makes them unpleasantly blurry as long as the animation is playing.
• when the textbox is expanded, you're hit with a large portion of your screen on a light background, even in dark mode. personally, i'd re-theme the textbox as a whole to fit in with the dark theme better.
• when the textbox is expanded, the dropdown for the visibility of the post goes offscreen. conversely, when it's collapsed, the tooltips get clipped when expanding outside the column. not just that, when your post gets long enough, it just goes off-screen.
• typing into the expanded textbox feels quite unresponsive compared to the sidebar version.
• copy-pasting certain markdown syntax out of a text editor works, others don't - i've noticed headers work, but lists don't.
• CSS in the WYSIWYG text editor is inconsistent, most noticeable for lists such as this one
• the Share feedback button (which i just clicked) opens up a different post form, with: weird scrolling behavior for long posts, the tooltips still getting clipped when overflowing the column, and the visibility picker having the exact same text color as the background and ending up invisible.
• deleting a post gives three separate errors (popup before & after page refresh, inside column), but the post is deleted.
• searching seems incredibly buggy - clicking on a trending topic shows only a few posts & gets erased when switching category, searching on the top right yielded some better results (i think), but now that i've tried it again while writing this, it doesn't do anything
• lastly (for now), on the same page changes that trigger the bounce animation (inconsistent too, not good) erase your textbox, which is quite unfortunate.

some words of encouragement

i really like what you're going for here, from the conceptual level to the implementation so far - haven't looked too deep, but the tech stack seems good, especially the focus on serverside rendering.

i think modularity is useful in many applications, but specifically in the fediverse, i believe it to be extremely important. i'm not an activitypub user, but in my slight testing in the past, i've encountered incompatibilities between different applications. i'm hoping that bonfire with its modular approach can give instance owners or even users the tools to bridge the gaps in the protocol and the feature sets of different applications.

i'm also quite interested in zappa, and while i think some of the goals are quite a ways off (personal AI?), i believe the output can be quite useful to community managers, even outside of the fediverse community.

cheeky feature requests

• aforementioned retheming for the text box.
• different favicon for the playground compared to the blog, i can't tell which tabs are which while tabbing around right now
• turning off wysiwyg in the text editor, but with still working markdown

hope you enjoyed reading this post as much as i enjoyed writing it. sorry for the lack of capitalization, i'm too lazy to reach for the shift key

@BonfireBuilders #bonfire_feedback

Hey @BonfireBuilders - would it be possible to get an edit button/option for posts? I just made my #firstpost, and realized I needed to add something. #bonfire_feedback

Congratulations!! Welcome Aurora 🥰 🥰 🥰

hello bonfire

Today we learned that J., whom we have known for over three decades, has died of her own volition. The MS which had, over the last decade, confined her to a wheelchair and robbed her of most of her ability to move muscularly, finally diminished her experience of life to the point that it did not seem worth going on. She refused water and drink and any external aids to life... and she died.

We never knew J. well. She was a nodding acquaintance, albeit one who crossed paths with us on a regular basis, leading to a lot of nodding over the years. We don't have any profound observations to make about her character, about the course of her life, We knew that her marriage to S. had been difficult, that S. had behaved increasingly erratically over the years, and we'd heard rumors that he had moved out and further rumors that he had been institutionaized with dementia. All of this must have made J.'s life even harder than it would otherwise have been.

We can't say, given how slightly we knew J., that we will miss her (in any meanigful sense of that word). We can say that, as far as we could tell, she was a nice enough person. There will probably be moments in the years to come, walking through the entrance area of our building or through the park at the end of the street, that we will remember that she was once among us and note that she is no longer.

This may be a limitation of the current implementation. I've noticed when you a draft to post, if you navigate anywhere in the UI (click notifications from home), your draft post is cleared.

It would definitely be nice to have this persist in cache or at the very least float a pop up warning of losing your drafted content.

#bonfire_feedback

"It would be really exciting if making a Bonfire instance was as easy as setting up a Discord server or a Facebook group. I think it could make the platform more inclusive towards less digitally literate people."

That's why I was working on https://twitter.com/permanentcpu pre-covid

Prova

A few other text fields seem to have the same issue. Tapping any field with a font size of less than 16px on iOS causes the page to zoom in.