Hey everyone,

Two releases in quick succession this time. Here's what changed and why.

A Note on How Fast We Move

Pactify ships updates almost every week. That's intentional—we'd rather fix something in three days than wait three weeks. But it also means if you're running an older version, you're missing fixes and improvements that are already live.

Chrome should auto-update extensions in the background, but it doesn't always happen immediately. If anything feels off, check your extensions page and make sure you're on the latest version. It genuinely makes a difference.

v1.1.6: Strengthening the Foundation

After the security incident we shared in v1.1.5, I wasn't satisfied with just stabilizing things. I went deeper.

The core of this release was building real-human verification into our system. The attack we experienced wasn't just about traffic—it was bots distorting signals, triggering false usage, and making it harder for real users to be seen. So we added verification checkpoints across the critical flow to distinguish genuine users from automated actors. When a bot can't get through, it stops doing damage.

The practical effect: less noise in our systems, fairer resource allocation for actual users, and better signal for us to improve the product based on real behavior rather than bot artifacts.

I also expanded the free trial to 30 conversations. If you've been on the fence, that's now a proper amount of time to see whether Pactify actually fits your workflow before committing.

One more thing—and I'll be direct about it: our Chrome Web Store visibility still hasn't fully recovered from the attack. The best thing you can do, if Pactify has been useful to you, is leave an honest review. Not for us—for the next person who needs this tool and is trying to figure out if it's worth trusting. Reviews from real users are the most effective counter to the kind of manipulation we went through. If you haven't yet, it would mean a lot.

v1.1.7: Reducing Friction

One thing I've noticed in user feedback: small interruptions break flow more than people account for. A dialog box that pops up mid-session—even a helpful one—can cost you three seconds of attention and derail a thought.

We removed the trial timeout dialog that used to appear while you were in the middle of a conversation. It was well-intentioned, but it was interrupting you at the wrong moment. The information it carried is still accessible, just no longer shoved in your face unprompted.

We also added a quiet version check. When a new version of Pactify is available, the extension will let you know—no pressure, just a nudge. Given our release cadence, staying current is worth it.

The Short Version

Security is tighter. Interruptions are fewer. And if you're not on v1.1.7 yet, it's worth the update.

Hey everyone,

I want to be honest with you about what's been happening behind the scenes these past two weeks.

Pactify Was Under Attack

We were hit by a coordinated negative SEO campaign. If you've tried searching for Pactify on the Chrome Web Store recently and couldn't find us—that's why. The attack was deliberate and precisely targeted, and the impact was significant.

We spent a large portion of these two weeks investigating, diagnosing, and upgrading our security defenses. The situation has mostly stabilized, but our visibility in Chrome Web Store search is still recovering. Daily traffic dropped sharply, and I won't pretend that didn't hurt.

Why This Hit Harder Than Expected

Here's the honest truth: Pactify is not a mass-market product. We serve a specific group of people—those who use AI tools intensively and want to connect them with Notion. That's a small, focused audience. We're not running aggressive freemium growth or viral referral loops. We grow slowly, by being genuinely useful.

Which means when someone targets that foundation, it matters.

What stings more is that I should have caught this earlier. I had neglected some of the infrastructure fundamentals—monitoring, anomaly detection, platform health checks. By the time I sat down and did a serious analysis, a meaningful amount of damage had already been done. A well-designed attack was already weeks old before I recognized it for what it was.

What Comes Next

We're doing an internal review of our roadmap. This situation forced me to confront something I'd been deferring: we need a more stable foundation before we keep adding features on top of it.

That means three things going forward:

First, service stability and infrastructure will get the attention they deserve. Not glamorous work, but necessary.

Second, we're diversifying how we reach people. Relying too heavily on one discovery channel made us fragile. SEO, content, community—these need to work together.

Third, new feature development will slow down—temporarily. I know that's frustrating to hear if you've been waiting on something. But shipping features into an unstable foundation isn't responsible to you or to the product.

A Note to Everyone Still Here

This was a lesson. I'm not going to pretend otherwise or dress it up as a strategic pivot. We took damage, we made mistakes, and we're fixing them.

But I also know what Pactify is, what it's for, and who it's for. That hasn't changed. I'm asking for your patience while we make the underlying service worthy of the trust you've placed in it.

We'll come back stronger. Thank you for staying.

Hey everyone,

This week was all about fixing the small things that add up to big frustrations.

The Gemini Title Bug

Some of you noticed conversations syncing to Notion as "Untitled" when they came from Gemini. I finally tracked it down—Gemini changed their DOM structure, and my title scraper couldn't find the conversation name anymore. Rewrote the logic to handle their new layout. Your conversation titles should now show up correctly in Notion.

Understanding Why You Leave

I added a simple feedback form that shows up when you uninstall the extension. Just two questions: why you uninstalled, and what would bring you back. I'm not tracking you or selling data—I just need to know what's not working. If you ever decide to leave, your honest feedback would help more than you think.

The Title & URL Sync You Asked For

This one's been requested a few times: you rename conversations in ChatGPT to stay organized. In Claude, you move conversations between Projects. But Notion never knew about these changes—so your database got out of sync with your actual chats.

Now the sync is smarter. When you update a conversation, it checks if the title or URL changed (like when moved to a different project). If they did, it updates your Notion database automatically. One less thing you have to manually fix.

That's it for this week. Small improvements, but the kind that matter when you're using this daily.