Releases: osmoscraft/osmosfeed
Releases · osmoscraft/osmosfeed
v1.11.0
- Added: support an experimental template for YouTube feed 📺 Demo | Source
- Aggregate content from any YouTube channel rss url
https://www.youtube.com/feeds/videos.xml?channel_id=<replace_with_channel_id>
- Videos are embedded via iframe and loading accelerated by youtube-lite-embed
- Ads are reduced thanks to YouTube's policy for embedded videos 🙃
- Works on mobile devices with butter smooth horizontal scroll.
- Caveat: the template works only with YouTube content. You cannot mix textual RSS feed or other video sources such as Vimeo.
- Aggregate content from any YouTube channel rss url
- Changed: Default HTML template meta tag adjusted to match convention
- Changed:
sources
in template data is now ordered by last update timestamp (as opposed to alphabetical) - Thank you @PiyushLosalka
v1.10.2
- Added: testing and CI/CD workflows
v1.9.0
- Added: experimental support for iTunes podcast feed: Demo | Source. With this new release, you can render an audio control to play the mp3 file and display iTunes episode duration. It is "experimental" due to these caveats:
- This feature is currently only available through custom template.
- iTunes has no strict format requirement for
duration
. The unit is most likely seconds but can be "hh:mm:ss" or "mm:ss" for some sources. A future version may expose a human readable string to the template. - No image support yet. Some shows might have disabled CORS or use a relative URL for image, which forces osmosfeed to download the image during build. A future version may support it.
- You can't republish the podcast in the feed output. Supporting this goes beyond the scope of the project at the moment.
- Fixed: the
articles
in template data were not sorted. - Thank you @Zenigata
v1.8.1
- Fixed:
UnhandledPromiseRejectionWarning: Error: At least one option must be a string
v1.8.0
- Changed: Smart summary truncation. When there is no dedicated
summary
(only Atom feed has it, and many sites don't use it) from the source, we check if the content/description (Both Atom and RSS) field is long enough to be full text. If so, it will be truncated into a "pseudo" summary. If not, we assume the source used thecontent
field as summary, and it will be displayed in full length. - Thank you: @LooperXX.
v1.7.2
- ⚠ Deprecated: To accommodate the monorepo setup, the node version in all templates/demos/examples has changed from 14 to 16. This is not a breaking change as our compile target is still node 14, and node 16 is backward compatible. We still recommend you start using
node-version: "16"
in your.github/workflows/update-feed.yaml
today to get the performance/security improvements from the newer node. See example - Chore: Reorganize to monorepo with npm workspace.
v1.7.1
- Fixed: static files were unnecessarily copied for custom templates.
v1.7.0
v1.6.0
- Added: Link from the title of a subscription to its website.
- Added: Store
feedUrl
andsiteUrl
for each source in cache. - Added: Semantic element (
<time>
) for timestamp on the UI. - Added: Semantic API for theming the default template. Demo | Source | Docs
- Changed: Moved feed metadata from article level to feed level in cache.
- Fixed: Any html-like text was stripped from title. Fixed with encoded text.
- Removed:
href
for each source in cache. The value was never used so it's not a breaking change.
v1.5.0
- Added: Atom feed generator
- Added: Customizable site title
- Added: Copy all files from
static
directory to the root of the site. - Changed: Favicon, css, and js assets now existing at site root level.
- Chore: Excluded testing files from repo.