Am I an ant? Yes.

But, am I spicy? Also yes.

  • 1 Post
  • 3 Comments
Joined 1 year ago
cake
Cake day: January 19th, 2024

help-circle
    1. The fear of missing out was something that made me double think deleting my facebook. It turned out to be unfounded fear, as none of the hypothetical “missing out” scenarios have proven to be an actual problem.

    If the study group is very important to you, and the study group is on Facebook, then just have a Facebook. Deadlines and test info are not critical information that you need to receive in your pocket as soon as it is shared. You can check your anonymous Facebook account once a week through a VPN in a desktop computer and you will likely be well informed enough. If you have a friend that is both in Signal and that Facebook group, you can tell them about this and ask as a favor that they forward any critical time-sensitive info.

    As for my response, mostly I use XMPP. I turn on my WhatsApp phone on every few weeks. People can message me via XMPP, e-mail, or Signal.

    1. I have a little scanner. I can use the phone’s browser and log-in, using the scanner for the 2FA. But it is very rare that I use banking through the phone, as I do most of my banking via a desktop computer.

    2. Bike, public transport, walking, and planning ahead.

    3. On the desktop I do use Google Maps as it is quite efficient. Usually I plan ahead if I am biking somewhere new. I will often draw a path, write some street names at turns/crossings to remember, and pick some landmarks. Usually I am moving near places I know, so this is not task that comes up often.

    4. At different points in time I have kept multiple fitness and nutrition logs (on websites and notebooks), but I rarely looked back at them. Now days I track rest times, hear rate, and running parameters while exercising, so I have a garmin watch and look at the output logs at the end of the exercise on the watch itself. It is not connected to any apps.

    5. I make use of three devices: I. A Pixel phone running GrapheneOS has no SIM card. I have my apps, music, etc in this phone, and I use it as a mini tablet. It needs WiFi to get internet.

    II. A PinePhone. I bought a large stack of the cheapest pre-paid SIM cards a while ago, and put in a new one whenever a SIM card runs out. I wrote a hook that, when I power down the device, a random IMEI is generated and written to the LTE modem. So, if I turn it off, swap the SIM, and turn it back on, I have a phone with a completely new mobile identity. This phone I can use to make calls and to share data with the GrapheneOS, but it does not have a static phone number. Usually it is off.

    III. A Raspberry Pi 5 with a 4G LTE hat. This hat takes in a SIM card that is stable. So, this device is associated with a phone number and a persistent identifier, but it does not move. This is my phone number. SMS messages get sent to me via XMPP. If I am called, my XMPP also lets me know. I don’t have VoIP, so I do need to call back if I choose to. However, it is so so rare that I make a phone call that I have not bothered to implement VoIP.



  • Step 1 of installing GrapheneOS for de-googling your life: Buy a Google Pixel phone

    Look - I know, I know. I get it. Google allows you to unlock the bootloader while maintaining the phone’s unique and excellent hardware security features. The argument makes sense. It is compelling. Other manufacturers do not give you this freedom. I am not arguing about that. I have a Pixel phone running GrapheneOS myself.

    However… It is just so very obviously ironic that one needs to trust Google’s hardware and purchase a Google product to de-google their life through GrapheneOS. I think that it is a perfectly valid position for someone to raise their eyebrows, laugh, and remain skeptical of the concept either because they do not want to support Google at all, or because they simply will not trust Google’s hardware.

    The reason why I think that this is “controversial” is because I have seen multiple instances of someone pointing out the irony, followed by someone getting defensive about it and making use of the technical security arguments in an attempt to patch up the irony.