Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[FEATURE] Store Voice engines in other path than '~/Library/Caches/'

Open
#1,087 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
56/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
swift
Domain
desktop

Research direction

Start by locating where FluidVoice stores and loads voice engines under ~/Library/Caches/, then trace how that path is used for downloads and subsequent access. The issue proposes a dedicated ~/.fluidvoice folder; check the existing storage and loading entry points before changing the location. Done means voice engines are stored outside the cache and remain available after cache cleanup.

Written by the indexing model from the issue text.

Description

enhancement keep-open
Problem

[FEATURE] Store Voice engines in other path than '~/Library/Caches/' because CleanMyMac and other Mac cleaners wipe out this path an Voice engines disappears forcing users to download it over and over.

Proposed solution

Store Voice engines in other path than '/Library/Caches/' like '/.fluidvoice' dedicated folder

Alternatives considered

No response

Dominant language
Swift
Stars
11.9k
Forks
863
Avg merge
1d 13h
Merged PRs (30d)
27

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from altic-dev/FluidVoice

All issues in altic-dev/FluidVoice

Similar issues

More Swift issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.