Grant Joseph

@GrantJoseph
4 Followers
64 Following
195 Posts
Software developer and cybersecurity major. Available for hire. Check out my new website and blog!!
Bloggrantjoseph.dev
Email[email protected]
X/Twitterhttps://x.com/GrantLJoseph
Show threadGrant Joseph6d ago
@GrapheneOS Ah, okay. I forgot this was already the Q3 release. I appreciate the explanation!
Grant Joseph6d ago
Show threadGrapheneOS6d ago

@GrantJoseph The next release is Android 17 which will be received by AOSP.

The standard cycle is a yearly release in June, 1st quarterly release in September, 2nd quarterly release in December and then the 3rd quarterly release in March.

The yearly release and 2nd quarterly release are the ones intended for use by other OEMs and pushed to AOSP. Security backports are provided for the yearly release and 2nd quarterly release which is what the security preview releases we make are based on.

Show threadGrant Joseph6d ago
@GrapheneOS If I'm following, that means it will reach AOSP at the time of the 2nd quartly release?
Grant Joseph6d ago
@GrapheneOS Is there a timeline for when desktop mode newly announced by Google for a Pixel Drop is coming to GrapheneOS? I've been very excited for desktop mode reading GA. I'm not knowledgeable enough about GrapheneOS release cycles to tell if I should be able to figure out the timeline on my own.
Grant JosephMar 16
/etc witchMar 16
i am curious as to why the seattle mariners thought it was necessary to specifically write a rule against dropping off your dog at the baseball park, having the dog show their own ticket, and walk to their assigned seat on the view level to watch a baseball game without a human
Show threadGrant JosephMar 16
@hackbyte I took all my meds today. Didn't miss a bottle. I think I made it pretty clear I don't think removing encryption is okay. But I do understand the business case for a company that cares far more about business than privacy or human rights. I honestly don't think this is that big of a deal because no one should expect real privacy from fucking Instagram. It should never have been considered more than a gimmick by anyone who understands secure messaging. We have Signal for that.
Grant JosephMar 16
Show threadGrant JosephMar 16
@mshelton Realistically, every random social media service doesn't even need their own DMs. We don't need a so many different messaging services. Especially when a company like Meta has WhatsApp, they should unify it with Facebook, Insta, etc. and just use its infrastructure everywhere. But that's probably not good for social media business/retention. Federation tech could help though, if they're willing.
Show threadGrant JosephMar 16
@mshelton Realistically, every random social media service doesn't even need their own DMs. We don't need a so many different messaging services. Especially when a company like Meta has WhatsApp, they should unify it with Facebook, Insta, etc. and just use its infrastructure everywhere. But that's probably not good for social media business/retention. Federation tech could help though, if they're willing.
Show threadGrant JosephMar 16
@hackbyte @mshelton When you keep a feature, you need to support it. Browsers, operating systems, and dependency libraries change with time. This will introduce a maintenance burden to keep the feature working. Instragram itself will also change around the encrypted DMS. It's not like everything is standing still, and all of that is a maintenance burden. And when things break, people file support tickets. Hell, people file support tickets regardless, that someone has to handle.
Show threadGrant JosephMar 14
@mshelton It takes even more engineering hours to support a feature to keep it from decaying with time. I think E2EE should absolutely remain, but removing it could make sense for purely practical reasons.