The reason they rolled their own was because it came out before the Double-Ratchet/Axolotl protocol and OtR (which double-ratchet is essentially based on) was extremely inconvenient to use properly and had its own weaknesses.
this actually makes a lot of sense lowkey, thanks :)
it's suspicious, but at the same time, iirc, nobody's been able to find a vulnerability in their encryption protocol :shrug
Aside from that, which distro would you choose for Coolify? I’m debating between Ubuntu 24.04 and Debian 13.
is it a honeypot? also did ovh change prices recently? I remember checking a couple years ago and it was more expensive vs hetzner
On an unrelated note, I found this "small phone" kickstarter project: https://www.ikkoaudio.com/products/mind-one-phone
But what is really preventing me from buying one of these is lack of AOSP support. I want to run GrapheneOS or CalyxOS or postmarketOS, so if it can't do that it's off the table for me. I wish there was a way to sponsor the reverse engineering of a single phone's drivers.
Android is every bit as bad as iOS. Windows is as bad as MacOS, and Linux is as bad as either of them.
And it’s not just older folks. I routinely run into problems explaining technology to relatively younger folks; even highly educated ones.
I’ll bet that the author would have been just as frustrated, teaching Android to a room full of doctors and lawyers.
My doctor just sold his practice to NYU Langone, a very good organization (and he got lots of money, I’m sure). They installed a really intense (and expensive) IT setup in his office. I’ve been watching him and his staff, struggling with it. It’s actually an excellent system, and I’m sure that many folks here, would be proud of it, but they still struggle. He has a full-time staff member, supplied by Langone, whose only job, is to come in and help staff use the IT services. She’s very busy (and patient).
I feel like Accessibility needs to include discoverability, affordance, and usability, as principal axes.
The terminology we use, the words we pick, in user interface and feedback are vital. The design of affordances, the placement of UI elements, etc.
Glossaries are really important, and I watch people’s eyes glaze over, when I start talking about them. You can have Design Language glossaries; not just text ones.
It’s a huge topic, and not a particularly popular one.
I feel that a good start, is highlighting examples of products that get it right, with discussion on how they do it. I get pretty tired of everyone complaining about the failures. That’s just discouraging, and tends to get people circling their wagons. I think good examples would be very helpful.
I’ll start. My wife likes OXO kitchen gadgets a lot. So do I. She tends to buy stuff that I’d never get, if I were making the decision, but I find really good, once I start using it.
if you don't modify your library, app, OS, etc for 2 years, it's perceived as abandoned or obsolete, meaning even if you're achieved perfection in your product in terms of ui, you can't stay there, you must move forward and break it (i'm not talking about bugs or security vulnerabilities here, only the functionality itself)
prominent example is w/ microsoft word, where they kept adding an absurd number of features simply bc they felt like they had to, since ppl were paying for it, and this will KEEP HAPPENING TO EVERYONE so long as the software keeps moving at breakneck speed and backwards compatibility and stability are thrown out of the window...
I use spotlight constantly for everything, but I admit I don't use the search feature in settings all that often.
like, you learn to work around this, mostly by just using raycast, but it's just unacceptable that they've spent BILLIONS on useless ai shit, while stuff THAT HAS WORKED CORRECTLY ALREADY IN THE PAST gets broken and goes unfixed for literal years