i'm using apple ads' keyword recommendations as negative keywords in my campaigns.
i want to believe they labeled them as "recommendations" by mistake
users can see all your subscription offers in one place, even the ones you only show under certain conditions.
of course, many users might not know this, but you can never be sure it's working the way you intended.
I've decided to remove all my apps that still bring in a little revenue but haven't been updated in a while.
if your app has been rejected by apple a few times, this is worth a read
in the last 30 days, i've made $133 from users who found my app through chatgpt.
i'm really curious what those conversations looked like and how chatgpt ended up recommending my app.
thanks for all the advice!
i've added two options: a monthly subscription with tokens included, or byok.
free users can also try the app using my tokens, no setup needed.
this should definitely get more people to try it, so i'm pretty happy with how it turned out
i'm thinking about doing live youtube sessions on apple ads, aso, and indie app development.
we could discuss real world data and problems from both my apps and yours.
do you think it's a good idea?
Mehmet retweeted
part 2 is here!
you might discover a keyword before your competitors, but Apple Ads can discover it for them.
here's why Broad Match, Search Match, and app relevance are changing the ASO game in competitive markets.
i never believed in the "build an app that solves your own problem" advice.
now i'm building an app that solves my own problem, and i plan to launch it outside the app store in about 2 weeks.
let's see who's right. me or the people giving that advice
built my first app that i'll sell outside the app store and play store.
there's just one problem: users need to bring their own llm api key.
normal users won't know how to do that, and the ones who do could probably build the app themselves.
looks like i picked the wrong app idea again :d
i saw two posts here about tools for finding potential customers, but i can't find them anymore.
i think the founders even reached out to me via dms, but i can't find those either
if you see this, please ping me again. i'd love to check out your tools!
i've decided to focus on building a brand around my flagship app.
i've already ported it to swift, and now i'm porting it to android.
i've also changed the app's name to a branded one.
next, i'll start running social media ads to build brand awareness.
the only thing i'm unsure about is trademark registration in the us. no idea how that works yet.
part 2 is here!
you might discover a keyword before your competitors, but Apple Ads can discover it for them.
here's why Broad Match, Search Match, and app relevance are changing the ASO game in competitive markets.
looks like everyone's started using ai to find vulnerabilities :d
October just keeps stacking security disasters.
From developer tools to India’s largest bank, here’s the timeline of disclosures, patches, and incident updates:
Oct 21
- SBI: disclosed 3,897 customer records containing personal information exposed on the dark web. Investigation ongoing.
- PHP2Shell: patches released for two critical unauthenticated RCEs in PHP core. Exploitation attempts had already been observed.
- Railway: warned that customer environment variables may have been accessed, with some potentially decrypted. Deployments were initially paused.
- LiteLLM: malicious v1.107.0 packages and container images carried credential-stealing malware and loaders. Vendor reported containment the same day, but affected machines still need remediation.
- GitLab: patched a CVSS 10.0 unauthenticated RCE affecting versions since 7.0, exploitable under certain conditions.
- Java: Oracle issued an out-of-cycle alert for CVE-2026-91403, a CVSS 9.1 remotely exploitable JSSE vulnerability requiring no authentication.
- Node.js: released multiple high-severity security fixes.
Oct 20
- eMudhra: public advisories detailed eight compromised intermediate CA keys with dangerously weak randomness. Browser blocking began Oct 17. India’s DSC/eSign services were unaffected, according to the company.
- Plex2Shell: CISA added all four actively exploited vulnerabilities to KEV. Patches had been available since August.
- SiteGuard Server Edition: exploited OS-command-injection flaw added to KEV.
- Siemens Software Center: exploited DLL-sideloading flaw added to KEV.
- HTTP/3: Header Accordions research detailed QPACK memory-amplification/DoS weaknesses across multiple implementations. Several were already patched.
Oct 19
- OVHcloud CLI: attackers replaced GitHub release binaries after compromising a developer account. Source code was unaffected.
Oct 17
- OpenCode: disclosed a hosted Console breach potentially exposing saved AI-provider API keys for a subset of users.
- Zeabur: announced a phased shutdown following its Oct 14–15 breach. Its subsequent report confirmed over 3.2 million environment-variable records were accessed.
If these are in your stack, check the affected versions and exposure windows now.
Patch vulnerable systems. Revoke and rotate potentially exposed secrets. If malicious software ran, follow containment and rebuild guidance too.
A patch fixes the vulnerability. It doesn’t undo credentials already stolen.










