As far as I understood from Graphene, when Google released the source code for Android 16, they also stripped all the reference code for Pixel devices.

Historically, Google would ship the code for Pixel and a software emulator as “reference designs”. Now, it’s only shipped with the emulator.

The Graphene Team needed to reconstruct the pixel code from the Android 15 release. Fortunately, the divergence between Android 15 and 16 was minimal, but I’m certain the division will widen as time goes by.

… except for the binary os blobs, that’ll need to be reverse engineered to run it on… well… any real hardware /s

… and force push.

If you ever find yourself in a situation where rebase or a force push seems to be the solution, take a step back, clone your repo in a new directory and copy the changes into you’re new checkout - ‘cause you gon’ and screwed somethin’ up, son.

trunk?

Oh, I know the answer to this one: superbad.com (suitable for work).

… I bet they’d be able to work remotely if they switched to Slack :P

Take a look at ssh-agent. It’s bundled with ssh-client and designed to solve this problem.

The quick usage is, create a terminal and run:

eval `ssh-agent`
ssh-add /path/to/your/encrypted/key1
#type in password
ssh-add /path/to/your/encrypted/key2
... 

# all commands in this terminal will use the keys above w/o asking you for a password 
git clone git@githib.com...
git push... 
etc

So, basically you type your credentials once during the life cycle of your terminal.

If you really want to go full power-user, simple run ssh-agent (without the eval) and you’ll see it just sets some env-vars, which can be imported into any terminal/shell you have open.

So, if you put some logic in your shells rc file, you can effectively share a single ash-agent between all your shells, meaning you just need to type your password for your keys once when you log into your system… and your now passwordless for any future terminals you create (this is my setup).

Also, if you’re interested take a peek at the man pages for ash-agent. It has a few interesting features (ie: adding a password lock for your agent, removing keys from the agent, etc).

A link for those interested.

OP, what bluGill said is exactly your problem (assuming your DMARC and friends are setup correctly).

The concept is referred to as “email (or domain) reputation”. The implementation details are closely guarded secrets, unique for each email receiver.

One of the metrics for establishing a positive email reputation the “How much email does your mail server sends?” : the more the better**

If you’re a large company, it’s fine… but if it’s just a personal domain with < 20 per week, you’re not going to establish a reputation and (depending on the receiver) you’re email might just get dropped.

The other (frequent) metric is: “Of the emails that are sent, how many are read, and how many are flagged as spam?” In order, for these crowd sourced spam filters to work, they need you to send large amounts of email. Receivers like Gmail/Google are pretty forgiving. However, Outlook/Microsoft are very aggressive, meaning if enough outlook users flag your email as Spam, then future emails sent to outlook from your domain will probably automatically be marked as spam. Obviously, these are all black boxes, so I can only offer my personal observations (take it worth a grain of salt).

As bluGill mentioned, there is a solution, but it involves moving your custom domain to a larger (re: paid) email provider. If you were to move to Google (for example), it doesn’t matter if your custom domain sends 5 emails per week. Those 5 emails are being sent from Google mail servers (using your custom domain) , which means they’re gaining the “reputation” of google and you can be certain that your emails will arrive, even if it’s (non-obvious) spam. Because, the email receiver assumes that Google will shut you down, if you’re a spammer.

It’s a sad state that one of the original “pillars of the internet” (email) has degraded to feed only the big tech companies… but unfortunately this has been the case for many years.

Without getting too critical of your code (congrats BTW), never use strcpy instead use strlcpy.

strcpy will happily allow you to create buffer overflows (a common challenge with C) which will cause your application to crash.

You’ll find more details here.

Good luck!

The handful of us have moved onto Crystal Lang. It’s a statically type checked and compiled dialect of Ruby. Crystal is fun to write code, but the compiler is slower (compared to go-lang/rust)… because… well it’s a ruby dialect (with DSL’s)… and the 3rd party libraries are limited.

Thank you for finding that.

I got lucky, I bought a quest around July/August and needed to do the mandatory/initial OS install.

I ended up with v78 (August 3, 2025) release.

I didn’t realize there was a WiP announced in July 2025.

… makes the latest headset with a rather recent update (but NOT the very last ones, so be cautious!) rootable.

Any ideas which version(s) are susceptible? I couldn’t find it mentioned.

Actually, those steps are the ones necessary to recover from a hard brick (re: the device is unusable because you did something you shouldn’t have as root).

The actual process to root the device is simply running a few adb commands (so a prereq is having Developer Mode enabled).

Once you have ran the exploit, your root escalation is temporary until the device is rebooted or you take additional steps to persists your root privileges (thus, potentially leading you towards a hard brick).

source: The docs

How do you think this technology would be abused?

If the device included full audio and video surveillance - I’d totally agree. However, the device does not include video (and it would be a real hard sell to include that).

If all parties are aware that monitoring will occur (maybe include a sign in the door), I’d argue that minors are aware of what this means.

Perhaps, it would mean that students “finish up” faster, rather than loitering and vaping (or bullying, etc)… and if that’s the case, I guess the device has fulfilled it’s purpose.

The article did mention how a hacked device could be used to “play sounds” or trigger false calls for “help”, or gunshots. But I’d argue this would be the modern day equivalent of falsely pulling the fire alarm.

An interesting article and tbh, I’d actually support the device (… and I’m usually very privacy focused).

According to the article the purpose of the microphone is to listen for certain keywords (ie: “help”, “call 911”, gunshots, etc) and to detect when people are vaping, etc.

I mean, I would never install one in my home, due to privacy and security concerns. But if you’re in a public place, like a school such features make sense.

If you’re being bullied or need help, having a facility member “hanging out” in the schools public bathroom would be weird, creepy, and more of an invasion of privacy than a mic in a smoke detector.

That said, students and facility should be aware of what this device is doing and why. However, this article does a very good job of summarizing that.

Yes, the devices security is rubbish, but was patched. It’s not the first IoT device to do that and it won’t be the last (unfortunately).

Thanks for sharing the article OP.

Thanks for recommending Navidrome. It looks really interesting.

I was using Spotify, but switched to Spotube. After Spotube was crippled, I was kind of aimless. I really liked having my music available on my cellphone and desktop. It looks like Navidrome will fill the gap perfectly.

You’d mentioned ripping CDs. Would you have some software, you’d recommend (Windows or Linux)? Preferably in FLAC.

I haven’t looked at ripping software in a few years, but it was kind of tedious to set up and very manual to get the proper metadata, genres, and cover art. I’ve got a hundred CDs and that’ll take awhile…

It could be the quality of your headphones.

I’m not an audiophile, but back-in-the-day I bought some analog “sennheiser studio monitors” as opposed to “just headphones”.

I actually returned the first one and exchanged them, because when I listened to a live recorded CD, I kept hearing loud “pops” that I didn’t hear with my “regular headphones”. I assumed they were defective.

The exchanged sennheiser had the same “pop” in this CD. It turns out, most “regular headphones” didn’t have the same depth in sound frequency as studio monitors and the “pops” were accidental artifacts that were mixed into the CD.

For other CD’s, I’d hear telephones ringing and sirens in the background.

Eventually, I got use to it. Then after a few years, I replaced my CD collection with mp3’s… and I could tell a different in songs/albums I was really familiar with. The base wasn’t as deep, the high sounds weren’t as high, I didn’t hear telephones ringing in the background.

I had the same sennheiser, it was just that the nature of mp3’s “flattened” the music.

Now, with Bluetooth and the disappearance of 3.5 mm jacks, there are too many layers of digital conversion happening. I’ve given up… and now just have some cheap ear buds I listen to.

If you’re whitewater kayaking, it’s not uncommon to have a knife accessible from your PFD.

It can be used to cut any ropes you might be tangled in or (worse case) cut the PFD.

In general, having a knife with you is useful in most emergency situations (and a throw rope, pin kit, plus knowledge of how to use them).

edit: Oops, this was supposed to be a response for the parent thread.

… and I want my headphone jack, back.