Spelling: American, in the podcast save/drop copy
Build Debug APK / build (push) Successful in 5m17s

This commit is contained in:
Greg Shuflin
2026-09-07 00:42:38 -07:00
parent e52652c3a2
commit dd5e063271
3 changed files with 4 additions and 4 deletions
@@ -16,7 +16,7 @@ import kotlinx.coroutines.launch
*
* The two are not the same lifetime, and that was the bug. Playback here is a
* [com.gregshuflin.synchronicity.media.PlaybackService], so leaving the player screen does not stop
* the audio: the notification keeps it going, out of a composition that has since been cancelled.
* the audio: the notification keeps it going, out of a composition that has since been canceled.
* The screen used to own the write loop and flush on its way out, which meant everything after that
* flush was lost — an hour listened from the lock screen recorded as the two minutes before the
* user navigated away.
@@ -41,7 +41,7 @@ private const val MIN_PROGRESS_MS = 3_000L
*
* A cache and named like one: the files are content-addressed by the Rust side, so a second play
* finds one already there, and nothing here removes them — the platform reclaims `cacheDir` under
* storage pressure, which is the behaviour wanted for a copy that can always be made again.
* storage pressure, which is the behavior wanted for a copy that can always be made again.
*/
private const val PODCAST_AUDIO_CACHE = "podcast-audio"
@@ -427,7 +427,7 @@ class PodcastRepository(private val nativeLib: NativeLib) {
* Download [episode]'s audio and keep it, so it plays with no network.
*
* Downloading is one of the moments an episode earns a document, and unlike playing it does not
* need the listener to have started — saving a back catalogue for a flight is something the
* need the listener to have started — saving a back catalog for a flight is something the
* user has said about those episodes. The Rust side creates the document and runs the download
* as a tracked job.
*
+1 -1
View File
@@ -626,7 +626,7 @@ const DOWNLOAD_CHUNK_BYTES: usize = 64 * 1024;
///
/// Downloading is one of the moments an episode earns a document (see
/// [`ensure_episode_document`]), and unlike playing it does not require the
/// listener to have started: a user who saves a feed's back catalogue for a
/// listener to have started: a user who saves a feed's back catalog for a
/// flight has said something about those episodes, and the document is where
/// that is recorded.
///