Donated! Glad you are branching out, doing something to spur you on, and working to keep yourself encouraged.
Deliverer of ideas for a living. Believer in internet autonomy, dignity. I upkeep instances of FOSS platforms like this for the masses. Previously on Twitter under the same handle. I do software things, but also I don’t.
Donated! Glad you are branching out, doing something to spur you on, and working to keep yourself encouraged.
Tesla, himself, is giving a gentle thumbs up from his grave.
“We did the back-of-napkin math on what ramping up this experiment to the entire brain would cost, and the scale is impossibly large — 1.6 zettabytes of storage costing $50 billion and spanning 140 acres, making it the largest data center on the planet.”
Look at what they need to mimic just a fraction of our power.
+1 for Netdata
This is :: chef’s kiss ::
Dumb error messages like that have to do with the UI and UX. The user interface (UI) in APT has mostly to do with how easily users see, recognize, and understand descriptions of errors (that is, how text appears and is organized), and the user experience (UX) in APT has to do with how easily users can, say, follow-up, within the tool, to resolve those errors.
An example of a better UI in APT could be grouping to-be installed packages with clear linebreaks and color, or highlighting how much space is to be used by bolding it. All good stuff that isn’t gonna kill my eyes when I have to scroll around to find what was / wasn’t installed properly.
And that scrolling around is all about the UX. An example of a better UX could be installation bars rather than percentages to keep the screen from scrolling past errors too quickly, affordances for users to make decisions within APT to resolve dependency issues without it dropping back into the terminal (again, dumb error messages), or providing help within the interface without having to back out to the terminal and use APT with an operator.
I think it would be great to keep those error messages you mention, like, front-and-center, even after an operation has wrapped up. Who wants hunt/grep through a full log?
It’s Linux-based hardware, so any OS could be installed easily if PureOS isn’t a good fit for OP. And, unlike the phone, it’s basically a computer, like one of their laptops (which have been fine).
If we are talking about Pinephone, Fairphone, Librem 5, etc. – they all suffer uniquely. Modems drop on all these devices often enough, battery life sucks based on tasks, app support is sundry, screens are left wanting, and more. Phones are hard to make.
I might class Linux-based hardware phones differently from Linux-based hardware tablets.
deleted by creator
+1 for battery voltage, OP. You may have a faulty battery. If that is the case, how long have you owned the replacement? Is it within a window of returning it?
Duskers looks fantastic. Thanks for sharing the link!
I suspect it may be a bit more along how you’re describing here – we expect some user experience patterns to already be in place, if not considered, like not being able to select inappropriate handles. Former Twitter folks should know ‘better.’ From the outside looking in, it tracks.
I wonder if the Bluesky team, right now at least, is more engineer / dev heavy, and they have not brought on UX folks to help drive a product design that considers patterns we’d be used to experiencing. They may be operating pretty lean.
An idea, at least.
Only the Taco Bell distro will survive.
I am so digging this!