motioneye-project/motioneye 0.43.1

on GitHub

First stable 0.43.1 release!

To see what's new since the last stable 0.42.1, see the previous beta release notes:

• https://github.com/motioneye-project/motioneye/releases/tag/0.43.1b1
• https://github.com/motioneye-project/motioneye/releases/tag/0.43.1b2
• https://github.com/motioneye-project/motioneye/releases/tag/0.43.1b3
• https://github.com/motioneye-project/motioneye/releases/tag/0.43.1b4
• https://github.com/motioneye-project/motioneye/releases/tag/0.43.1b5

What's new since 0.43.1b5:

• The /picture/ID/list and /movie/ID/list media file list API have been extended by a new optional boolean with_stat query parameter, which defaults to true, preserving the previous behavior. If set to with_stat=false, the returned data object contains only the data.path element, no data.timestamp, data.sizeStr, etc. This speeds up processing time and request size by at least a magnitude of order, and hence reduces the change to run into the list_media_timeout timeout defined in motioneye.conf. This is made use of internally for the initial recursive file list requested when opening the picture/movie browser on camera panels, when generating a time-lapse movie, downloading or deleting all media files in a directory, speeding up each of these tasks significantly: #3225 @MichaIng
• Also behind the scenes, the Python code to loop through the files and obtain the info has been unified and enhanced, to speed up the calls: #3215 #3219 @MichaIng
• Translated strings inside HTML documents are now assured to be HTML-escaped: #3239 @MichaIng
• Several translation updates, many thanks to all @weblate contributors ❤️
• Some major polishing on our Weblate translation repository has been done: with Nepali being the only exception, all languages got all missing strings machine-translated, and all machine-translated backend/Python strings are now used by motionEye. Previously, those, which are marked as "needs editing", were not compiled, hence Esperanto source strings were shown instead. However, note that the quality of those machine-translated strings varies. We have no costly API key for proper translation services like DeepL, hence LibreTranslate is used, which ... has mixed results 😅. But I spent some time to address nearly all annotations of Weblate's quality checks, which includes a lot of formal things like correct spacing, consistent punctuation, Python format variables, as well as word repetition and similar things, which includes most bad machine-translation results. For some languages, LibreTranslate does not work, in which case I used DeepL manually. Only for Nepali, with close to 500 missing strings, the work would have been too much, bear with me. The machine-translated strings do not contribute to the completion percentage, show up as "unfinished words" with a "needs editing" mark.
  => So please everyone, check our our Weblate repo, and help to finish or polish the translation for your language, let's make motionEye a please to use for people of any language and culture 🙂. @MichaIng