Jeeves – Reasoning improves Jev-like decision models - PostHog/jeeves

Jeeves – Reasoning improves Jev-like decision models - PostHog/jeeves

Jeeves – Reasoning improves Jev-like decision models - PostHog/jeeves

Jeeves – Reasoning improves Jev-like decision models - PostHog/jeeves

Jeeves – Reasoning improves Jev-like decision models - PostHog/jeeves

Jeeves – Reasoning improves Jev-like decision models - PostHog/jeeves

Jeeves – Reasoning improves Jev-like decision models - PostHog/jeeves

Jeeves – Reasoning improves Jev-like decision models - PostHog/jeeves

I tried other options and this was the smoothest. FluidVoice is GPLv3, free, but connects to posthog by default without asking. It has a vibecoded looking UI with gradients. Voiceink seems good but it’s paid for the compiled build. TypeWhisper is also about 1/4 the size of these other options. This parakeet model they all have as options is fantastic.

overdrawn98901: > I’d assume they don’t want 2 analytics running at the same time, so benefit of doubt is they forgot to remove Google tag manager. A cynical take would be they lied and kept using Google all along. We removed Google Analytics from our marketing site (it was never used on our card platform) and replaced it with Plausible, which we recently replaced with PostHog because they support anonymous, first-party analytics, allow us to identify and respect GPC (Global Privacy Control) signals and allow us to now run a single analytics platform across both the marketing site and card platform. lissy93: > My issue with them, is that they said they removed Google Analytics. When actually they just removed it from their privacy policy + homepage, but kept recording user events on the account pages (where it matters most). I reviewed them here. Hi @lissy93! My apologies, I wasn’t aware you had an issue with us. Please allow me to clarify a few things for you here. We did remove Google Analytics from our marketing site as I previously mentioned, and it has never been used on our card platform. We use PostHog on our card platform to understand how people use our service, where they get stuck and proactively identify bugs and usability issues. These usage analytics are a part of how we constantly improve our customer experience and make the platform better. Separately to this, our team have been testing different marketing channels and payment processors (Stripe). Google Tag Manager (GTM) was implemented as part of this testing to identify which marketing campaigns are the most effective. Our team have already come up with alternative approach that doesn’t require GTM in the middle and we’ll move to this once our testing is complete. Also, you gave us quite a lot of homework to do in our PR last week. We’ve applied all the fixes to our marketing site and are working through the requests made for our card platform. Because we handle card payments and funds on behalf of thousands of people, we take a little longer to implement, test and publish changes to the card platform, but I’ll definitely re-open the PR and publish a breakdown of all the changes we’ve made as soon as they’re live.