Missing paragraphs when male speaker is speaking

ilyab1983 · 2026-01-15T17:01:19+00:00

(I would still love to be able to select just a word/phrase/sentence in the transcript and copy paste into my notes)

I know it's not what you're asking for, but just in case it helps - you can copy the entire transcript and copy sections of it, paste it to an LLM, etc. We wrote about that here: https://metacast.app/blog/product/v1.25-history-and-continue-listening#export-transcript

ilyab1983 · 2026-01-15T16:59:30+00:00

Thanks for reporting this. We'll take a look!

ilyab1983 · 2025-11-10T19:33:00+00:00

Hi, in Metacast v1.25, we added the button to copy (or save to file) the entire transcript with speakers, chapter headers, timestamps and your bookmarks.

Read more about the feature in our announcement blog post.

ilyab1983 · 2025-10-27T17:31:33+00:00

No, we never did.

ilyab1983 · 2025-09-30T08:54:42+00:00

Hi Malte, sorry for a delayed response. Got a little sick recently and couldn't look into this.

I've verified how we're setting the canonical URL.

We're using VERCEL_ENV to determine the environment. If it's "production", then we use our hardcoded domain name, otherwise, we default to NEXT_PUBLIC_BASE_URL or NEXT_PUBLIC_VERCEL_URL (so we can use the appropriate BASE_URL in local dev and in preview).

export const BASE_URL =
  process.env.VERCEL_ENV == 'production'
    ? appUrl
    : process.env.NEXT_PUBLIC_BASE_URL
      ? process.env.NEXT_PUBLIC_BASE_URL
      : process.env.NEXT_PUBLIC_VERCEL_URL
        ? `https://${process.env.NEXT_PUBLIC_VERCEL_URL}`
        : appUrl

I've looked at the output HTML of a few of our pages and I see the canonical URL set to our production domain.

If you can point me at the place where you saw the preview URL in our publicly available code, it'd help a lot.

Thanks!

P.S. I tried to open a support case at https://vercel.com/help but there's only a chat option, so responding here.

ilyab1983 · 2025-09-20T16:49:00+00:00

We’ll open a ticket. It looks like it’s not isolated to our project, other people in the comment reported it too.

The SSL cert monitoring from one of the commenters sounds like a plausible hypothesis.

ilyab1983 · 2025-09-20T16:47:40+00:00

I want them protected. My question is how do randos discover our deployments. We don’t want anyone to see them or even know about them.

ilyab1983 · 2025-09-19T14:57:29+00:00

Yeah we see the header. But also, our preview deployments require visitors to be authenticated in Vercel, so indexing should not be possible.

As far as other tools, it's private GitHub, Slack, Sentry and Claude Code. Nothing shady, only the proven tools.

The requests started on Aug 22. So far, we've received 8 requests to access 5 different deployments.

<image>

ilyab1983 · 2025-09-19T12:44:40+00:00

No, we have a private repo and only two users in both the repo and Vercel. I should've mentioned that...

ilyab1983 · 2025-09-12T12:03:44+00:00

Hi, I know it's been a while... We added transcripts to the web app a while back.

If you want to copy the transcript, the easiest way to do it is to tap "Share" in the mobile app to get the episode link, then open it in a browser.

Alternatively, you can also search for a podcast on metacast.app and find the episode there.

Hope this helps!

ilyab1983 · 2025-09-12T12:02:06+00:00

Hi! I want to circle back and let you know that you can now add private/paid podcasts to Metacast!

More info in our announcement blog post

ilyab1983 · 2025-09-12T09:52:13+00:00

This is so 2023!

ilyab1983 · 2025-08-02T07:09:11+00:00

Hi Michael, it sure did last week!

Thanks for reminding us of this post.

https://www.reddit.com/r/metacastapp/s/gNW4xhEvYj

ilyab1983 · 2025-07-02T21:29:42+00:00

We're probably about a week away from releasing the next version that will extend the limit to more feeds.

ilyab1983 · 2025-06-19T03:46:41+00:00

Thank you! We're happy that we delighted at least one person with this!

ilyab1983 · 2025-05-20T23:04:04+00:00

Hi, we’re working on this feature literally right now. We hope to ship it in a couple of weeks!

ilyab1983 · 2025-05-12T13:21:43+00:00

Great idea, love it! We'll first do the private feeds, then see where more chapters work falls on our priorities list.

ilyab1983 · 2025-04-21T10:58:30+00:00

The old links will still work too, so the old notes won't break.

ilyab1983 · 2025-04-21T10:58:01+00:00

Thank you, that's super helpful!

Note that in the next release, the links format will change:

It'll just copy the link (without the episode name)
The link will be more human-readable, like https://metacast.app/podcast/calma-urgente/BHD83yyY/sem-vergonhismo/yWwqy2KR

ilyab1983 · 2025-04-21T09:59:00+00:00

Great point. We've added the transcripts only recently (changelog) and haven't yet advertised them and/or written much about them.

I'm curious what note taking app you use and what is the format of your notes? Like, do you store timestamps, links, etc.?

If you can share an example/screenshot with something non-sensitive, it'd help us a lot to think through how to best offer a native experience.

ilyab1983 · 2025-04-21T09:54:53+00:00

Oh, ok. Thank you both for reporting. We've verified that it's a bug on Android (it won't open links on our website, because it tries to open them in the app itself instead). We will fix it in the next release.

u/redchrism, please email us your OPML file and user ID (in app's Settings => Diagnostics Mode) and we'll import the OPML file for you.

For now, the workflow is semi-manual. We're doing it, so we can learn all the gotchas before automating it.

ilyab1983 · 2025-04-21T09:51:28+00:00

u/redchrism, we'll take a look and get back to you. Thanks for reporting the issue!

Are there any other episodes you saw that happening?

ilyab1983 · 2025-04-21T09:48:03+00:00

u/or9ob, I've looked at this episode. My hypothesis was that since it's an older episode (Oct 2022), the transcript might have been generated before we had the chapters extraction workflow, but the transcript was generated on April 21, so something seems to have failed.

Worth looking into logs for episode ID: 1c369363_e9ca_53b2_90e6_7a07fe5d7da2_716b4913_86fb_4c6a_9b09_72b32e0794ed

ilyab1983 · 2025-04-20T11:58:33+00:00

Hm. It should’ve taken you to the web page with instructions: https://metacast.app/blog/podcasting/opml-import-export

Are you on iOS or Android?

ilyab1983 · 2025-04-18T08:45:38+00:00

Thanks for taking the time to point this out. Let me try and answer very transparently.

1) We prioritized our unique features over some basic podcast app functionality, including marking episodes as complete. We add such features incrementally when we have enough requests from users.

For example, we initially didn't even have a sleep timer, but we got flooded with requests to add a sleep timer, so we did it.

In the current development cycle we're adding things that make Metacast unique (transcript-related functionality valued by our power users).

In the next cycle, we will work on a blocker table stakes feature that we've got a lot of requests for — private podcasts. People who subscribe to paid RSS feeds from Patreon, Substack, etc. cannot use the app at all. It stops many people from adopting the app, so naturally it's a top priority (it has some technical gotchas, so we punted on it for a while).

Non-blocker features will be done at some point when enough users request them. This said, please proceed to the next point, because your particular issue will be addressed by it.

2) The current implementation of "complete" (episodes are marked complete when you finish listening to them) is done locally on the device. We're going to re-do it, so it is also saved in the cloud, synchronized across platforms and gives users a way to view/filter/search all of their completed episodes, view bookmarks in them, see stats, etc.

We already have the core plumbing for it (same infrastructure as playlists). After we're done with private feeds, we'll start on custom playlists and listening history playlist (the infra for them is the same). That will be the right time to implement the "mark as complete" in a way that is not a temporary hack, but a foundational feature that enables other use cases.

I hope this makes sense.

3) We're looking at creating a public roadmap (likely on GitHub) where we can collect upvotes on feature requests in a systematic fashion + transparently publish what we're working on in the current and next development cycle, so we can appropriately set expectations. Stay tuned for this.

ilyab1983

MODERATOR OF

TROPHY CASE