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

Frist post!!11eleven

I wonder if anyone has analysed this topic from an intersectional feminist point of view, as "technical [details] should seen not heard" feels similar to what may [have been] said of women or servants...

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.

Why does it switch you into another flavour? It is confusing as someone who assumes they are doing one thing here, feels like we should stay in Upcycle. Or somehow automatically come back.

So far, the Solus installer stays on a Qwerty layout, but does perform the mkinitcpio hooks that turn the keyboard at the FDE password time into an alternative layout (e.g. Dvorak) on the second boot, which means that instead of not working on the first boot, it doesn’t on the later ones (which isn’t ideal if you use a YubiKey, or at all really).

As usual I’ve worked around this problem by setting a Qwerty layout at install time, and changing it after rebooting.

When I need to enter my password to unlock my session, the layout stays on Qwerty, which isn’t elegant… Because there’s FDE anyway, I’ll just try to remove this prompt.