chirospasm

+1 !!

Currently, I prefer the Kagi model as my daily driver – pay a small fee each month and not worry about having your search data, in all its forms, sold instead. They have some neat features, as well, like AI summaries and the ability to ask questions about pages. It’s those two features I have used to determine what kind of content, even musical, may be on the page for me without having to go to the page, itself.

There is also SearXNG, which is an open source, privacy-respecting, hackable metasearch engine. It can be self-hosted and also has a number of instances you can access.

GrapheneOS user here – for many years and several devices. Also had many devices, prior to that, running LineageOS.

GrapheneOS

First thing to weigh, between your two options, is that GrapheneOS is considered its own mobile operating system at this point, and the development of this mobile operating system is driven chiefly by privacy and security. While founded on AOSP, GrapheneOS gets such benefits as – but not limited to – more frequently updated kernel patches, code removal or alteration to abate zero-day vulnerabilities normally addressed more slowly (or not at all) in vanilla Android, the security of a re-locked bootloader (only available on Pixel devices), an isolated and sandboxed Google Play to access normal apps (microG and other replacements are considered, in GrapheneOS circles, less secure), isolated user profiles for different sets of apps that have the ability to push notifications to each other, hardened memory allocation, and so much more.

Pixel hardware is a great fit for GrapheneOS due to the kind of security chipsets they employ, too. By selecting a device that allows users to re-lock the bootloader (other devices do not afford this), as well as leverage Pixel-specific hardware-level security features, there’s a measure of consistency for overall security provided to GrapheneOS users and developers, alike. The devs don’t have to provide workarounds, for example, in the same way other ROM makers do, such as for LineageOS. There can be focus. And that benefits everyone who is primarily interested in privacy and security in a phone OS.

LineageOS

Second thing to weigh, between your two options, is the intent behind LineageOS: it’s an open source variation of AOSP, and is considered both an excellent extension mechanism for aging Android devices and an open source alternative to vendor-created – and often vendor-locked – ROMs that come, by default, on a variety of devices. LineageOS has been focused on being one of the most consistent, open source ROMs around. This means the consistency in UX, features, and flexibility of LineageOS can translate between many targeted devices. Over 20 vendors of devices benefit from the hard work of LineageOS.

Like GrapheneOS is focused on privacy and security for their users, LineageOS is focused on being a solid, consistent ROM for their users.

Further Consideration

I can go into the weeds of both, but at some point I made a decision to buy into the Pixel ecosystem – and subsequently learned about GrapheneOS as an option. I value what they offer, and I understand their stricter alignment with their approach to developing an OS.

While I choose to lock myself into the Pixel lineup of phones, I would also consider LineageOS – modified to my own specs – if I had to shift to another device. Each have their strengths. Each have their focuses.

Features like this exist for putting the phone back at rest when there hasn’t been a successful unlocking for X hours – GrapheneOS, an Android OS, has a similar feature. The objective is to limit the window of time an attacker has to try to exploit anything the phone may have in operation during a not-at-rest state (when the user is still ‘logged in’ to the phone, certain background services / features may be available to exploit).

Rebooting automatically, especially if the phone not has not been successfully unlocked recently, may place the phone in a less exploitable state, as those services / features might not be available without logging in first.

I am so digging this!

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.’

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.

Woohoo!

Tesla, himself, is giving a gentle thumbs up from his grave.

+1 for StandardNotes. It’s been a wonderful product.

The stage where I eat wings. Mmmm.

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

“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 ::