Yes, my background is in „software as a product/service”. As such, I develop mostly for non-technical audience.

Since the testers here might reflect the audience you intend to reach, why not starting a poll with different variants of an error message and see, what resonates the best?

It seems that the uploaded images are not displayed well - they cannot be enlarged to their original size in the webUI, nor can they be opened in a new tab (that would be downloaded as a file).

測試中文

But why?

If I'm using a emoji picker and it behaves like this I wold fill a bug report.

Sinto que vou gostar bastante desse programa. Ainda tem uns cortes de papel, mas nada que realmente atrapalhe.

Frist post!!11eleven

It's a matter of opinion, but "technical errors should be logged, but not shown to people" seems to be a practice coming from software as a product/service, I wonder if that applies as much to "software as a tool"?

We've indeed seen and discussed that article 😊 It has some good suggestions though seems mostly focused on errrors related to user input (like in forms, which is something we could/should quite easily improve in Bonfire).

I'd also like feedback on how we could improve messages related to unexpected or general errors, such as due to or untested edge case. For example:

• You seem to have provided an incorrect data type (eg. an invalid ID)
• You seem to be referencing an invalid object ID, or trying to insert duplicated data
• The data provided caused an unexpected error and could do not be inserted or updated
• The data provided seems invalid and could not be inserted or updated
• Invalid arguments passed
• The function post/2 in module Posts didn't receive data in a format it can recognise
• A function didn't receive data in a format it could recognise
• A with condition didn't receive data in a format it could recognise
• A case condition didn't receive data in a format it could recognise
• A condition didn't receive data that matched a format it could recognise
• Could not complete this action
• Could not complete this request
• The app encountered an unexpected error
• An exceptional error caused the operation to stop
• An exceptional error was thrown
• An exceptional error occurred
• Something went wrong
• Oops, this resulted in something unexpected
• You need to log in first
• Not found
• You do not have permission to [...]
• We couldn't find an account with the details you provided
• This site is by invitation only
• This link or token has expired, please request a fresh one
• This link or token was already used, please request a fresh one if necessary
• This token was not found, please request a fresh one
• This user account is disabled. Please contact the instance administrator
• Please confirm your email address first
• Reset your password to login
• User not found
• Could not delete
• Bad request: malformed header
• Unknown resource

You'll notice many of these are similar, but because they for different reasons wording them differently helps us identify the problem when reported.

Duplicates playground.bonfire.cafe/coor...

I didn't see how to edit or delete units. Maybe the same for resource specifications? In the case of units, seems like delete is probably enough, easy to re-add, unless that messes up some internal key.

I filled out an offer, then uploaded a picture, after it uploaded, what I had filled out was gone, had to re-enter before saving offer.