kopia lustrzana https://github.com/Podcastindex-org/podcast-namespace
commit
19f0964a26
|
@ -100,7 +100,7 @@ Here is what a very basic chapters file may look like:
|
||||||
```
|
```
|
||||||
|
|
||||||
In this simple form, the chapter objects are treated as sequential just based on their index as a function of being
|
In this simple form, the chapter objects are treated as sequential just based on their index as a function of being
|
||||||
ordered in ascending fashing based on their `startTime`. In a very simple example such as this nothing is present except the `startTime`,
|
ordered in ascending fashion based on their `startTime`. In a very simple example such as this nothing is present except the `startTime`,
|
||||||
`title`, and a few bits of optional meta-data.
|
`title`, and a few bits of optional meta-data.
|
||||||
|
|
||||||
<br><br>
|
<br><br>
|
||||||
|
@ -171,4 +171,4 @@ chapter list, but allows for different artwork to be shown:
|
||||||
|
|
||||||
Clearly, when pulling in web based data there is the chance that this functionality could be used for tracking. As a safeguard against that, apps
|
Clearly, when pulling in web based data there is the chance that this functionality could be used for tracking. As a safeguard against that, apps
|
||||||
using chapters are encouraged to prompt the user to acknowledge whether they trust the podcast in question before displaying the content. Trusted
|
using chapters are encouraged to prompt the user to acknowledge whether they trust the podcast in question before displaying the content. Trusted
|
||||||
podcasts can then be remembered for the future.
|
podcasts can then be remembered for the future.
|
||||||
|
|
Ładowanie…
Reference in New Issue