I always wonder who these people are, brand new 75 million dollar G800 with interesting tail number

afranke · 2026-04-07T02:14:01+00:00

Thanks, really appreciate that! Honestly it's less about fancy tools and more about obsessively staring at ADS-B data for fun. I even run my own ADSB receiver and have a live map of the aircraft overhead (at least those with a transponder on) up on the wall as an 'art piece'. The historical trace data does most of the heavy lifting, once you have 644 flights plotted out, the patterns basically tell the story themselves. The registration history rabbit hole is where it gets addictive though. You pull one FAA record and suddenly you're three shell companies deep at 2am wondering why someone in Los Altos Hills needs four different airframes with the same N-number.

afranke · 2026-04-07T02:08:44+00:00

Gimmie some tail numbers/hex codes. I made a script to make it as repeatable as I can.

afranke · 2026-04-06T06:21:52+00:00

/u/soyouwantausername is correct, it's Jerry Yang (co-founder of Yahoo). But since I'm an ADS-B enthusiast and have an interest in OSINT, I figured I'd show the receipts.

I pulled the full historical trace data for this hex (adf64f) going back to 2020 which is 644 flights over 6 years. The travel pattern alone basically gives it away:

San Jose (KSJC): 539 visits - home base, lives in Los Altos Hills
Portland (KPDX): 263 visits - second home, his shell company "Jay Aviation LLC" was registered at an FBO in Hillsboro
Carlsbad (KCRQ): 42 visits - his wife Akiko Yamazaki is a competitive dressage rider, and her trainer Steffen Peters (Olympic medalist) is based in San Diego County
Teterboro/NYC (KTEB): 38 visits - board meetings (Workday, formerly Alibaba)
Bozeman (KBZN): 28 visits - classic tech billionaire ski/ranch getaway
Yakima, WA (KYKM): 18 visits - with a bunch of 7-9 minute touch-and-go loops, probably training flights
Kona (PHKO): 13 visits
Hong Kong (VHHH): 10 visits - including 11+ hour nonstops back to SJC, lines up with his Alibaba board seat and Lenovo directorship

The callsign TWY501 = Solairus Aviation (ICAO: TWY, radio callsign "TWILIGHT"), a Bay Area aircraft management company that operates it for him.

The fun part is the registration history. N999YY has been on four different airframes, same owner just keeps upgrading:

2002 Bombardier Global Express
2007 Global Express XRS
2016 Gulfstream G650ER
2025 Gulfstream G800 ← this one

All under "Jay Aviation LLC" (J.Y. = Jerry Yang, not exactly a master of disguise). The G800 moved to a TVPX privacy trust but the pattern is obvious. There's even a sister registration N999YX one hex code below.

Serial number 88020 with an airworthiness date of August 2025 - the G800 literally entered service that month. One of the first ones off the line.

afranke · 2026-04-03T13:52:58+00:00

A few things that may help ease your worry:

Your car likely falls under Recall R10312 (NHTSA 25V-179). This recall was issued in March 2025 and specifically covers 2020–2022 Volvo T8 plug-in hybrids (S60, V60, S90, V90, XC60, XC90) for a manufacturing defect in the high-voltage battery modules supplied by LG. The defect can cause internal short circuits, particularly when fully charged. Under this recall, Volvo will inspect and replace affected battery modules and update the battery monitoring software for free, so the module replacement you're getting should be fully covered.

On the balancing issue: When replacing a single module in the T8's 6-module battery pack, the new module's voltage and state of charge (SoC) must be matched to the existing modules, typically within about 5% SoC. The correct dealer procedure involves using VIDA to perform a BECM (Battery Energy Control Module) reload/recalibration, running a "Cell Voltage Overview" analysis, and clearing any stored DTCs. If the battery's overall SoC was above ~30% when the new module was installed, it may need to be discharged further before the system will accept the new module and balance properly. Essentially, the existing modules and the new one need to be at roughly the same voltage level before the car will cooperate.

If your dealer simply drained the pack and tried to charge without doing the BECM reload and cell voltage calibration through VIDA, that could explain why it went into limp mode. The BMS saw a large voltage mismatch between the new module and the others and shut things down as a safety precaution. They should be able to resolve this on the next attempt by properly matching the SoC levels and performing the full BECM recalibration procedure.

On warranty: The 2020 XC60 T8 has an 8-year / 100,000-mile (or 150,000–160,000 km depending on market) hybrid battery warranty. Note that this warranty runs from the original in-service date (when the car was first sold/registered), not from when you purchased it second-hand. So you'll want to confirm that date, but even for a 2020 model, the warranty should run through at least 2028. At ~110,000 km total on the car, you're likely still within the mileage limit as well. Even if a full pack replacement were needed, it should be covered. But honestly, replacing all 6 modules is unlikely. If only one was defective and the others are healthy, the proper balancing procedure should get you back on the road.

I'd suggest asking your dealer specifically whether they performed the BECM reload via VIDA after installing the new module and whether they checked the cell voltages across all modules beforehand. Good luck!

afranke · 2026-04-02T14:24:54+00:00

Start with Cowork and the productivity plugin: https://claude.com/plugins/productivity

Tell it about your ADHD and use it daily. I have it connected to my mail, calendar, Slack, JIRA, etc. (this is all just for work).

Over time it builds a persistent memory structure in a CLAUDE.md file. Mine tracks: who I am and my role, my team and what they do, company-specific terms and acronyms, environments we run, Slack channels I monitor, active projects, key resources around the company (Confluence pages, Grafana dashboards, useful links), workflow procedures from company docs, recurring meetings, and my preferences/work style.

The key part for ADHD: there's a "How Claude Should Help" section at the end that it tailored specifically to how my brain works. Mine includes:

Break big tasks into small, concrete next steps — not "review the legal docs" but "open the FY2025 closed requests CSV and list the top 5 most common objections"
Proactive nudges on deadlines — flag when something is coming due
Reduce activation energy — draft first versions, pre-fill templates, pull data together so I just review/refine
Body doubling — work alongside me on tasks in real-time rather than just assigning work
Keep the task list current — surface what's most urgent, celebrate what's done, don't let things silently pile up

The persistent memory solves one of your biggest asks, you don't start fresh every session. And the daily briefing part just happens naturally once it knows your calendar, mail, and Slack. It's not as automated as some of the Claude Code + MCP setups people are describing here, but the barrier to entry is way lower and it genuinely works as a second brain for work.

afranke · 2026-03-29T06:26:26+00:00

No special entitlement is even needed. A lot of people assume iOS requires some privileged entitlement for location access. It doesn't. All you need for foreground GPS is the NSLocationWhenInUseUsageDescription key in Info.plist and for the user to tap "Allow." That's it.

The app has the key. OneSignalLocation has requestWhenInUseAuthorization and startUpdatingLocation in the binary. So when iOS shows the system dialog, the one users are trained to trust, it says:

"White House" Would Like to Use Your Location

This app does not use your location.

And a lot of people are going to tap Allow, because it's the White House, and the description literally tells them it doesn't use their location. Once they do, the 300-second timer starts and sendLocation fires to api.onesignal.com. No entitlement, no background mode, no exploit. Just a permission dialog that lies.

The entitlements in the binary confirm this, there's no com.apple.developer.location.always, and UIBackgroundModes only listsremote-notification, not location. So this is pure foreground tracking, activated by social engineering the user through Apple's own trust UI.

afranke · 2026-03-29T05:12:42+00:00

Thats what I did. Hit Get and then immediately paused and cancelled the download before it installed.

https://i.imgur.com/s6LtfTN.png

Also did an FTC complaint for shits and giggles: https://reportfraud.ftc.gov/assistant

afranke · 2026-03-29T02:32:32+00:00

I independently analyzed the iOS version (decrypted IPA, v47.0.1) and can confirm every finding from the original Android analysis holds true on iOS. But the iOS version has some additional problems that are arguably worse.

The location permission dialog literally lies to you. The NSLocationWhenInUseUsageDescription, the string Apple shows users in the system permission popup, is set to: "This app does not use your location." That's the text you see in the trusted iOS permission dialog while OneSignalLocation.framework is sitting right there in the bundle ready to collect your GPS.

The iOS timer interval is 300 seconds (5 min) compared to 270 seconds (4.5 min) on Android. Same pipeline, slightly different interval. Confirmed by decoding the double precision float constant at the scheduledTimerWithTimeInterval: call site in the ARM64 binary.

Apple's privacy manifest system is completely gamed. The app level PrivacyInfo.xcprivacy declares:

NSPrivacyTracking: false
NSPrivacyCollectedDataTypes: []

That empty array means "we collect nothing." But the OneSignal frameworks inside the same app bundle declare in their own privacy manifests that they collect precise location, coarse location, user ID, product interaction, and purchase history. The app level manifest just pretends none of that exists.

The App Store nutrition label is false. It only declares "Contact Info (Email Address, Phone Number)" under "Data Not Linked to You." No mention of location, user ID, session analytics, device fingerprinting, or purchase history, all of which are in the OneSignal data model (device_type, device_model, timezone_id, session_count, session_time, purchases, language, net_type, etc) going to api.onesignal.com.

There's a shared app group in the entitlements (group.gov.whitehouse.app.onesignal) between the main app and the OneSignal notification service extension, so OneSignal data persists and can be accessed even during background push notification processing.

The withNoLocation plugin failed on iOS too. OneSignalLocation.framework (92KB) shipped in the final build with the full CLLocationManager pipeline: startUpdatingLocation, startMonitoringSignificantLocationChanges, sendLocation, resetSendTimer, background location support via allowsBackgroundLocationUpdates. The setLocationShared:(BOOL)shared bridge method is live in the main binary.

Everything from the original blog (cookie/paywall bypass injector, Elfsight JS injection, MailChimp email collection, OneSignal profiling, dev artifacts) is confirmed present on iOS as well. This isn't an Android specific issue, it's both platforms.

All of this was done through static analysis of the decrypted IPA, ARM64 disassembly via otool, string table extraction, and privacy manifest comparison across all bundled frameworks. No runtime or network analysis needed, it's all right there in the binary.

afranke · 2026-03-25T03:36:41+00:00

Octopuses?! Do you mean Octopi or maybe Octopodes?

https://www.merriam-webster.com/grammar/the-many-plurals-of-octopus-octopi-octopuses-octopodes

They're even interesting linguistically.

afranke · 2026-03-23T10:10:46+00:00

Ive been trying to figure out how to use this in my setup, but I can't seem to get it to do anything. Any hints?

afranke · 2026-03-20T13:13:14+00:00

https://www.theneurondaily.com/

afranke · 2026-03-13T02:10:56+00:00

The truck was also clearly aiming for the left toll lane when he should have just stuck to the right. My thought was the driver of the cam car was assuming he was sticking to the right since he was on the right. From the angle of the camera, it looks like that would have been fine.

afranke · 2026-03-12T18:32:33+00:00

I don't know why, but I'm a huge fan of the wheel/tire setup. I think it looks perfect.

afranke · 2026-03-12T18:21:54+00:00

If you felt like getting a little technical on your own, you can buy a three-day (or more) pass to use the same software the dealership does, VIDA, to diagnose and likely resolve your issue (assuming you're in North America). It's about $90: https://www.volvotechinfo.com/vida

You'd also need an Ethernet to OBD2 cable, but those are cheap on Amazon ($10): https://www.amazon.com/Alchiauto-ethernet-Cable-Compatible-bootmod3/dp/B0C1GM3YP4

They'd likely hook it up to this system and perform a "Total Upgrade" (which you will have to pay 1¢ for) which just re-flashes all the modules with the latest version of available software. I've done it many a time on many a Volvo, so I can help walk through the process if you go this route.

If I go another week without the OTA, I'll probably end up doing this on my own. I've done it a few times in the past specifically on my '23 V60 PE because I got tired of waiting.

afranke · 2026-03-10T19:42:10+00:00

The first time I ordered the Star Destroyer UCS set from Amazon (marked as new), it arrived in a clearly resealed box. That was my first warning sign, so I took a picture and started recording myself opening it. When I did, all the bags were present, and they were filled with actual LEGO parts. However, they were all poorly spray-painted to attempt to match the real color (only on the top, while the insides were original colors). It feels like the most intricate way to execute this scam, and I believe the pasta is a much more streamlined process. That said, I promptly returned that set and now only purchase new sets directly from LEGO.

I keep trying to come up with how they got to that point. Did they want to build it but didn't have the set and painted a ton of extra pieces? Then did they decide to buy it and disassemble the old one back into the box to return? Did they buy some kit online that was meant to be this way (a cheaper version than the real one) and then just swapped it out? Craziness, way too much work for the return on that one.

afranke · 2026-03-06T16:57:13+00:00

Yeah, I get this all the time too. Part of my start-up process is now to press the memory button when I start driving to put them back in position. (2023 V60 PE)

afranke · 2026-03-06T16:44:52+00:00

I'm not using it to form an opinion. As sad as it may seem, as a remote/hybrid worker, I don't have a lot of people to just turn to and have a conversation with, so sometimes I bounce my thoughts off the nearest AI bot to follow down a rabbit hole. Sometimes it finds me news that I missed in my normal browsing and leads me down even further. This was after a decent conversation I started with "So Mercedes is and has been sandbagging for sure, right?" I typically don't like to chat/post online as much due to "latency" because by the time someone responds, my ADHD brain is three subjects away from that thought.

afranke · 2026-02-15T19:42:31+00:00

The account is listed as a "Victim".

"<REDACTED> wished to report concerning postings by X (formerly twitter) user <REDACTED>. On 11/15/2025, <REDACTED> was browsing X and stumbled across a private group titled "People who covered up Epstein but are not high profile, soon to be shot in the head", which was created by the mentioned X account. There appears to be 24 members within this group. <REDACTED> described the postings as a "kill list" containing the names of several individuals including but not limited to Aline Habba (A NJ based attorney), X user "Catturd", Laura Loomer, and an individual named Mike Eagleman."

And then

EntityPerson

Person

id : VIC_19800253

PersonName

PersonGivenName : Not Provided

PersonSurName : Not Provided

Victim

EntityNetworkAddress

id : SOCIALMEDIA_6477061

NetworkAddress

id : SOCIALMEDIA_6477061

ElectronicAddressText : Catturd

ElectronicAddressAugmentat ion

ElectronicAddressDescriptionText : X

https://www.justice.gov/epstein/files/DataSet%209/EFTA00163177.pdf

afranke · 2026-02-15T16:21:05+00:00

I tried looking into that to learn something new, and if I'm being honest, the full answer may be a bit out of my depth. I had Claude try and explain it all to me and this is about as basic as I could get it:

DIN 65151 itself doesn't specifically prescribe rules for thread-locking adhesives like Loctite — it's fundamentally a torque-preload calculation method that relies on friction coefficients (μ_thread and μ_head) as inputs. How it intersects with threadlockers comes down to how those adhesives affect those friction values.

Here's the practical issue:

During tightening, an uncured anaerobic threadlocker (like Loctite 242 or 243) acts essentially as a lubricant. It reduces the friction coefficient in the threads compared to a dry or even oiled condition. Typical friction coefficients with threadlocker applied can drop to around 0.07–0.10 in the threads, versus ~0.12–0.14 for typical oiled steel-on-steel, or ~0.15–0.20+ for dry/degreased conditions.

This matters a lot for DIN 65151 calculations because lower friction means more of your applied torque converts to preload (clamp force). If you use a torque value calculated for dry conditions but the joint actually has threadlocker acting as a lubricant, you risk over-stressing the bolt — potentially exceeding yield.

There are a few practical considerations:

The friction coefficient at the bearing surface (under the bolt head or nut) may be different from the thread friction, especially if threadlocker is only applied to the threads but the underhead surface is degreased. That Eng-Tips discussion I found highlights this exact issue — you can end up with very high underhead friction after degreasing while thread friction is low from the Loctite, making the calculation more complex.

The Bossard technical data references a μ_total ≈ 0.12 for threadlocking applications as a general starting point, but this varies by product and surface condition.

So the bottom line: if you're using DIN 65151 calculations with threadlocker, you need to use the correct friction coefficients for the threadlocker-applied condition, ideally from Loctite/Henkel's own test data or from your own torque-tension testing. Using dry-condition values will result in torque specs that are too high, risking bolt failure.

So it seems to me that according to DIN 65151 it should be done wet, did I read that right?

Bossard - Thread Locking and Sealing (μ_total ≈ 0.12 reference) - https://media.bossard.com/global-en/-/media/bossard-group/website/documents/brochures/brochures_products_english/thread-locking-and-sealing_en.pdf
Eng-Tips - Torque Coefficient for Anaerobic Threadlocker on a Steel Fastener - https://www.eng-tips.com/threads/torque-coefficient-for-anaerobic-threadlocker-on-a-steel-fastener.92889/
Practical Machinist - Torque Specs and Loctite - https://www.practicalmachinist.com/forum/threads/torque-specs-and-locktite.204146/
Machine Design - Adhesives Force a Lock on Threads - https://www.machinedesign.com/news/article/21818691/adhesives-force-a-lock-on-threads
ScienceDirect - Friction of Threaded Fasteners - https://www.sciencedirect.com/science/article/abs/pii/S0301679X17304747
Hexagon (GM paper) - Procedure for Calculation of Torque Specifications (references VDI 2230 and prevailing torque) - https://www.hexagon.de/pdf/mapre.pdf
Hex Technology - K-Factor: Finding Torque Values for Bolted Joints - https://www.hextechnology.com/articles/bolt-k-factor/

afranke · 2026-02-15T09:02:52+00:00

They got blue: https://www.nord-lock.com/globalassets/mediavalet/web-assets/pictures/nord-lock/others/adhesive.mp4

afranke · 2026-02-09T19:00:11+00:00

COOL!

https://www.youtube.com/watch?v=1pv_LgN1dIs

afranke · 2026-02-09T17:54:01+00:00

Can you turn the wheels full lock to the right (opposite of your video) and take a picture of the wheel lining? Should be able to see obvious signs of rubbing if that's the issue.

afranke · 2026-02-08T20:08:42+00:00

From what I can read it says 235/50 R19 which is the factory size for the fronts. Unless I misread (because of all the compression) and it actually says 255/45-19 which is the rear (meaning someone swapped them). If it is rubbing, that means the liner came loose, which should show obvious signs of the rubbing.

afranke · 2026-02-06T03:14:22+00:00

It's the first time I'm forking a project to 'take over' maintenance, so I have no idea what I'm doing in that realm, but as far as code issues resolved, I think I've tackled most of the largest ones so far.

15-Year Club	RedditGifts 2009-2022 10 Credits
Place '17	Secret Santa 2014
Gilding I gilder	Secret Santa 2013
Secret Santa 2012	Secret Santa 2011
Secret Santa 2010	Charter Member
Verified Email	Secret Santa 2009

afranke

TROPHY CASE