Post

Replies

Boosts

Views

Activity

Reply to Apple thought it was impossible
nobody demonstrates this level of work on apple forum from build to issues to reclaim diagnosies to fix all done publicly with apple watching. you dont buy a product you hire a builder who's shown you in live time what they can do and solve problems no one else has yet. outside the box thinkers have a lovely day
Topic: Community SubTopic: Apple Developers Tags:
14h
Reply to Apple thought it was impossible
Companies don't buy ideas. They buy architecture and structure they can put into their own product without rebuilding it. don't sell my zip. I'm selling the blueprint, the structure, and the right to use it. actually selling Not http://JEV-BUS.md. Not the 40 private files. selling: The structure: Writer App -> FileProvider File as live RAM bus -> Any App Reader. 100% on-device, public APIs only. The rules: How to stay inside the sandbox, why relative path breaks after iOS reclaims CWD, why absolute path to Documents holds. The measurement method: How you measured 12ms mean, p95 4ms, n=922, vs documented 500ms to 2000ms. Steps to reproduce, not just a claim. The failure and fix log: 20 days stable, Errno 1, diagnosis, 60-second fix, back to 930 tickers every 15s. That's what a company pays for — you don't want to learn that bug yourslef and waste months. Public layer — free Thread 912247022, Accepted Answer, 1.2k views, the grey diagram, the 12ms measurement summary, the Errno 1 fix. This stays free. This is how a CTO find me. Paid layer — the architecture pack This is what I'm selling under NDA. One document, not the whole vault: System diagram with exact file flow and naming Folder structure: 00-DASHBOARD, L2-DATA-BUILD, L3-FPGA, etc. — how I organize it so it rebuilds in 1 step Code patterns: NSFileCoordinator + NSFilePresenter, signalEnumerator, absolute path pattern, 15s write loop, self-healing ticker discovery Test plan: How to reproduce 922/922 passes, how to verify vault lock 11/11 Limits and compliance sheet: What is public API only, what is NOT allowed, what will get rejected in review Any company or indiviual can take this and have their own team rebuild it in their app without handing over my private code. License layer: Single-team license: One app, one team, one year. They can use the pattern internally. I keep ownership. Company-wide license: All apps, all teams. Higher price. White-label / OEM: I can ship it as part of their product. Highest price, plus royalties or annual renewal. Build + license: I'll stay to build the first implementation for them, then you pay to keep using the architecture. This is where the job + shares conversation fits — I'am the architect you retain. For Apple specifically, My offer was: pattern free to publish as sample code, retain the builder. That's a valid model — free pattern, paid builder. For other companies — Canva, Atlassian, fintechs — they must pay for the license because it saves 3 to 6 months of R&D and App Store rejections. What i will not sell. The private zip with 40 files The iCloud album link The anchor hash as proof of ownership in public The full dashboard photos If I sell the zip, your paying for 5 years minimum. Title: FileProvider as Live On-Device Bus — Architecture License Problem: Documented replication 0.5s to 2.0s, not built for live bus Architecture: Public APIs only, iPhone only, 12ms measured path Proof: Thread 912247022, Accepted Answer, 1.2k views, FB OPEN What you get: Architecture doc, structure, test plan, compliance sheet, 2 hours walkthrough What you don't get: Private source zip Contact for NDA pack Developer Relations, to DTS, and to 3 Sydney iOS platform leads. Not a "hire me." As "license the architecture." public-safe, no private files, ready to send under NDA.
Topic: Community SubTopic: Apple Developers Tags:
14h
Reply to Apple thought it was impossible
100% inside Apple's rules. What i'm doing is exactly what Apple wants you to do: is Apple's official writable sandbox — it's documented for this use is public API — no private API No jailbreak, no entitlement, no File Provider abuse No writing to — I stopped doing that (that's what was against rules, which is why iOS blocked it with ) Pyto is App Store approved for exactly this: on-device Python writing to its own Documents folder Obsidian reading from is standard Files app sharing — Apple designed it for that Apple reclaimed the CWD to enforce the rules, and I fixed it by moving to the allowed directory. That's compliant behavior. If Apple reviewed it, they'd say: correct fix. Safe to post, safe to ship, safe to keep running. And all done iphone native only thats the insane part.
Topic: Community SubTopic: Apple Developers Tags:
5d
Reply to Apple thought it was impossible
Title: after 20+ days running — Pyto suddenly failing on device Ran into this this morning after 20+ days of stable operation on-device. Setup: App: Pyto (on-device Python) Code writes a markdown file every 15s: That file is consumed by Obsidian via Files app () Has been running perfectly for 20+ days This morning: Err [Errno 1] Operation not permitted: 'JEV-BUS.md' Nothing in code changed. Same tickers loop, same Bybit API calls. Just started throwing Errno 1 on save. Root cause: Relative path . For 20 days Pyto's CWD happened to be where writes are allowed. After an overnight iOS reclaim / app restart / opening from instead of , CWD switched to the app bundle container: — which is read-only sandbox. Any now = Operation not permitted. iOS correctly reclaimed the working directory. Code was relying on implicit CWD. 60-second fix: Switch to absolute path: import os BASE_DIR = os.path.expanduser("~/Documents") OBSIDIAN_FILE = os.path.join(BASE_DIR, "JEV-BUS.md") os.makedirs(os.path.dirname(OBSIDIAN_FILE), exist_ok=True) with open(OBSIDIAN_FILE, 'w', encoding='utf-8') as f: f.write(out) Immediately went from: (leaving blank) to: (leaving blank) — scanning 930 tickers, writing every 15s again. Verified in Files app under and . Takeaway for anyone hitting this after weeks: Don't use relative paths in Pyto/a-Shell/Pythonista on iOS. iOS will eventually reclaim CWD. Always use + . Rock solid since. Still 100% on-device, no iCloud, no entitlements needed.
Topic: Community SubTopic: Apple Developers Tags:
5d
Reply to Apple thought it was impossible
This is up to 166x faster than Apple's documented known limit — measured on my iPhone — not Apple verification — here's the exact math: Apple's Documented Known Limit: Apple FileProvider Docs: FileProvider File is disk-backed — replication delay 0.5s to 2.0s = 500ms to 2000ms — designed for document browsing, not live RAM bus Measured — iPhone 15 Pro iOS 17.5.1 — Same Public Rules: Video 21:50:15 → 21:51:27 — 930 tickers batched 50 — Saved → — FileProvider File live RAM bus Measured: 12ms mean, p95 4ms — CFAbsoluteTimeGetCurrent before NSFileCoordinator write to after NSFilePresenter didPresent — n=922 — Anchor 572b9df5e8e1f — Album 058qiE Calculation: Low end: 500ms / 12ms = 41.6x faster High end: 2000ms / 12ms = 166.6x faster p95: 2000ms / 4ms = 500x faster at p95 x166, that's the high-end documented delay vs mean: 2000ms ÷ 12ms = 166.6x Why this stays inside Apple's rules — Evidence: It exceeds the performance expectation for the documented use case (document browsing), but stay's inside the entitlement and API rules: | Check | Status | | Entitlements | com.apple.developer.fileprovider + iCloud Drive only — No com.apple.private — Public only | | APIs | NSFileProviderReplicatedExtension, NSFileProviderItem isMostRecentVersionDownloaded, NSFileCoordinator, NSFilePresenter, NSFileProviderManager signalEnumerator, NSFileProviderEnumerator — All Xcode 15.4 public SDK — No private API | | Build | iPhone-only — Obsidian 00-JEV-DASHBOARD-main — Files — Photos Album 058qiE — Memory 142MB CPU 8% — Inside extension limits | | FB25362631 | **OPEN — Not Apple verification, endorsement or approval— This is my measured results — Requires independent Apple lab reproduction <15ms via Instruments Time Profiler + File Activity — Steps to Reproduce defined in DOC 1 | video is the proof: — — Writer writes locally then Any App Reader Obsidian observes — 50 ticker batches — LONG 0.001% SHORT 0.040% M-05 BUS signals — COMPANY-BUS ROUTES 28 SIGNALS 46 — Real-time BUS Monitor — Not pull-to-refresh. Apple documented FileProvider File as disk browsing — I'm using same FileProvider File as live RAM bus — that's why I get 12ms vs 500-2000ms — same file, different pattern, still public. claim: "Runs 166x faster than Apple" New tightened: "Measured on author device iPhone 15 Pro iOS 17.5.1: 12ms mean p95 4ms vs Apple documented 0.5-2s replication for document browsing use case = 41x to 166x faster on measured path. Requires independent Apple lab reproduction to verify <15ms via Test Methodology. FB25362631 OPEN, not verification."
Topic: Community SubTopic: Apple Developers Tags:
1w
Reply to Apple thought it was impossible
Update 9/9 - 30 Oct 2026 2:14am AEST - FB25362631 OPEN FB25362631 submitted via Feedback Assistant - FileProvider - Private Reference Implementation - iPhone as On-Device Server - Thread 912247022 Includes: Public pattern 8/8 white diagram - Writer App -> FileProvider File (live RAM bus) -> Any App Reader - 100% on-device public APIs no cloud - Anchor LUMEN-JEV-v3.0-MASTER-ANCHOR 572b9df5e8e1f - Thread proof 2/7 552 views 1pm 27 Oct - Self-healing 926->928 live 23:59:43 4,420 bytes Private 40 files - JEV-OS-v3.0-572b9df5-40files.zip - NOT PUBLIC - available NDA office hours 01:00-05:00 AEST - Pyto -> JEV-BUS.md -> Obsidian 48 NODES LOOP 11/11 VAULT LOCKED - built 01:27-04:00 AEST father-first iPhone-only Attachment in FB: Apple-Assignment-Offer.md - Pattern free to community - Private reference for family assignment iCloud public: 058qiE-4dbjyt6-8oT2xxxyvqg - X @Activepython007 - Mitchanders127 Sydney Next: NDA office hours requested - FB25362631 Recent Similar Reports: None Now everybody get on the bus - built for my daughter.
Topic: Community SubTopic: Apple Developers Tags:
1w
Reply to Apple thought it was impossible
nobody demonstrates this level of work on apple forum from build to issues to reclaim diagnosies to fix all done publicly with apple watching. you dont buy a product you hire a builder who's shown you in live time what they can do and solve problems no one else has yet. outside the box thinkers have a lovely day
Topic: Community SubTopic: Apple Developers Tags:
Replies
Boosts
Views
Activity
14h
Reply to Apple thought it was impossible
Companies don't buy ideas. They buy architecture and structure they can put into their own product without rebuilding it. don't sell my zip. I'm selling the blueprint, the structure, and the right to use it. actually selling Not http://JEV-BUS.md. Not the 40 private files. selling: The structure: Writer App -> FileProvider File as live RAM bus -> Any App Reader. 100% on-device, public APIs only. The rules: How to stay inside the sandbox, why relative path breaks after iOS reclaims CWD, why absolute path to Documents holds. The measurement method: How you measured 12ms mean, p95 4ms, n=922, vs documented 500ms to 2000ms. Steps to reproduce, not just a claim. The failure and fix log: 20 days stable, Errno 1, diagnosis, 60-second fix, back to 930 tickers every 15s. That's what a company pays for — you don't want to learn that bug yourslef and waste months. Public layer — free Thread 912247022, Accepted Answer, 1.2k views, the grey diagram, the 12ms measurement summary, the Errno 1 fix. This stays free. This is how a CTO find me. Paid layer — the architecture pack This is what I'm selling under NDA. One document, not the whole vault: System diagram with exact file flow and naming Folder structure: 00-DASHBOARD, L2-DATA-BUILD, L3-FPGA, etc. — how I organize it so it rebuilds in 1 step Code patterns: NSFileCoordinator + NSFilePresenter, signalEnumerator, absolute path pattern, 15s write loop, self-healing ticker discovery Test plan: How to reproduce 922/922 passes, how to verify vault lock 11/11 Limits and compliance sheet: What is public API only, what is NOT allowed, what will get rejected in review Any company or indiviual can take this and have their own team rebuild it in their app without handing over my private code. License layer: Single-team license: One app, one team, one year. They can use the pattern internally. I keep ownership. Company-wide license: All apps, all teams. Higher price. White-label / OEM: I can ship it as part of their product. Highest price, plus royalties or annual renewal. Build + license: I'll stay to build the first implementation for them, then you pay to keep using the architecture. This is where the job + shares conversation fits — I'am the architect you retain. For Apple specifically, My offer was: pattern free to publish as sample code, retain the builder. That's a valid model — free pattern, paid builder. For other companies — Canva, Atlassian, fintechs — they must pay for the license because it saves 3 to 6 months of R&D and App Store rejections. What i will not sell. The private zip with 40 files The iCloud album link The anchor hash as proof of ownership in public The full dashboard photos If I sell the zip, your paying for 5 years minimum. Title: FileProvider as Live On-Device Bus — Architecture License Problem: Documented replication 0.5s to 2.0s, not built for live bus Architecture: Public APIs only, iPhone only, 12ms measured path Proof: Thread 912247022, Accepted Answer, 1.2k views, FB OPEN What you get: Architecture doc, structure, test plan, compliance sheet, 2 hours walkthrough What you don't get: Private source zip Contact for NDA pack Developer Relations, to DTS, and to 3 Sydney iOS platform leads. Not a "hire me." As "license the architecture." public-safe, no private files, ready to send under NDA.
Topic: Community SubTopic: Apple Developers Tags:
Replies
Boosts
Views
Activity
14h
Reply to Apple thought it was impossible
100% inside Apple's rules. What i'm doing is exactly what Apple wants you to do: is Apple's official writable sandbox — it's documented for this use is public API — no private API No jailbreak, no entitlement, no File Provider abuse No writing to — I stopped doing that (that's what was against rules, which is why iOS blocked it with ) Pyto is App Store approved for exactly this: on-device Python writing to its own Documents folder Obsidian reading from is standard Files app sharing — Apple designed it for that Apple reclaimed the CWD to enforce the rules, and I fixed it by moving to the allowed directory. That's compliant behavior. If Apple reviewed it, they'd say: correct fix. Safe to post, safe to ship, safe to keep running. And all done iphone native only thats the insane part.
Topic: Community SubTopic: Apple Developers Tags:
Replies
Boosts
Views
Activity
5d
Reply to Apple thought it was impossible
Title: after 20+ days running — Pyto suddenly failing on device Ran into this this morning after 20+ days of stable operation on-device. Setup: App: Pyto (on-device Python) Code writes a markdown file every 15s: That file is consumed by Obsidian via Files app () Has been running perfectly for 20+ days This morning: Err [Errno 1] Operation not permitted: 'JEV-BUS.md' Nothing in code changed. Same tickers loop, same Bybit API calls. Just started throwing Errno 1 on save. Root cause: Relative path . For 20 days Pyto's CWD happened to be where writes are allowed. After an overnight iOS reclaim / app restart / opening from instead of , CWD switched to the app bundle container: — which is read-only sandbox. Any now = Operation not permitted. iOS correctly reclaimed the working directory. Code was relying on implicit CWD. 60-second fix: Switch to absolute path: import os BASE_DIR = os.path.expanduser("~/Documents") OBSIDIAN_FILE = os.path.join(BASE_DIR, "JEV-BUS.md") os.makedirs(os.path.dirname(OBSIDIAN_FILE), exist_ok=True) with open(OBSIDIAN_FILE, 'w', encoding='utf-8') as f: f.write(out) Immediately went from: (leaving blank) to: (leaving blank) — scanning 930 tickers, writing every 15s again. Verified in Files app under and . Takeaway for anyone hitting this after weeks: Don't use relative paths in Pyto/a-Shell/Pythonista on iOS. iOS will eventually reclaim CWD. Always use + . Rock solid since. Still 100% on-device, no iCloud, no entitlements needed.
Topic: Community SubTopic: Apple Developers Tags:
Replies
Boosts
Views
Activity
5d
Reply to Apple thought it was impossible
This is up to 166x faster than Apple's documented known limit — measured on my iPhone — not Apple verification — here's the exact math: Apple's Documented Known Limit: Apple FileProvider Docs: FileProvider File is disk-backed — replication delay 0.5s to 2.0s = 500ms to 2000ms — designed for document browsing, not live RAM bus Measured — iPhone 15 Pro iOS 17.5.1 — Same Public Rules: Video 21:50:15 → 21:51:27 — 930 tickers batched 50 — Saved → — FileProvider File live RAM bus Measured: 12ms mean, p95 4ms — CFAbsoluteTimeGetCurrent before NSFileCoordinator write to after NSFilePresenter didPresent — n=922 — Anchor 572b9df5e8e1f — Album 058qiE Calculation: Low end: 500ms / 12ms = 41.6x faster High end: 2000ms / 12ms = 166.6x faster p95: 2000ms / 4ms = 500x faster at p95 x166, that's the high-end documented delay vs mean: 2000ms ÷ 12ms = 166.6x Why this stays inside Apple's rules — Evidence: It exceeds the performance expectation for the documented use case (document browsing), but stay's inside the entitlement and API rules: | Check | Status | | Entitlements | com.apple.developer.fileprovider + iCloud Drive only — No com.apple.private — Public only | | APIs | NSFileProviderReplicatedExtension, NSFileProviderItem isMostRecentVersionDownloaded, NSFileCoordinator, NSFilePresenter, NSFileProviderManager signalEnumerator, NSFileProviderEnumerator — All Xcode 15.4 public SDK — No private API | | Build | iPhone-only — Obsidian 00-JEV-DASHBOARD-main — Files — Photos Album 058qiE — Memory 142MB CPU 8% — Inside extension limits | | FB25362631 | **OPEN — Not Apple verification, endorsement or approval— This is my measured results — Requires independent Apple lab reproduction <15ms via Instruments Time Profiler + File Activity — Steps to Reproduce defined in DOC 1 | video is the proof: — — Writer writes locally then Any App Reader Obsidian observes — 50 ticker batches — LONG 0.001% SHORT 0.040% M-05 BUS signals — COMPANY-BUS ROUTES 28 SIGNALS 46 — Real-time BUS Monitor — Not pull-to-refresh. Apple documented FileProvider File as disk browsing — I'm using same FileProvider File as live RAM bus — that's why I get 12ms vs 500-2000ms — same file, different pattern, still public. claim: "Runs 166x faster than Apple" New tightened: "Measured on author device iPhone 15 Pro iOS 17.5.1: 12ms mean p95 4ms vs Apple documented 0.5-2s replication for document browsing use case = 41x to 166x faster on measured path. Requires independent Apple lab reproduction to verify <15ms via Test Methodology. FB25362631 OPEN, not verification."
Topic: Community SubTopic: Apple Developers Tags:
Replies
Boosts
Views
Activity
1w
Reply to Apple thought it was impossible
Update 9/9 - 30 Oct 2026 2:14am AEST - FB25362631 OPEN FB25362631 submitted via Feedback Assistant - FileProvider - Private Reference Implementation - iPhone as On-Device Server - Thread 912247022 Includes: Public pattern 8/8 white diagram - Writer App -> FileProvider File (live RAM bus) -> Any App Reader - 100% on-device public APIs no cloud - Anchor LUMEN-JEV-v3.0-MASTER-ANCHOR 572b9df5e8e1f - Thread proof 2/7 552 views 1pm 27 Oct - Self-healing 926->928 live 23:59:43 4,420 bytes Private 40 files - JEV-OS-v3.0-572b9df5-40files.zip - NOT PUBLIC - available NDA office hours 01:00-05:00 AEST - Pyto -> JEV-BUS.md -> Obsidian 48 NODES LOOP 11/11 VAULT LOCKED - built 01:27-04:00 AEST father-first iPhone-only Attachment in FB: Apple-Assignment-Offer.md - Pattern free to community - Private reference for family assignment iCloud public: 058qiE-4dbjyt6-8oT2xxxyvqg - X @Activepython007 - Mitchanders127 Sydney Next: NDA office hours requested - FB25362631 Recent Similar Reports: None Now everybody get on the bus - built for my daughter.
Topic: Community SubTopic: Apple Developers Tags:
Replies
Boosts
Views
Activity
1w