No description
228bb62df4
In order to ease podcast listening, the player can be put on top of the feed entry as main content. Use the `Use podcast player` option to enable that. It works on audio and video. Also, when playing audio or video, progression will be saved in order to be able to resume listening later. This position saving is done using the original attachement/enclosures player AND podcast player and do not rely on the podcast player option ti be enabled. Additionally, I made the player fill the width with the entry container to ease seeking and have a bigger video. updateEnclosures now keep existing enclosures based on URL When feeds get updated, enclosures entries are always wiped and re-created. This cause two issue - enclosure progression get lost in the process - enclosure ID changes I used the URL as identifier of an enclosure. Not perfect but hopefully should work. When an enclosure already exist, I simply do nothing and leave the entry as is in the database. If anyone is listening/watching to this enclosure during the refresh, the id stay coherent and progression saving still works. The updateEnclosures function got a bit more complex. I tried to make it the more clear I could. Some optimisation are possible but would make the function harder to read in my opinion. I'm not sure if this is often the case, but some feeds may include tracking or simply change the url each time we update the feed. In those situation, enclosures ids and progression will be lost. I have no idea how to handle this last situation. Use the size instead/alongside url to define the identity of an enclosure ? Translation: english as placeholder for every language except French Aside, I tested a video feed and fixed a few things for it. In fact, the MimeType was not working at all on my side, and found a pretty old stackoverflow discussion that suggest to use an Apple non-standard MimeType for m4v video format. I only did one substitution because I only have one feed to test. Any new video feed can make this go away or evolve depending on the situation. Real video feeds does not tend to be easy to find and test extensively this. Co-authored-by: toastal |
||
|---|---|---|
| .devcontainer | ||
| .github | ||
| api | ||
| cli | ||
| client | ||
| config | ||
| contrib | ||
| crypto | ||
| database | ||
| errors | ||
| fever | ||
| googlereader | ||
| http | ||
| integration | ||
| locale | ||
| logger | ||
| metric | ||
| model | ||
| oauth2 | ||
| packaging | ||
| proxy | ||
| reader | ||
| service | ||
| storage | ||
| systemd | ||
| template | ||
| tests | ||
| timer | ||
| timezone | ||
| ui | ||
| url | ||
| validator | ||
| version | ||
| worker | ||
| .gitignore | ||
| ChangeLog | ||
| doc.go | ||
| go.mod | ||
| go.sum | ||
| LICENSE | ||
| main.go | ||
| Makefile | ||
| miniflux.1 | ||
| Procfile | ||
| README.md | ||
| SECURITY.md | ||
Miniflux 2
Miniflux is a minimalist and opinionated feed reader:
- Written in Go (Golang)
- Works only with Postgresql
- Doesn't use any ORM
- Doesn't use any complicated framework
- Use only modern vanilla Javascript (ES6 and Fetch API)
- Single binary compiled statically without dependency
- The number of features is voluntarily limited
It's simple, fast, lightweight and super easy to install.
Official website: https://miniflux.app
Documentation
The Miniflux documentation is available here: https://miniflux.app/docs/ (Man page)
- Opinionated?
- Features
- Requirements
- Installation Instructions
- Upgrading to a New Version
- Configuration
- Command Line Usage
- User Interface Usage
- Keyboard Shortcuts
- Integration with External Services
- Rewrite and Scraper Rules
- API Reference
- Development
- Internationalization
- Frequently Asked Questions
Screenshots
Default theme:
Dark theme when using keyboard navigation:
Credits
- Authors: Frédéric Guillot - List of contributors
- Distributed under Apache 2.0 License