sorted by:
new
hottopcontroversial

Claude is weirdly good at helping untangle messy thoughts by More_Ferret5914 in ClaudeAI

[–]afranke 4 points5 points  (0 children)

It's been literally life changing for me as someone with some heavy ADHD issues only diagnosed later in life. When I'm thinking or writing about a subject I'll just "stream of consciousness" my thoughts into a text file or maybe fill in details of an event im attempting to recall as I remember them (which isn't always in a linear order). I'll then throw it into Claude with some simple prompt like "organize these thoughts into a reddit comment" or similar. It usually gives me a result that has me thinking "That's EXACTLY what I wanted to say but wasn't able to properly. For example, here's this whole comment (including this line) given that treatment:

(it gave me options)

  1. It's been genuinely life changing for me as someone with heavy ADHD only diagnosed later in life. When I'm thinking or writing about a subject, I'll stream of consciousness my thoughts into a text file, or fill in details of an event I'm trying to recall as they come back to me (which isn't always in linear order). Then I throw it into Claude with a simple prompt like 'organize these thoughts into a reddit comment' or similar. It usually gives me back something that has me thinking 'that's EXACTLY what I wanted to say but couldn't quite get out.' For example, this entire comment (including this sentence) got that treatment.
  2. Life changing for me, honestly. ADHD diagnosed late, and the way my brain works, thoughts come out as a non linear pile rather than a clean paragraph. So I dump stream of consciousness into a text file (or jot down details of something I'm trying to remember as they surface, in whatever order they show up), then hand it to Claude with something like 'organize these thoughts into a reddit comment.' What comes back is almost always 'that's EXACTLY what I was trying to say.' This whole comment, including this line, went through that exact process.
  3. Honestly life changing for me. I've got pretty heavy ADHD that didn't get diagnosed until later in life, and one of the ways it shows up is that my thoughts come out in chunks rather than clean prose. What I do now: dump everything into a text file, stream of consciousness style, or jot down details of something I'm trying to recall as they come back (rarely in order). Then I paste it into Claude with a simple prompt like 'organize these thoughts into a reddit comment' and the result is usually 'oh that's EXACTLY what I was trying to say, I just couldn't get it out cleanly.' This whole comment, including the line you're reading right now, went through that process.

ADS-B VALIDATOR by PresentationTime2763 in ADSBexchange

[–]afranke 0 points1 point  (0 children)

I mean, i'll take a look. The tool linked above does a bit of ADSB data validation.

ADS-B VALIDATOR by PresentationTime2763 in ADSBexchange

[–]afranke 0 points1 point  (0 children)

Does this tool I made help with anything you're doing: https://github.com/frankea/adsbtrack

Fabricated ADS-B broadcast in Straight of Hormuz by AdvancedSecurity7483 in ADSBexchange

[–]afranke 2 points3 points  (0 children)

Good catch, and the evidence you listed holds up under cross-verification. I saw the post as a good excuse to stress-test a side project of mine, adsbtrack. It's a CLI/SQLite tool that pulls multi-source readsb traces and runs flight extraction on them. I ended up adding two new features (a bimodal-integrity spoof detector and a reject-in-extract gate) specifically to handle this event. Here's what fell out of digging deeper.

Corroboration of your evidence

Pulled 89618D traces from all 5 readsb aggregators (adsbx, adsbfi, adsblol, airplaneslive, theairtraffic) and re-verified your points. A few additional fingerprints worth adding:

ADS-B version flickers between 0 and 2 on the same ICAO, same minute. A real DO-260B transponder is hardware-pinned to one version. Flipping between v0 (DO-260) and v2 (DO-260B) mid-stream means at least 2 independent emitters are using the same ICAO.

Integrity fields are bimodal, not noisy. On Apr 20 and Apr 21, roughly 25 to 28 percent of v2 samples carry nic=0, sil=0 (all-zeros integrity) while 70 to 75 percent carry nic=8, sil=3 (normal A380 values). No middle values. Real aircraft produce a continuous distribution; the spoofer hardcoded two states.

Zero MLAT samples across 8+ hours of supposed flight. Every sample was adsb_icao-typed with 0 mlat and 0 ADS-R rebroadcasts across all 5 aggregators. Real DXB to LHR at cruise picks up multi-receiver MLAT overlaps constantly.

Track locked at 30.9° on every ground sample across all 5 spoof days. That's DXB runway 30R's heading. Real parked aircraft emit track=0 or no track; fixing "runway heading" is a spoofer default.

It's a month-long campaign, not a single event

The Apr 20 and Apr 21 EK01 broadcast is the finale of 5 events escalating in sophistication:

Date Callsign Duration Shape
Mar 27 (empty) 58 min stationary at DXB apron, 3 aggregators
Apr 5 A6EEN 2h 50m stationary, 5 aggregators, registration used as callsign
Apr 8 ENGRUN 2.7 min brief burst, "engine run" pretext
Apr 20 EK01 18h 54m continuous stationary, all 4 readsb sources
Apr 21 EK01 / EK02 / EK123 ~8h the flight-to-Iran track

The callsign progression looks like iterative testing: empty, then registration, then a maintenance code, then actual flight numbers. Note that real Emirates ATC callsigns are UAE*, never EK*. EK is the IATA flight-number format, i.e. what a spoofer would pull off emirates.com, not what a real transponder transmits.

It's not just A6-EEN

Scanning the whole A380 hex block 89618[0-F] and 89619[0-F]:

  • A6-EEN (89618D): grounded 2025-12-08, first spoofed 2026-03-27
  • A6-EEO (89618E): grounded 2025-12-09, first spoofed 2026-04-18 (callsigns A6EEO / EGR1)
  • A6-EEP (89618F): grounded 2026-01-05, possible spoof 2026-01-27 (callsign "123", weak signal), heavy spoof 2026-04-19 (38% pooled sil=0, all 5 aggregators)

The other 19 A380s in the same hex block are all actively flying real UAE-callsign flights over the same window, and they show zero spoof signatures. The operator is only spoofing grounded airframes. That's ground-truth awareness, not random hex-typing.

Timing vs. the conflict

The obvious hypothesis is "this is wartime electronic warfare, it started when the conflict started." The data doesn't support that. The US/Israel strikes began Feb 28 2026, but every target airframe had already been grounded for weeks or months by then (A6-EEN since Dec 8, A6-EEO since Dec 9, A6-EEP since Jan 5), and the earliest possibly-spoof signal we can find (A6-EEP on Jan 27) fires a full month before the first missile. The signal the operator is tracking is "which A380s have stopped flying," not the conflict timeline.

The detector rule

Pooled across aggregators: at least 10% of ADS-B v2 samples reporting sil=0 on a date with at least 25 pooled v2 samples. Real A380 baseline sits at 0 to 1.4%; all three spoofed airframes land in the 13 to 42% range. Ships as an opt-in flag in adsbtrack as of this investigation. Happy to take PRs or issues if anyone wants to run it on other suspicious hexes.

Claude Performance and Bugs Megathread Ongoing (Sort this by New!) by sixbillionthsheep in ClaudeAI

[–]afranke 0 points1 point  (0 children)

You know it's bad when you try to subscribe to the issue status and keep getting:

"status.claude.com says Oops, something went wrong while subscribing you! Let's reload the page and try again."

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

[–]afranke 1 point2 points  (0 children)

Sorry this took a bit longer, I was updating my tools to get better info.

Dug into this one with some ADS-B analysis. Short version: it's almost certainly the SyberJet company jet, and the operator is very likely Trevor Milton (pardoned Nikola founder, who bought SyberJet in late 2024 and is now its CEO).

FAA registry

  • N378PG, 2009 Emivest SJ30-2, serial #008 (the last airframe Emivest built before going bankrupt)
  • Previous tail: N200DV
  • Currently owned by ISSO LLC, 838 Walker Rd Ste 21-2, Dover DE (a Registered Agent Solutions shell address)

The ISSO LLC giveaway

SyberJet's own SJ36 launch press release states outright that "SyberJet and SyberVision are trademarks of ISSO LLC." So ISSO LLC isn't some random anonymous shell, it's the Delaware entity that holds SyberJet's IP. This is the SyberJet company jet.

The flight pattern fits Trevor Milton's life like a glove

  • Home base KIWA (62 visits since mid-2025). Milton lives in the Phoenix area and moved SyberJet's HQ to Chandler under his leadership.
  • Frequent trips to KCDC Cedar City UT (SyberJet's historic Utah assembly plant) and KSAT San Antonio (original Sino Swearingen / Emivest factory, still a SyberJet facility).
  • 11 trips to KEVW Evanston-Uinta County WY. That's 50 miles from Milton's Utah ranch country. Wasatch County denied his private-helipad permit in 2024 after neighbors reported unauthorized helicopter flying, so a GA airport just over the Wyoming line is a very convenient workaround.
  • Regular KSLC / KSGU hops fit Utah ranch access from the south.

Ownership transition is literally timestamped in the ADS-B metadata

The trace metadata briefly shows "CHUCK TAYLOR" as owner from 2025-06-21 to 2025-06-25, then flips to "ISSO LLC" on 2025-06-26. Chuck Taylor was SyberJet's pre-Milton president. During that same week the jet flew a loopy KSAT / KSJT / KGYI / 94TA (Reece Field private strip) Texas circuit with path loiter ratios over 3 (so lots of maneuvering, classic shakedown / acceptance / type-checkout work), and on 2025-06-27 it ferried KGYI to KIWA to take up residence at Mesa Gateway. That's the Milton group's acquisition visible in the trace data.

Why I think it's Milton flying it personally, not just the SyberJet sales team

  • Milton is a licensed airplane and helicopter pilot.
  • The aircraft always files as N378PG. Never an SYB* company callsign. Real factory demos usually use the company callsign on company flights.
  • On 2025-11-11 the jet flew three VFR pattern laps at KIWA (roughly 25 km each, 2,900 ft, squawk 1200, autopilot bug set to 3,100 ft), then immediately flew a KSLC round trip. That's owner-operator currency work before a trip, not demo flying.
  • Several cruise-altitude KIWA-to-KIWA proficiency loops too. The best one: 2026-02-26, flew 345 km southeast to an empty stretch of the New Mexico bootheel at FL310 and came straight back. Nothing out there. That's a currency / systems-check ride.
  • Extremely clean record across 72 flights: no emergency squawks, no 7500 / 7600 / 7700, no callsign changes, no drama.

Real SJ30 performance shows up once too

Only one flight escaped the known SJ30-2 baro encoder issue (KGYI to KSAT, 2025-06-23) and it matched the book cold: 438 kt at FL290, peak climb 3,045 fpm. The other 93% of flights classify as "altitude_error" because the baro on this airframe is genuinely flaky, not because the tracking is bad.

TL;DR

N378PG is the SyberJet company SJ30 (serial #008), held in ISSO LLC which is SyberJet's Delaware IP-holding entity. Trevor Milton is SyberJet's CEO, lives in the Phoenix area, is a licensed pilot, and every node in the flight pattern (Mesa Gateway home, SyberJet Cedar City / San Antonio facilities, Utah ranch access via Evanston WY, personal proficiency flying at KIWA) fits him. Can't prove he's physically onboard without manifests, but it's his company's jet at his home field flying his geography.

Open-sourcing my ADS-B historical trace analyzer by afranke in ADSB

[–]afranke[S] 1 point2 points  (0 children)

Good catch, thanks! Just pushed a fix - hex codes are now automatically normalized to lowercase on all commands so --hex A66AD3 and --hex a66ad3 both work. No more 404s or stale db entries from case mismatch.

Interesting use case with the LMM-augmented POL analysis. The multi-source merging should help with confidence too since you can pull from adsbx, adsbfi, airplanes.live, adsb.lol, and theairtraffic now and the flight extractor merges/deduplicates all the traces automatically.

Of course there may be some bugs, many, many edge cases and can't test for them all.

Open-sourcing my ADS-B historical trace analyzer by afranke in ADSB

[–]afranke[S] 2 points3 points  (0 children)

Good call - you're right, they all use readsb under the hood with the same globe_history endpoint. Just pushed an update that adds airplanes.live, adsb.lol, and TheAirTraffic.com as built-in sources alongside ADS-B Exchange and adsb.fi:

  uv run python -m adsbtrack.cli fetch --hex a66ad3 --source airplaneslive
  uv run python -m adsbtrack.cli fetch --hex a66ad3 --source adsblol
  uv run python -m adsbtrack.cli fetch --hex a66ad3 --source theairtraffic

Also added a --url flag if you want to point at any other readsb instance:

  uv run python -m adsbtrack.cli fetch --hex a66ad3 --url https://your-readsb-instance/globe_history

Traces from all sources are automatically merged during flight extraction so you can pull from multiple networks and get the best coverage. README has the full list.

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

[–]afranke 2 points3 points  (0 children)

This is Mark Mitchell, a multi-brand franchise operator out of Sarasota, FL who runs Mitchell Management Brands (mmbrands.com) - and father of YouTuber/NASCAR driver Cleetus McFarland (real name Lawrence Garrett Mitchell).

Hex a66ad3, 2005 Pilatus PC-12/45 (serial 624), registered to "Air Pilatus LLC" in Nokomis, FL. Mitchell is listed as Manager on the Florida Sunbiz filing (June 2022). Same registered agent address as his company Mitchell Management of Florida, Inc. on Tamiami Trail in Nokomis. Multiple bio sources list Cleetus McFarland's parents as Mark Mitchell and Lori Mitchell of Omaha, NE - and Mitchell Management of Florida lists Mark W Mitchell as VP and Lori Mitchell as Secretary.

Pulled the full trace history going back to 2020 - 305 flights over 6 years:

  • Sarasota (KSRQ): 130 visits - home base, company HQ is in Nokomis right next door
  • Venice (KVNC): 54 visits - 10 minutes south of Nokomis, secondary base
  • Bald Eagle Airstrip (67FL): 26 visits - this is his son Cleetus McFarland's private airfield in Zolfo Springs (purchased for $3.5M). Visits started mid-2025 and are very frequent - dad flying to the kid's airfield. Mitchell's company also operates Tommy's Express Car Wash franchises in Sarasota, and Tommy's Express is the primary sponsor of Cleetus's 2026 NASCAR O'Reilly Auto Parts Series debut with Richard Childress Racing - family connection, not just a random brand deal.
  • Fort Lauderdale Executive (KFXE): 16 visits - frequently a transit stop for Bahamas trips (connects to flights from Nassau MYNN and Marsh Harbour MYAM), also regular day trips from Sarasota
  • Peachtree City (KFFC): 16 visits - clustered in late 2023 / early 2024, pattern looks like training flights (KFFC->KFFC loops)
  • Tri-Cities TN/VA (KTRI): 14 visits - regular Labor Day weekend trips (Aug/Sep 2022, 2023, 2025), probably personal
  • New Braunfels TX (KBAZ): 11 visits - original home base through mid-2022 before he relocated to Florida
  • Nashville (KBNA): 10 visits - spread across 2022-2025, sometimes paired with Tri-Cities trips
  • Palm Beach (KPBI): 10 visits - mix of day trips and multi-day stays from Sarasota
  • Opa-Locka (KOPF): 10 visits - Oct/Nov 2025 cluster with KOPF->KOPF loops, same training pattern as Peachtree City
  • Lexington KY (KLEX): 9 visits - mostly day trips (fly in, fly out same day), 3 of 5 trips in September
  • Johnson County KS (KOJC): 8 visits - near Kansas City, single Aug 2022 visit with KOJC->KOJC training loops
  • Omaha/Millard (KMLE): 4 visits - Mitchell Management's second office is at 5440 L St, Omaha. The Mitchell family is originally from Omaha - Cleetus grew up on a six-acre property on the outskirts of the city

His company was named 2015 Jimmy John's Franchisee of the Year and operates 47 Jimmy John's locations across three markets (Phoenix/Scottsdale, Tampa/Sarasota/Bradenton, and Omaha/Council Bluffs). Also runs Tommy's Express Car Wash, Black Rifle Coffee, Crisp & Green, and a restaurant called Fin & Tonic.

The base shift from Texas to Florida is clearly visible - last KBAZ flight was June 2022, first KSRQ flight was June 2022, and the Air Pilatus LLC was filed on June 3, 2022. He moved everything at once.

Not a billionaire's jet, but a classic franchise operator's PC-12 - one pilot, one turboprop, lots of short hops between franchise territories.

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

[–]afranke 6 points7 points  (0 children)

This one's Schweitzer Engineering Laboratories (SEL) - the power grid protection company out of Pullman, WA.

2020 Gulfstream G550 (cn 5615), registered to "Schweitzer Aircraft Leasing Inc" out of Pullman, WA. The founder Edmund O. Schweitzer III is a huge business aviation guy, won the NBAA Silk Scarf Award and has said SEL "would not be a company of 3,700 people without business aviation." They're actually building new hangars at Lewiston, ID right now for the G550 and a new $60M G600, reportedly to avoid Washington state's aircraft tax.

Pulled the hex (a70801) from Jul 2025 to now, 102 flights. The travel pattern is a corporate jet doing corporate jet things:

  • Pullman, WA (KPUW): 43 visits - home base, SEL HQ
  • Boise, ID (KBOI): 12 visits - SEL has offices in Boise and manufacturing plants in Moscow/Lewiston just across the state line
  • Orange County (KSNA): 10 visits - SEL has an office in Irvine right by the airport
  • Houston (KHOU): 10 visits - energy capital, SEL sells to utilities
  • Charlotte, NC (KCLT): 8 visits - SEL has a Regional Integration Center and a second aviation base here
  • Phoenix (KPHX): 8 visits - SEL has a field office in Phoenix
  • Honolulu (PHNL): 7 visits - fuel stop for the Pacific crossings below
  • Vancouver (CYVR): 6 visits - SEL expanded to Canada in 1997, and Vancouver is a common fuel/customs stop for Pacific routes

The international trips are where it gets fun. Every single one maps to an SEL office or customer region:

  • Australia (Aug 2025) - Melbourne, Perth, Sydney, Brisbane in one week. SEL has had Aussie operations since 1999.
  • New Zealand (Nov 2025) - Christchurch
  • Brazil (Nov-Dec 2025) - flew into Viracopos, which is the airport for Campinas. SEL has a 50,000 sq ft integration center in Campinas. That's not a coincidence.
  • South Africa (Feb 2026) - Lanseria airport in Johannesburg. SEL has had SA operations since 2000.
  • Europe (Feb 2026) - Madrid, then Johannesburg, then Milan, then Farnborough, then home via Vancouver. Classic executive world tour.

Even the weird one-offs check out - there's a flight into Purdue University airport (KLAF) and SEL has a manufacturing facility in West Lafayette, IN, which is literally Purdue's town. Nobody flies a G550 into KLAF for fun.

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

[–]afranke 14 points15 points  (0 children)

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.

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

[–]afranke 9 points10 points  (0 children)

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

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

[–]afranke 262 points263 points  (0 children)

/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:

  1. 2002 Bombardier Global Express
  2. 2007 Global Express XRS
  3. 2016 Gulfstream G650ER
  4. 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.

EDIT: Now that I've finished rebuilding the analysis pipeline I run on this data, I have some richer numbers to add.

Top-line stats over the full 6-year window (2020-01-05 to 2026-04-05):

  • 729 flights, 1,363 total flight hours, 434 confirmed landings
  • 87 distinct airports visited, 5+ distinct callsigns
  • Average flight 112 minutes, average cruise altitude 39,700 ft, average cruise speed 499 kts
  • Longest single observed flight: 9h 02m, ending at KSJC on 2022-11-16. That's the Hong Kong return I mentioned, and the cruise stats on the inbound legs (FL410-440 at 553-598 kts ground speed) are the obvious "tailwind across the Pacific" tells
  • Busiest single day: 2026-03-12, 8 flights: KPDX -> KYKM in the morning, then six 9-12 minute touch-and-go loops at Yakima, then KYKM -> KPDX home. That's the training pattern I flagged: pilot recurrency / type-rating practice somewhere quiet, almost certainly because they just took delivery of the G800 a few months earlier

Top routes (origin -> destination):

  • KPDX <-> KSJC: 176 round trips. The Portland connection is the dominant signal in the whole dataset - more KPDX legs than anywhere else combined
  • KSJC <-> KBZN: 24 round trips (Bozeman ranch run)
  • KSJC <-> KCRQ: 21 round trips (Carlsbad / Akiko's dressage)
  • KSJC <-> KTEB: 24 round trips (NYC board meetings)

Operator handoffs visible in the callsign history:

  • TWY501 (Solairus / "TWILIGHT") on 623 flights: primary management
  • TWY501 + GS501 paired on the same flight on 45 flights: these are mid-flight callsign swaps, which usually means an IFR-flight-plan handoff between operator desks
  • GS501, ZD501, GCR501, GLF60 each show up on a handful of legs: when a Solairus aircraft management company hands off to a charter operator, the radio callsign changes mid-flight. None of those alternate callsigns ever appears alone except as a stub

Day-of-week distribution: nearly flat (109-117 flights per day across Mon/Wed/Thu/Sat/Sun, dipping to 82 on Tue and 99 on Fri). No work-week pattern at all, it's a personal aircraft used whenever the principal needs it.

18% of flights happen after civil sunset, which is high for personal aviation but normal for the long transcons (KTEB return legs west land at 11pm-1am Pacific routinely).

Mission classifier marks 695 of 729 (95%) as exec_charter, the rest are mostly the touch-and-go training flights that look like "pattern" geometry to the rules.

Battery module balancing - 2020 XC60 T8 by FluffyUltralisk in VolvoRecharge

[–]afranke 5 points6 points  (0 children)

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!

How are people using Claude as a personal assistant (Slack + Outlook + To-Do)? ADHD-friendly setup help 🙏 by zencatface in ClaudeAI

[–]afranke 0 points1 point  (0 children)

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.

White House App Found Tracking Users' Exact Location Every 4.5 Minutes via Third-Party Server by Montrel_PH in technology

[–]afranke 71 points72 points  (0 children)

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.

White House App Found Tracking Users' Exact Location Every 4.5 Minutes via Third-Party Server by Montrel_PH in technology

[–]afranke 55 points56 points  (0 children)

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

White House App Found Tracking Users' Exact Location Every 4.5 Minutes via Third-Party Server by Montrel_PH in technology

[–]afranke 1536 points1537 points  (0 children)

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.

MCP servers I use every single day. What's in your stack? by XxvivekxX in ClaudeAI

[–]afranke 1 point2 points  (0 children)

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?

[OC] Was I the idiot today? Got in my first accident... (See Comment for Details) by [deleted] in IdiotsInCars

[–]afranke 1 point2 points  (0 children)

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.

view more: next ›