Jacob
281 posts

Jacob
@JZivanDesign
Husband and Father of 5. Author of https://t.co/6kvP36zH0s. Not a social media person, so I'll get back to you later :D
가입일 Şubat 2025
206 팔로잉136 팔로워

@jacobtechtavern The thing that's been driving me nuts lately is how safari will create new windows every time I open a link from a 3rd party app like slack.
English

@joshdholtz Print the document with the words on it with the 3D printer. It will cost more. But it will be cooler
English

alright here’s every practical security tip i have on agents:
- move critical data to a USB stick, unplug when sleeping
- security by least privilege, not by prompts
- billing cap on everything AI touches
- limit reads of external data, wrap in always
- don’t post about what access your agent has publicly - those are prompt injection invitations (unless @levelsio already posted about it, then it’s a race)
- don’t connect to moltbook (lol?)
- roll every skill yourself
- sandbox browser access
- readonly prod access
- allow prod writes only for specific use cases (i have /admin/zoe/* for zoe to handle support cases like credit topups)
- one-time access for anything sensitive (eg gmail) with human in the loop, self-revoke access on script finish
- create dedicated scripts, avoid improvised bash
- use better models
- audit trails everywhere -> security self-improvements
mistakes will happen. limit worst case, embrace the rest

@levelsio@levelsio
This guy has lots of great security tips if you're coding with AI, great follow @elvissun
English

Back home after an amazing @letsvisionos conference!
- Launched a new Agent Skill (see pinned tweet)
- Visited Shanghai's Apple Developer Center
- Presented my best practices for Agent-Driven Development
And yes, we've also been such tourists (see reply)



English

THIS IS NOT ME, STOP SENDING IT TO ME
📜Echoes of Empire📜@EchoesofEmpire_
Archduke Franz Ferdinand posing as a mummy on a trip to Cairo in 1896.
English

@RevenueCat guys, you need to improve the paywall experience for the the web.
While you are pushing the web payment in your marketing efforts, the user experience of it, is half baked imo. examples:
- packages have some kind of conflict with the purchase buttons and needs extra click
- no hover interaction for purchase buttons
- no preview options for the web, only iphone and ipad previews
I love your service, and I'm a fan of you for years. But the user facing web paywall and the developer experience needs your attention.
English

@Fire_At_Will_ I got over 2 feet of snow! Took forever to clear the drive.
English

@JZivanDesign Yesterday was 80 degrees with pollen everywhere. Today? Snow on the blooming azaleas! 🤯

English


I type. I relearned with colemak because qwerty was literally designed to slow down typists when jamming a typewriter was a problem that needed solving.
I don't trust these companies with my biometric data, so I don't dictate.
I type.
It suits me.
I use the moonlander and love this keyboard.
zsa.io/moonlander
English

@MikeWingerii I actually have a second question… what are your thought on Logos' AI features they rolled out with Logos premium?
English

@MikeWingerii I know I'm late to the party. But, it's been something stewing in my brain for a while. There are several instances in where the laying of hands is associated or seemingly a prerequisite of the receiving of the Holy Spirit. What are your thoughts on that?
English

@joshdholtz @DeepDishSwift Duuuuude! Does it feel like a pokedex? Can I see it?
English

🍕 Did I vibe-code a mostly good CRM + sales pipeline so I can track @DeepDishSwift ticket conversations and see retention by cohort?
Yes. Yes I did.
The insights are eye-opening. I’m not sure who I’ve become 🫠

English
Jacob 리트윗함

We've heard more and more cases of developers ending up on the wrong side of Apple for using non-IAP payments in their apps. There is a lot of confusion and some ambiguity right now in the US on what is and isn't allowed following the December 2025 appeal of the Epic v Apple case.
Our basic understanding:
1. Linking to an out-of-app web browser from your app that lets US users purchase - 100% OK
2. Linking to an in-app web browser that lets US users purchase - Unclear if this is ok, but we've seen some reviewers ok with it some not, benefits marginal
3. Having a button that uses an in-app, non-StoreKit (Stripe or others) to complete via Apple Pay - Very not ok, some people have been getting through, but pretty sure this is asking for a rejection or a ban
This is a somewhat probabilistic understanding as every submission to the App Store is a bit random, and we don't have direct channels with app review day to day, but we believe that right now, #1 is the only 100% safe path.
There are other vendors, some partners of ours, who are giving misleading guidance. We're working with these partners to try and keep everyone in the clear, but it's a bit of whack-a-mole.
If in doubt, play it safe. It's really really not worth the few percentage points margin to risk your main channel and main partner.
English









