Unless you have built your own custom version of wine, and/or you don’t remove your wine directory between versions, you can always install a different version of wine and try it out.
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.
Unless you have built your own custom version of wine, and/or you don’t remove your wine directory between versions, you can always install a different version of wine and try it out.
Donated! Glad you are branching out, doing something to spur you on, and working to keep yourself encouraged.
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.
It sounds like Nextcloud, an alternative to the Google services platform, may have a feature like this through their PhoneTrack app. Is that what you are looking for?
You’d have to set it up, but Nextcloud is easy to set up.
Tesla, himself, is giving a gentle thumbs up from his grave.
+1 for StandardNotes. It’s been a wonderful product.
TL;DR use FF
The stage where I eat wings. Mmmm.
+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.
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
“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 ::
I would highly consider leveraging the AsteroidOS project – a privacy-focused linux smart watch effort – on one of their approved devices. That link should bring you straight to the watches they support.
Pine Time works well with Pine Phone, but only has basic functionality with other Android devices, like notifications. Not much else last I looked, but I may be out of sync with the community’s development efforts.
The Bangle.js 2 smart watch is another open source device you could look into.
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?
I am so digging this!