#Tag
I would highly recommend any techbro (and any developer) to spend some time on slow, laggy or even cutting out internet. So just they can see how their always-online web apps plainly crash when unable to cope with a short offline time. Absolute tragic #UX, loss of data common!
#webdev #usability #accessibility #a11y #web
I would highly recommend any techbro (and any developer) to spend some time on slow, laggy or even cutting out internet. So just they can see how their always-online web apps plainly crash when unable to cope with a short offline time. Absolute tragic #UX, loss of data common!
#webdev #usability #accessibility #a11y #web
#NoScript 13.5 is out, with many user experience improvements!
The most visible:
- new "cascade permissions" mode
- the onboarding / site classification behavior panel (in the picture)
- many #usability and #security enhancements regarding blocked content and click-to-play
The greatest thanks(giving) to the Open Technology Fund #otf for strenuously supporting NoScript during the past 2 years, especially through the Manifest V3 compatibility ordeal.
#NoScript 13.5 is out, with many user experience improvements!
The most visible:
- new "cascade permissions" mode
- the onboarding / site classification behavior panel (in the picture)
- many #usability and #security enhancements regarding blocked content and click-to-play
The greatest thanks(giving) to the Open Technology Fund #otf for strenuously supporting NoScript during the past 2 years, especially through the Manifest V3 compatibility ordeal.
To the user-interface designers and programmers out there: If the unfortunate event happens and you have to show an error message, please make sure the message is actually helpful for identifying the issue. You might think that hiding technical details is user-friendly, but in fact, the opposite is true. Do not make us guess what is wrong, tell us what you know!
You might be afraid that this confuses users who are less tech-savvy. Not necessarily, if you give them a rough idea first (maybe in a more emphasized font) and then continue with the details you have (maybe in a smaller font). I am quite sure users are able to ignore the parts they do not understand, and if they need support, at least the person giving support has something to work with.
Some simple examples:
❌ "Cannot connect to bluetooth device."
❓ "Okay, but why?"
✅ "Cannot connect to bluetooth device 'foo' (maybe it is turned off?): The device does not respond."
❌ "Cannot open file."
❓ "Which file? And again, why?"
✅ "Cannot open file 'testfile.txt' for reading: Permission denied"
❌ "Something went wrong when trying to load the website."
❓ "Again, what's the problem? Is the network interface down? Is the DNS server down? Is the target server itself down? Give me a hint, please!"
✅ "Cannot load the website. Maybe your computer is not connected to the Internet? Details: No route to host (192.168.10.1) when attempting to connect to the DNS server."
This is nothing new. In fact, it is just an adaptation of the top-down writing approach we also use when writing scientific papers, for example: You begin with a rough overview and give increasingly more details later in the text.
But do not omit the details completely!
#usability #userinterfaces #userinterfacedesign #errormessages #programming #writing #technicalwriting
PLEASE SHARE
Are you an #OpenSource project? Would you like to make your website (or web app?) easier to use?
I teach a university course on #usability testing, and I'm looking for clients to work with in spring semester. I'd love to help an open source project.
Timeframe is early March until early May, and you get a detailed report that tells you what's easy, what's hard, and what to improve. And it's FREE.
Interested? Email me so we can talk about details:
jhall @ freedos . org
PLEASE SHARE
Are you an #OpenSource project? Would you like to make your website (or web app?) easier to use?
I teach a university course on #usability testing, and I'm looking for clients to work with in spring semester. I'd love to help an open source project.
Timeframe is early March until early May, and you get a detailed report that tells you what's easy, what's hard, and what to improve. And it's FREE.
Interested? Email me so we can talk about details:
jhall @ freedos . org
To the user-interface designers and programmers out there: If the unfortunate event happens and you have to show an error message, please make sure the message is actually helpful for identifying the issue. You might think that hiding technical details is user-friendly, but in fact, the opposite is true. Do not make us guess what is wrong, tell us what you know!
You might be afraid that this confuses users who are less tech-savvy. Not necessarily, if you give them a rough idea first (maybe in a more emphasized font) and then continue with the details you have (maybe in a smaller font). I am quite sure users are able to ignore the parts they do not understand, and if they need support, at least the person giving support has something to work with.
Some simple examples:
❌ "Cannot connect to bluetooth device."
❓ "Okay, but why?"
✅ "Cannot connect to bluetooth device 'foo' (maybe it is turned off?): The device does not respond."
❌ "Cannot open file."
❓ "Which file? And again, why?"
✅ "Cannot open file 'testfile.txt' for reading: Permission denied"
❌ "Something went wrong when trying to load the website."
❓ "Again, what's the problem? Is the network interface down? Is the DNS server down? Is the target server itself down? Give me a hint, please!"
✅ "Cannot load the website. Maybe your computer is not connected to the Internet? Details: No route to host (192.168.10.1) when attempting to connect to the DNS server."
This is nothing new. In fact, it is just an adaptation of the top-down writing approach we also use when writing scientific papers, for example: You begin with a rough overview and give increasingly more details later in the text.
But do not omit the details completely!
#usability #userinterfaces #userinterfacedesign #errormessages #programming #writing #technicalwriting
Oh, why am I spending my morning looking through the source code of a Chrom(ium) extension that clicks OK buttons repeatedly, you ask?
Because I have about 1,000 transactions from Stripe from our Gaza Verified Emergency Appeal to reconcile in Xero and apparently the galaxy brains at Big Business, Inc., think that making you click a button 1,000 times is just fine, actually.
Fucking capitalists can’t even do capitalism right.
*smdh*
#xero #capitalism #usability #design #BigTech #business #accounting #money #bullshit
Laptop Support and Usability (LSU): May 2025 report from the FreeBSD Foundation
<https://github.com/FreeBSDFoundation/proj-laptop/blob/main/monthly-updates/2025-05.md>
– via <https://www.reddit.com/r/freebsd/comments/1l5amd4/>
#FreeBSD#Foundation#LSU #laptop #support #usability#KDE#Plasma #installer
Solving a 17 years old issue of #Thunderbird by exposing the default sorting and threading options in the settings, and allowing a quick "Apply to all" button (or choose folders separately).
Soon, on a daily release near you...
#UX #usability
A space for Bonfire maintainers and contributors to communicate
![Screenshot detail of code:
function match_statement(matched, statement){
//get reference id from xero
var id_set = null;
var set_spans = matched.querySelectorAll('.c0 .details span');
if(set_spans.length > 0){
var i;
for(i=0; i < set_spans.length; i++) {
if(id_set=set_spans[i].textContent.match(id_set_regex)){
id_set = id_set[1];
if(id_set){break;}
}
}
}
if(!id_set){return false;}
var id_rec = null;
var rec_spans = statement.querySelectorAll(".statement.no-shadow div.info div.line-details span");
if(rec_spans.length > 0) {
…](https://s3-eu-central-1.amazonaws.com/mastodon-aral/media_attachments/files/115/411/534/257/780/940/original/1bf9420c2174d024.png)
