We're looking for early users willing to test Polyvia and
give feedback. Ideal if you're:
- Building AI agents or multimodal workflows
- Working with documents heavy on charts, diagrams,
infographics
- Frustrated with RAG missing visual data What you get: Early access to Polyvia API + MCP Server Direct line to the founders for support Input on what we build next Interested? Sign up here: https://polyvia.ai/#access Or drop a comment happy to answer any questions first!
Hi Everyone! Our app is designed to be used at site and I always felt that response speed is critical for seamless app use
It appeared to be a compromise. This specially relates to audio and TTS we use. We can use very naturally sounding TTS models, but they may take about 1 minute to respond. Or we can use something which responds in 5 seconds but quality will be lower. How much do you think a user can wait for response before she shuts down the app as it takes too long?
Gitmore lets you ask questions about your GitHub, GitLab, and Bitbucket repos in plain English. Instead of filtering PRs, scanning commit logs, or interrupting engineers: "What shipped last week?" "Who's been working on the API?" "Which PRs have been open longest?" "Summarize this month's releases" Plain English in, plain English out.
How it works:
Connect your repos via OAuth. We register webhooks. Every event gets normalized into a structured schema commit message, PR description, author, timestamp, files changed. The AI queries structured data, not raw text. PR descriptions and titles carry context that individual commits often miss.
1. Recently, several small bloggers have talked about ProblemHunt: a few from the USA, a few from Spain, and one from France. And we noticed an obvious thing: traffic from these countries, although not much, has started to grow.
2. But the most important thing is that people from these countries have started sharing problems more actively. For example, in the last month alone, France has already submitted 4 problems, three of which were published yesterday and today.
Hey PH community! As we all rely on video calls more than ever, I'm curious about your biggest frustrations with tools like Google Meet, Microsoft Teams, Jitsi, or even the infamous Cluey. Do clunky interfaces, poor AI integrations, or a lack of admin controls (like forcing video on for interviews) drive you nuts?
I'm thinking about adding video chat to Blimp (getblimpy.cloud), our AI-native productivity suite. Imagine an AI assistant that quietly takes minutes in the background (non-intrusive), auto-generates bullet-point actions as tasks in your project hub (ditching those sloppy AI emails), plus admin perks like mandatory video, global audio muting, and background video effects that don't slow down your video.
What are your top video chat pain points? Share below your ideas could shape this!
Ho ho ho! We ve been busy improving the platform instead of adding flashy features but we couldn t resist. So yes, we added some flashy ones too. What's on the release:
We built a small calculator for you to see how much time you are wasting per day/week/year just due to context switching between different AI tools. Try it out! My wastage was 6 hours/week, what's yours?
We re currently building a new capability in SuperIntern: turning real meeting conversations into MCP-powered automation.
The idea is simple: SuperIntern listens to the meeting, understands what people say, and then uses Model Context Protocol (MCP) to orchestrate other tools and agents.
Hey collectors, We are so happy to see so much attention and support from you ^_^, and really wanted to share some discounts or free trials, but our product is free and the only thing we can do - improve your experience using us! Have you had a chance of registering your Supabase schemas and using several suggestion quieries? If you spot any troubles, want to improve something or just having unexpected urge of saying "Hi!", please do. Just DROP here everything you want.
Some of you might even want to have more control over the Racoon - do not hesistate to create PR. Thank yall!!! ------ SlopCollector's team, with love - Samat & Aisulu.
The year is almost done, and I have started to be curious about what could be stopping companies from adopting AI for their customer support services?? From my experience, I can tell - fear, fear of losing control. Support leaders worry that AI will say the wrong thing, sound off-brand, frustrate customers, or create more cleanup work for the team. Until they see that an AI agent can learn from their own knowledge base, follow rules, escalate when needed, and stay accurate, they hesitate. Once they realize it can actually reduce workload without breaking trust, adoption becomes much easier. What do you think? Do you agree with me?
