chirospasm

I am so digging this!

Let me supersonic for you, Kermie

If you have access to any kind of UX and UI folks, you automagicallly get a leg up on this, y’all. It is goddamn amazing.

Single dev on a personal project? Go find someone in the community who has an eye for design or hit up a design forum. Work has you on a project with only two other devs and limited resources? Ask for a favor from the UX team down the hall.

We are all tryna make good experiences out here. Let us avoid getting ‘teabagged.’

Thinkpads – a laptop with a rich history of Linux use – can be bought with an integrated 4090. The ThinkPad P1 Gen 6 can be configured with an i9, plenty of flexibility for drive space and RAM, and an RTX 4090. It’ll run you, even used, around $3k to $4k, which is the equivalent of a desktop replacement. But it’ll be pretty doggone compatible with any Linux distro you’d like.

Donated! Glad you are branching out, doing something to spur you on, and working to keep yourself encouraged.

OpSec, y’all. OpSec.

fr fr

Use the user profiles feature of grapheneos to make a “social” profile and only use that to access Instagram / facebook.

You’ll want to consider isolating IG from your primary profile, to start. The above user’s suggestion hits the nail on the head.

Once the profile ks created, and you’ve installed IG, you’ll want to deselect the option in your Manage Profiles settings on GrapheneOS to ‘Allow running in the backgroud.’ This way, you can ensure the app is entirely stopped until you want it open.

Another consideration may be to turn off your Bluetooth when it’s not in use, as well: BT emits an ‘address’ of sorts that, if another IG user has enabled BT access on their IG app, may be able to detect your phone and track a conversation knowing you are in the other user’s vicinity.

Is IG on a completely different profile in GrapheneOS, or is the app installed on the primary profile where you use your other apps? GrapheneOS’s profiles completely isolate from one another.

Woohoo!

TL;DR use FF

Top comment, should be pinned. We need a gaggle of these. A gagglebyte.

Ah! A Chilean vegan, I see.

+1 For the Light Phone. Owned both their Kickstarter edition and their latest generation, and makes travel, camping, and more easy when I forward my calls/texts. Great battery life with still some creature comforts we have all gotten used to, smart phone wise.

Nice

Love me some Jitsi. The app, and website, make it easy to just start a secure, anonymous call with pals. No weird AI models running in the background like Teams or Zoom.

TrailSense, an easy to use, comprehensive wilderness tool.

The goals of the developer are fun to consider:

Goals

• Trail Sense must not use the Internet in any way, as I want the entire app usable when there is no Internet connection

• Features must provide some benefits to people using the app while hiking, in a survival situation, etc.

• Features should make use of the sensors on a phone rather than relying on stored information such as guides

• Features must be based on peer-reviewed science or be verified against real world data

Likewise, the features being developed under those goals are great for getting outside:

Features

• Designed for hiking, backpacking, camping, and geocaching
• Place beacons and navigate to them
• Follow paths
• Retrace your steps with backtrack
• Use a photo as a map
• Plan what to pack
• Be alerted before the sun sets
• Predict the weather
• Use your phone for astronomy
• And more

AROOOOOO BROTHER I FEEL YA BECAUSE SOMETIMES I AM CRANKIN MY HOG IN THE GARAGE SO MUCH AND I JUST FORGET TO GROCERY SHOP

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?