This has be fixed in the library, so should work with the next update.

@vera a link preview is supposed to appear, it wasn't in this case because of the absence of opengraph/oembed/etc tags, but that will be fixed in the next update

#BonfireFeedback If you're going to truncate link urls grab page title and interpolate into status. Currently the length is too long to be "pretty" and too short to be useful.

First meeting of anagora.org/coop-cloud-feder... today

Also just changed 'bug' to 'UX'

I've just filed a bug for what might seem like the world's most trivial thing @ivan

github.com/bonfire-networks/...

However, I think that having a delay from clicking the star icon to it turning yellow is likely to lead to frustration and/or people repeatedly clicking it because it "hasn't worked".

(you know when the UX 'bugs' are getting this specific that you're doing something right overall!)

(you know(you know when

Any feedback on this?
github.com/bonfire-networks/...

campground.bonfire.cafe/post... not showing space between mention and message #BonfireFeedback

@Oceane thanks a lot for reporting this

#bonfire_feedback hashtags beginning just after a typographic character aren't interpreted, made clickable, or indexed

Ok, it doesn't seem to work?

|#Interpol #Anarchists|
«#Marvel #CIA #propaganda #pacifism»
|#Commune|
«#AxiologicDispositions»
"#GuyDebord"
"#Web #SpectacleSociety"

I'd like to check if hashtags work properly here (#Zuckerberg #CIA #Erdogan #WhatsApp #Signal #ChatControl #Nebraska).

Filed an issue: github.com/RobertDober/earma...

The new release includes among other things:

• 🎨 improved themes consistency and a11y
• 📱 improved mobile responsive
• The layout has been adapted to the latest mockups in preparation for groups and topics (it may feels a bit weird ATM to have the left sidebar emptier than before, but it will be filled with groups and topics 🙃
• several bugfixing ( you can follow this milestone for more details github.com/bonfire-networks/... )

@Oceane it seems that it works only
if the striked text is on a seperate line
The markdown processing library we use has a few bugs like this, we'll need to either compile a list and try to contribute fixes, or maybe use a different one.

#bonfire_feedback ^ no strikethrough?

I'd like to make a joke about the FSF making a browser preventing you from collaborating loading non-free Javascript but it wouldn't be funny because it's true