• 0 Posts
  • 18 Comments
Joined 2 years ago
cake
Cake day: August 8th, 2023

help-circle
  • My regular Pixel 7 (not 7a) has a swelled battery and I can see the screen starting to separate from the rest of the case.

    The phone would be otherwise still fine despite being 2 years old. I’m sure even if it was covered, Google would find some way to not repair it under the program because it is a carrier unlocked model running GrapheneOS.

    I would opt for third party repair but the place I used for this exact problem before (replacing swollen battery on a Samsung phone) was a little sketchy and when I got it back, there was evidence they tried to rifle through my device.

    Aside from taking this to Rossman himself, I’m wondering if there are any other reputable 3rd party repair options.



  • My understanding is that, in broad strokes…

    1. Aurora acts like a proxy or mirror that doesn’t require you to sign in to get Google Play Store apps. It doesn’t provide any other software besides what you specifically download from it, and it doesn’t include any telemetry/tracking like normal Google Play Store would.

    2. microG is a reimplementation of Google Play services (the suite of proprietary background services that Google runs on normal Android phones). MicroG doesn’t have the bloat and tracking and other closed source functionality, but rather acts as a stand-in that other apps can talk to (when they’d normally be talking to Google Play services). This has to be installed and configured and I would refer to the microG github or other documentation.

    3. GrapheneOS has its own sandboxed Google Play Services which is basically unmodified Google Play Services, crammed into its own sandbox with no special permissions, and a compatibility layer that retains some functionality while keeping it from being able to access app data with high level permissions like it would normally do on a vanilla Android phone.





  • Its possible a sleeper cell of terrorists could effectuate some small area drone strikes with commercial off the shelf drones and improvised explosives.

    The large scale military drones you are envisioning that can do the same damage as military aerial bombardment, that is a much harder thing to “sneak” into the US at any kind of scale or to build in secret.

    As for future state actor capabilities. It seems possible that China is working on drone tech deployed from submarines or other force-projection platforms. Yet another reason to avoid a hot war with near peer militaries in current year.


  • I am running GOS on a Pixel 7, which means I’ve had this device for ~2.5 years at this point, and back when I transitioned to this setup I was aware they were talking about being beholden to Pixels due to the hardware security module not being available on other devices.

    It has been a known issue. I understand it is a very difficult and costly undertaking to develop new hardware and new entrants would be competing against the big guys for fab space, manufacturing and assembly etc.

    We need some kind of nonprofit or independently financed group to advance this cause. Could it be FUTO, Framework, or some other company/organization like this?

    There would be market incentive to solve these problems - There has got to be a lot of demand for a neutral hardware platform that meets the hardware security module and other requirements for bootloader security, custom ROMs, etc.




  • Side note -

    I literally have the reader pictured in the thumbnail. It is a Kindle keyboard from 10+ years ago at this point. It still works fine. At one point the original battery went to shit, and it cost very little to get an aftermarket replacement and install it myself.

    I keep it offline and read 100% sideloaded .epub books from various sources. The lockscreen ads don’t even try to display anymore.

    Sure it isn’t backlit or waterproof but it still functions flawlessly as a generic reader. Old tech like this is awesome. Why not get a decade of use (or more) out of something that still works?



  • I’m having an OK time with alternatives, namely GrayJay on Android and Windows desktop. Basically I had to make sure my subscriptions included the 50-75 creators I am actually interested in, then the list becomes 100% relevant because it is just videos from creators you are subbed to. On the Desktop app it still uses algorithm of some sort for sidebar content based on the current video you are watching only. So if you still want to “organically discover” things you can, but don’t have to.

    The only bad part with the Windows desktop version is it will crash the entire app mid-playback sometimes. Hopefully the bugs get fixed eventually. Also the “home” tab of Grayjay is some weird pseudo political stuff but at least you can ignore that entire tab and just look at your own subscriptions.



  • This is ironic because all the 40 year old chicks who are career users of FB since college, all cite the same justification for continuing to use it: “But all my photos and the current happenings of my friends”.

    If you showed them epirical data that only 17% of what they consume on the platform is actually even tangentially related to their friends and family, maybe they’d finally decouple themselves from FB.



  • The most-aggressively short timelines don’t apply until 2029. Regardless, now is the time to get serious about automation. That is going to require vendors of a lot of off-the-shelf products to come up with better (or any) automation integrations for existing cert management systems or whatever the new standard becomes.

    The current workflow many big orgs use is something like:

    1. Poor bastard application engineer/support guy is forced to keep a spreadsheet for all the machines and URLs he “owns” and set 30-day reminders when they will expire,

    2. manually generate CSRs,

    3. reach out to some internal or 3rd party group who may ignore his request or fuck it up twice before giving him correct signed certs,

    4. schedule and get approval for one or more “possible brief outage” maintenance windows because the software requires manually rebinding the new certs in some archaic way involving handjamming each cert into a web interface on a separate Windows box.

    As the validity period shrinks and the number of environments the average production application uses grows, the concept of doing these processes manually becomes a total clusterfuck.