• 23 Posts
Joined há 4 anos
Cake day: abr 18, 2019


It’s definitely better in third-party reddit apps though.

That, and to have more power to fundamentally alter it.

I’m convinced he’s doing everything to burn it to the ground put it in bankruptcy as fast as possible.

I use HandBrake to transcode DVDs with the libdvdcss2 library and it works seamlessly, it doesn’t even know the DVD is copy-protected.


TAILS 5.6 is out
``` tails (5.6) unstable; urgency=medium * Upgrade Linux to 5.10.149 (tails/tails!935) Closes issues: - Fix beacown (tails/tails#19210) Commits: - Release process: bring back test that we can run locally, but not on Jenkins - Really disable broken Thunderbird test - Upgrade Linux to 5.10.149-1 * Disable broken Thunderbird test (tails/tails!934) Commits: - Disable broken Thunderbird test * Upgrade Tor Browser to 11.5.5 (tails/tails!936) Closes issues: - Upgrade to Tor Browser 11.5.5 (ESR 91.13 + ESR 102.4 backports) (tails/tails#19178) Commits: - Upgrade Tor Browser to 11.5.5 * post-release misc updates (tails/tails!932) Commits: - easier transmission-remote instructions - avoid re-downloading if restarting - better instructions for automated test suite * Thunderbird: remove obsolete oauth2 pref (tails/tails!929) Commits: - Thunderbird: remove obsolete oauth2 pref * Upgrader: when a manual upgrade is needed, point to the news & manual upgrade doc without specifying a (probably incorrect) version (tails/tails!915) Closes issues: - Tails Upgrader recommends manual upgrades to deprecated versions (tails/tails#17069) Commits: - Make /latest inline the translated version of the release notes - Rewrite in Markdown - Move latest release notes out of /news - Improve phrasing - Point to release notes of latest version only - Upgrader: when a manual upgrade is needed, point to the news & manual upgrade doc without specifying a version -- Tails developers <tails@boum.org> Mon, 24 Oct 2022 08:06:36 +0000 ```

Memtest86+ v6.00
V6.00 Changelog * Rewrite code for UEFI 32 & 64 bits * Add support for x64 Long Mode Paging * Add support for up to 256 cores * Add detection for DDR4 & DDR5 * Add support for XMP 3.0 * Add detection for AMD Zen 1/2/3/4 * Add detection for Intel up to 13th Gen * Add better support for AMD pre-ZEN CPUs * Add support for older nVidia and AMD chipsets * Add support for SDRAM * Many enhancements * Numerous bug fixes & optimization

And even better, with some older games already patched with unofficial updates that are considered must-have, like for Vampire : The Masquerade Bloodlines or for S.T.A.L.K.E.R.

SystemRescue 9.05
* **9.05) 2022-10-21:** * Split initialization of SystemRescue into parts done before and in parallel to networking (#304) * Add a new style for configuring autorun scripts (“autorun.exec”) (#287) * Change the default for ar\_nowait to true: don’t wait at the end of autorun by default anymore * Deprecate storing autorun scripts in the root of the boot disk (#252) * Bind-mount /run/archios/bootmnt in case of copytoram to create a stable path for use in autorun * Add yay AUR helper (#139) * Allow https-URLs for the archiso\_http\_srv option by disabling certificate checks * Don’t waste ram when using the archiso\_http\_srv option (#56) * mountall: run udevadm settle to mount newly opened cryptodisks, improve messages * Add rclone option to the “sysconfig” scope of YAML config file, it writes a rclone.conf file * Add sysctl option to the “sysconfig” scope of YAML config file * Added packages: whois (mkpasswd)

It’s fascinating how complex it can become when dealing with timezones from a programmer point-of-view.

deleted by creator

Cracking down on political dissidents outside of their jurisdiction? To me that sounds like an overreach and meddling of a sovereign nation’s internal affairs.

Can we post english links here? This is the lemmy.ml community, not feddit.de

We be nice to have a way to save a webpage as a WARC, and have them both available outside of Firefox for archival, but also in an “Offline” section within the app.

Looks like Cyberpsychosis will eventually be inevitable.

I guess you could find the RSS feed behind the Apple Podcasts listing using this


I mean, off course they think you should. They’re not gonna sell it at $120 and then say yeah, don’t actually buy it, it’s overpriced.

It’s is a scanning app, but its core relies on the zxing library. Sadly there isn’t a standardized way of calling a default barcode scanning app on Android, so your only option is to build your own inside the app, or rely in the zxing library.

Maybe you can look at how Binary Eye integrates the library and base your work upon it?

zxing is still the go-to for this matter. It’s technically in maintenance mode, doesn’t mean that it’s dead or unsupported.

Other barcode scanning apps like Binary Eye depends on it.

Maybe a workaround would be the ability to load your personal data from the privacy settings menu as a one-time import.

CTemplar is shutting down on May 26th 2022
> Dear users, > > CTemplar is closing and the last day of operation for this email service will be on May 26 of 2022. > > To transfer your contact list: > - Go to https://mail.ctemplar.com/mail/contacts > - Click on the button to export your contacts. > - Select your preferred format (CSV or VCF). > > To transfer your emails: > - Log into your account and download the exported data from your account. It includes emails and attachments. > > Remember to change your email information to your new service. > > Please migrate all your data out of this email service by May 26 of 2022, after this day all the stored that will be permanently erased. > > Please contact support to issue refunds! > > A huge thank you to everyone that supported us, > > The CTemplar Team

CTemplar is shutting down on May 26th 2022
> Dear users, > > CTemplar is closing and the last day of operation for this email service will be on May 26 of 2022. > > To transfer your contact list: > - Go to https://mail.ctemplar.com/mail/contacts > - Click on the button to export your contacts. > - Select your preferred format (CSV or VCF). > > To transfer your emails: > - Log into your account and download the exported data from your account. It includes emails and attachments. > > Remember to change your email information to your new service. > > Please migrate all your data out of this email service by May 26 of 2022, after this day all the stored that will be permanently erased. > > Please contact support to issue refunds! > > A huge thank you to everyone that supported us, > > The CTemplar Team

Filters to block and remove copycat-websites from DuckDuckGo, Google and other search engines. Specific to dev websites like StackOverflow or GitHub.

Starting with Firefox 93, Firefox will monitor available system memory and, should it ever become so critically low that a crash is imminent, Firefox will respond by unloading memory-heavy but not actively used tabs. This feature is currently enabled on Windows and will be deployed later for macOS and Linux as well. When a tab is unloaded, the tab remains in the tab bar and will be automatically reloaded when it is next selected. The tab’s scroll position and form data are restored just like when the browser is restarted with the *restore previous windows* browser option. On Windows, out-of-memory (OOM) situations are responsible for a significant number of the browser and content process crashes reported by our users. Unloading tabs allows Firefox to save memory leading to fewer crashes and avoids the associated interruption in using the browser. We believe this may especially benefit people who are doing heavy browsing work with many tabs on resource-constrained machines. Or perhaps those users simply trying to play a memory-intensive game or using a website that goes a little crazy. And of course, there are the tab hoarders, (no judgement here). Firefox is now better at surviving these situations. We have experimented with tab unloading on Windows in the past, but a problem we could not get past was that finding a balance between decreasing the browser’s memory usage and annoying the user because there’s a slight delay as the tab gets reloaded, is a rather difficult exercise, and we never got satisfactory results. We have now approached the problem again by refining our low-memory detection and tab selection algorithm and narrowing the action to the case where we are sure we’re providing a user benefit: if the browser is about to crash. Recently we have been conducting an experiment on our Nightly channel to monitor how tab unloading affects browser use and the number of crashes our users encounter. We’ve seen encouraging results with that experiment. We’ll continue to monitor the results as the feature ships in Firefox 93. With our experiment on the Nightly channel, we hoped to see a decrease in the number of OOM crashes hit by our users. However, after the month-long experiment, we found an overall significant decrease in browser crashes and content process crashes. Of those remaining crashes, we saw an *increase* in OOM crashes. Most encouragingly, people who had tab unloading enabled were able to use the browser for longer periods of time. We also found that average memory usage of the browser *increased.* The latter may seem very counter-intuitive, but is easily explained by survivorship bias. Much like in the [archetypal example of the Allied WWII bombers with bullet holes](https://en.wikipedia.org/wiki/Survivorship_bias#In_the_military), browser sessions that had such high memory usage would have crashed and burned in the past, but are now able to survive by unloading tabs just before hitting the critical threshold. The increase in OOM crashes, also very counter-intuitive, is harder to explain. Before tab unloading was introduced, Firefox already responded to Windows memory-pressure by triggering an internal memory-pressure event, allowing subsystems to reduce their memory use. With tab unloading, this event is fired after all possible unloadable tabs have been unloaded. This may account for the difference. Another hypothesis is that it’s possible our tab unloading sometimes kicks in a fraction too late and finds the tabs in a state where they can’t even be safely unloaded any more. For example, unloading a tab requires a garbage collection pass over its JavaScript heap. This needs some additional temporary storage that is not available, leading to the tab crashing instead of being unloaded but still saving the entire browser from going down. We’re working on improving our understanding of this problem and the relevant heuristics. But given the clearly improved outcomes for users, we felt there was no point in holding back the feature. ## When does Firefox automatically unload tabs? When system memory is critically low, Firefox will begin automatically unloading tabs. Unloading tabs could disturb users’ browsing sessions so the approach aims to unload tabs only when necessary to avoid crashes. On Windows, Firefox gets a notification from the operating system (setup using [CreateMemoryResourceNotification](https://docs.microsoft.com/en-us/windows/win32/api/memoryapi/nf-memoryapi-creatememoryresourcenotification)) indicating that the available physical memory is running low. The threshold for low physical memory is not documented, but appears to be around 6%. Once that occurs, Firefox starts periodically checking the commit space ([MEMORYSTATUSEX.ullAvailPageFile](https://docs.microsoft.com/en-us/windows/win32/api/sysinfoapi/ns-sysinfoapi-memorystatusex)). When the commit space reaches a low-memory threshold, which is defined with the preference “browser.low\_commit\_space\_threshold\_mb”, Firefox will unload one tab, or if there are no unloadable tabs, trigger the Firefox-internal memory-pressure warning allowing subsystems in the browser to reduce their memory use. The browser then waits for a short period of time before checking commit space again and then repeating this process until available commit space is above the threshold. We found the checks on commit space to be essential for predicting when a real out-of-memory situation is happening. As long as there is still swap AND physical memory available, there is no problem. If we run out of physical memory and there is swap, performance will crater due to paging, but we won’t crash. On Windows, allocations fail and applications will crash if there is low commit space in the system even though there is physical memory available because Windows does not overcommit memory and can refuse to allocate virtual memory to the process in this case. In other words, unlike Linux, Windows always requires commit space to allocate memory. How do we end up in this situation? If some applications allocate memory but do not touch it, Windows does not assign the physical memory to such untouched memory. We have observed graphics drivers doing this, leading to low swap space when plenty of physical memory is available. In addition, [crash data](https://bugzilla.mozilla.org/show_bug.cgi?id=1711610) we collected indicated that a surprising number of users with beefy machines were in this situation, some perhaps thinking that because they had a lot of memory in their machine, the Windows swap could be reduced to the bare minimum. You can see why this is not a good idea! ## How does Firefox choose which tabs to unload first? Ideally, only tabs that are no longer needed will be unloaded and the user will eventually restart the browser or close unloaded tabs before ever reloading them. A natural metric is to consider when the user has last used a tab. Firefox unloads tabs in least-recently-used order. Tabs playing sound, using picture-in-picture, pinned tabs, or tabs using WebRTC (which is used for video and audio conferencing sites) are weighted more heavily so they are less likely to be unloaded. Tabs in the foreground are never unloaded. We plan to do more experiments and continue to tune the algorithm, aiming to reduce crashes while maintaining performance and being unobtrusive to the user. ## about:unloads For diagnostic and testing purposes, a new page about:unloads has been added to display the tabs in their unload-priority-order and to manually trigger tab unloading. This feature is currently in beta and will ship with Firefox 94. ![Screenshot of the about:unloads page in beta planned for Firefox 94.](https://2r4s9p1yi1fa2jd7j43zph8r-wpengine.netdna-ssl.com/files/2021/10/AboutUnloads-250x199.png) Screenshot of the about:unloads page in beta planned for Firefox 94. ## Browser Extensions Some browser extensions already offer users the ability to unload tabs. We expect these extensions to interoperate with automatic tab unloading as they use the same underlying [tabs.discard() API](https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/API/tabs/discard). Although it may change in the future, today automatic tab unloading only occurs when system memory is critically low, which is a low-level system metric that is not exposed by the WebExtensions API. (Note: an extension could use the [native messaging support](https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/Native_messaging) in the WebExtensions API to accomplish this with a separate application.) Users will still be able to benefit from tab unloading extensions and those extensions may offer more control over when tabs are unloaded, or deploy more aggressive heuristics to save more memory. Let us know how it works for you by leaving feedback on [ideas.mozilla.org](https://ideas.mozilla.org) or [reporting a bug](https://bugzilla.mozilla.org/enter_bug.cgi?product=Firefox&component=Tabbed+Browser). For support, visit [support.mozilla.org](https://support.mozilla.org).Firefox crash reporting and telemetry adheres to our [data privacy principles](https://www.mozilla.org/en-US/privacy/principles/). See the [Mozilla Privacy Policy](https://www.mozilla.org/en-US/privacy/) for more information. *Thanks to Gian-Carlo Pascutto, Toshihito Kikuchi, Gabriele Svelto, Neil Deakin, Kris Wright, and Chris Peterson, for their contributions to this blog post and their work on developing tab unloading in Firefox.*

## ✨ New * Firefox now supports the new AVIF image format, which is based on the modern and royalty free AV1 video codec. It offers significant bandwidth savings for sites compared to existing image formats. It also supports transparency and other advanced features. * Firefox PDF viewer now supports filling more forms (XFA-based forms, used by multiple governments and banks). [Learn more](https://support.mozilla.org/kb/view-pdf-files-firefox-or-choose-another-viewer#w_fill-out-forms-in-pdf-viewer). * When available system memory is critically low, Firefox on Windows will automatically unload tabs based on their last access time, memory usage, and other attributes. This should help reduce Firefox out-of-memory crashes. Switching to an unloaded tab automatically reloads it. * To prevent session loss for macOS users who are running Firefox from a mounted .dmg file, they’ll now be prompted to finish installation. This permission prompt only appears the first time these users run Firefox on their computer. * Firefox now blocks downloads that rely on insecure connections, protecting against potentially malicious or unsafe downloads. [Learn more](https://blog.mozilla.org/security/2021/10/05/firefox-93-protects-against-insecure-downloads/) and see where to find [downloads in Firefox](https://support.mozilla.org/kb/where-find-and-manage-downloaded-files-firefox#w_download-protection). * Improved web compatibility for privacy protections with SmartBlock 3.0. [Learn more](https://blog.mozilla.org/security/2021/10/05/firefox-93-features-an-improved-smartblock-and-new-referrer-tracking-protections/) * Introducing a new referrer tracking protection in Strict Tracking Protection and Private Browsing. [Learn more](https://blog.mozilla.org/security/2021/10/05/firefox-93-features-an-improved-smartblock-and-new-referrer-tracking-protections/) ## ✔️ Fixed * The VoiceOver screen reader now correctly reports checkable items in accessible tree controls as checked or unchecked. * The Orca screen reader now works correctly with Firefox, no longer requiring users to switch to another application after starting Firefox. * Various [security fixes](https://www.mozilla.org/security/advisories/mfsa2021-43/) ## ≡ Changed * TLS ciphersuites that use 3DES have been disabled. Such ciphersuites can only be enabled when deprecated versions of TLS are also enabled. [Learn more](https://blog.mozilla.org/security/2021/10/05/securing-connections-disabling-3des-in-firefox-93). * The download panel now follows the Firefox visual styles. ## 📊 Enterprise Various bug fixes and new policies have been implemented in the latest version of Firefox. See more details in the [Firefox for Enterprise 93 Release Notes](https://support.mozilla.org/kb/firefox-enterprise-93-release-notes). ## 🔧 Developer [Developer Information](https://developer.mozilla.org/docs/Mozilla/Firefox/Releases/93) ## 🌐 Web Platform The UI for [<input type="datetime-local">](https://developer.mozilla.org/docs/Web/HTML/Element/input/datetime-local) has been implemented. ## 👤 Community Contributions With the release of Firefox 93, we would like to express our gratitude to all the volunteers who have contributed code to this release, 12 of whom were first time contributors! Please join us in thanking each of these diligent and enthusiastic individuals, and take a look at their contributions: * cwinter158: [1604914](https://bugzilla.mozilla.org/show_bug.cgi?id=1604914) * dalesionpt: [1723224](https://bugzilla.mozilla.org/show_bug.cgi?id=1723224) * diomede979: [1690415](https://bugzilla.mozilla.org/show_bug.cgi?id=1690415) * henry: [1725496](https://bugzilla.mozilla.org/show_bug.cgi?id=1725496) * kpatenio: [1609558](https://bugzilla.mozilla.org/show_bug.cgi?id=1609558), [1625478](https://bugzilla.mozilla.org/show_bug.cgi?id=1625478), [1727197](https://bugzilla.mozilla.org/show_bug.cgi?id=1727197) * Alex Finder: [1727919](https://bugzilla.mozilla.org/show_bug.cgi?id=1727919) * Fernando García Gómez, stripTM: [1283388](https://bugzilla.mozilla.org/show_bug.cgi?id=1283388) * Gerard A. Robinson: [1722223](https://bugzilla.mozilla.org/show_bug.cgi?id=1722223) * Haiyang Xu: [1727710](https://bugzilla.mozilla.org/show_bug.cgi?id=1727710) * Jacek Kuzemczak: [1719124](https://bugzilla.mozilla.org/show_bug.cgi?id=1719124) * Mohit: [1721825](https://bugzilla.mozilla.org/show_bug.cgi?id=1721825) * Niklas Baumgardner: [1635548](https://bugzilla.mozilla.org/show_bug.cgi?id=1635548), [1724792](https://bugzilla.mozilla.org/show_bug.cgi?id=1724792), [1728458](https://bugzilla.mozilla.org/show_bug.cgi?id=1728458) * Ruben Calvo: [1728366](https://bugzilla.mozilla.org/show_bug.cgi?id=1728366) * Tzvika Ofek: [1723820](https://bugzilla.mozilla.org/show_bug.cgi?id=1723820) * cschanaj: [1510664](https://bugzilla.mozilla.org/show_bug.cgi?id=1510664) * gstrauss: [472823](https://bugzilla.mozilla.org/show_bug.cgi?id=472823)

*You can also use your phone to enable third-party controllers.* --- You don't need to use the official [Stadia Controller](https://www.engadget.com/google-is-now-offering-a-permanent-chromecast-and-stadia-controller-bundle-053733986.html) if you want to use Google's game streaming service on your TV — or any dedicated controller, for that matter. Google is rolling out a feature that lets TV-bound Stadia players use their Android phone or iPhone as a virtual gamepad. You can also use third-party gamepads by connecting them to your phone through Bluetooth or USB. The widened controller support requires Android TV, [Google TV](https://www.engadget.com/chromecast-with-google-tv-review-163024220.html) or a Chromecast Ultra. In most cases, you'll need to either add a controller or enable the touch gamepad through the Stadia mobile app, and promptly choose "play on TV." Android TV and Google TV owners will also need to enable a controller through the avatar section on the big-screen Stadia app. This might help boost Stadia's adoption. While it has long given you the flexibility of where you can play, you haven't had many choices for that setup. It's now relatively easy to use a favorite gamepad with your TV or, if you prefer, save a little money and use no gamepad at all. It won't be perfect, however. A phone's touchscreen can only do so much, and using your phone as a go-between is bound to add a little latency.

This release brings you working imports from your YouTube subscriptions export, an “always go into full screen” toggle when you play a video via the main player, a new Invidious instance, and so much more that you basically have to read on. ## New * Rejoice! [@talanc](https://github.com/talanc) fixed an issue plaguing users since late July: Google changed the way it exports subscriptions from YouTube, rendering the previous import into NewPipe non-functional. You can now import your downloaded [CSV](https://en.wikipedia.org/wiki/Comma-separated_values) file, or even the ZIP file that contains that CSV, directly into NewPipe! * The behaviour of long press on the player queue was streamlined by [@ktprograms](https://github.com/ktprograms): It now also displays the popup menu from the main player. * A cool new setting was added by [@Stypox](https://github.com/Stypox): You can now automatically have videos playing in full screen if you use the main player. * [@Stypox](https://github.com/Stypox) also split search suggestions into two categories: local and remote. Now you have the option to enable or disable them independently of each other. * [@magicbrothers](https://github.com/magicbrothers) added a new Invidious instance, Tubus, meant for educational videos for children. * [@ktprograms](https://github.com/ktprograms) finished the ongoing work of adding the “Show channel details” option where it was still missing, that is, in local playlists, feed items, and history items. ### Improved * [@sauravrao637](https://github.com/sauravrao637) modified the app colours to be a bit darker when the dark theme is selected in the app, which looks loads better to us! He further added a darker splash screen variant when the OS’s theme is set to dark. We hope you like the new look too! * [@Stypox](https://github.com/Stypox) replaced the outdated Android-Universal-Image-Loader library (which has not had any new release in the last 6 years) with the more stable and updated Picasso, a library to download and cache images on Android (think all the thumbnails you see in the app). This fixes a nasty issue where the wrong notification thumbnail size could crash the whole System UI or even forcibly reboot the device! It also makes loading cached images instantaneous, and loading non-cached images smoother. * [@sherlockbeard](https://github.com/sherlockbeard) changed the “video not available” image from a static PNG to a vector XML image, allowing it to scale properly for screens of all sizes. * [@Stypox](https://github.com/Stypox) added the mime-type field to all calls to the SAF file picker, which causes files with the incorrect file format to be greyed out and become non-selectable. This will ensure the user can only choose a ZIP file when importing their database, for example. This should be a great quality-of-life improvement for many users! ### Fixed * [@litetex](https://github.com/litetex), together with [@Stypox](https://github.com/Stypox), improved the comments parsing for timestamps, which could have resulted in a crash if it happened in the wrong place at the wrong time. * [@Aga-C](https://github.com/Aga-C) added line wrapping to the settings texts, so they don’t get truncated anymore. * [@acti0](https://github.com/acti0) fixed a regression from a past release where the name of the video wasn’t being shared when sharing the video URL. * [@litetex](https://github.com/litetex) fixed a bug where you had to tap the Replay button twice for it to actually work. * While [@litetex](https://github.com/litetex) fixed the Replay button, they also fixed the direction buttons on D-Pads for Android TV users: the seekbar now jumps only 10 seconds, instead of several minutes. * [@litetex](https://github.com/litetex), being on a roll, reworked the error panel shown when an error happens. This results in a clearer error display. * [@Redirion](https://github.com/Redirion) implemented proper closure of audio streams when playback is stopped. This fixed a longstanding bug where NewPipe would create more and more audio sessions but use only one. This messed with equaliser apps. * [@TobiGr](https://github.com/tobigr) added proper error handling which might occur when trying to play a video in popup mode or get a search suggestion. * [@TobiGr](https://github.com/tobigr) also took care of a small UI bug: when one played something in the minimized player and changed the visibility of the description tab in the meantime, the visibility of the comments tab was changed instead. The app isn’t confused anymore, we cannot say the same about the dev… ## Translation * [@Stypox](https://github.com/Stypox) switched to using the custom cancel string everywhere, which is translated to more languages than the default android cancel string. * They jumped onto that plane and replaced a couple more strings to better translated ones: “ok”, “yes”, “no”, and “cancel”. They also removed “add”, and renamed “finish” to “ok”, because it clearly means “ok”, not “finish”! * [@Aga-C](https://github.com/Aga-C) added plural forms for download-related strings. * [@CBSkarmory](https://github.com/CBSkarmory) improved some wording in the issue template; thanks! ## Nerd Talk * [@TobiGr](https://github.com/TobiGr) updated the hardcoded SoundCloud client ID. * [@FireMasterK](https://github.com/FireMasterK) added support for extracting the channel avatar on YouTube and PeerTube. * [@FireMasterK](https://github.com/FireMasterK) also added the `uploaderVerified` info to the `StreamInfo` class. * [@litetex](https://github.com/litetex) switched GitHub Actions to using the Eclipse Temurin Java distribution, as AdoptOpenJDK is getting deprecated. * [@Redirion](https://github.com/Redirion) replaced NewPipe’s custom buffer values with ExoPlayer’s default ones. * [@Isira-Seneviratne](https://github.com/Isira-Seneviratne) changed `PackageInfo` to its backwards-compatible version, `PackageInfoCompat` to fetch the app signatures. * [@litetex](https://github.com/litetex) also updated the version of Kotlin used everywhere, and fixed some build problems. * They also introduced a cache setting in the [CI](https://en.wikipedia.org/wiki/Continuous_integration) configuration which lets it run faster. * [@XiangRongLin](https://github.com/XiangRongLin) added a Gradle parameter to prevent KtLint, the Kotlin [linter](https://en.wikipedia.org/wiki/Lint_(software))+[formatter](https://en.wikipedia.org/wiki/Prettyprint#Programming_code_formatting), from being run twice in the GitHub Actions CI. * dependabot updates: * Bump gson from 2.8.7 to 2.8.8 * Bump spotbugs-annotations from 4.4.0 to 4.4.1 ## Where to get this brand-new version NewPipe notifies you about new versions. You can download them when you press the notification, which will take you to the [GitHub Releases page](https://github.com/TeamNewPipe/NewPipe/releases). If you use the [F-Droid app](https://f-droid.org/), it, too, notifies you about updates for [NewPipe](https://f-droid.org/packages/org.schabi.newpipe/). Please keep in mind that it can take F-Droid a while to update their repository. If you have problems installing the update, you may need to uninstall NewPipe and then install it afresh. (Make sure to backup data by exporting your database from the `Settings > Content` menu.) If you already installed NewPipe from F-Droid’s repository, to get this version of NewPipe you can do one of the following: * Wait for them to update * Switch to NewPipe’s custom repository by following the [directions in the announcement post](https://newpipe.net/blog/announcement/f-droid/pinned/f-droid-repo/) Note: If you installed NewPipe from GitHub Releases you will not have to uninstall NewPipe to switch to our custom repo. Just let it update your current version. Make sure you back up your data as mentioned in the warning at the top of the FAQ page! Now that you’ve (hopefully) updated, please let us know what your experience of the latest release is, especially bugs in need of fixing. As usual, you can reach out to us via IRC ([#newpipe on Libera.Chat](https://web.libera.chat/#newpipe)), [open issues on GitHub](https://github.com/TeamNewPipe/NewPipe/issues/new) or, ideally, use our built-in crash reporter to send us machine-readable issue reports. You can even [send in fixes](https://github.com/TeamNewPipe/NewPipe/blob/dev/.github/CONTRIBUTING.md#bug-fixing) yourself. If you have any other questions, feel free to post them in the comments here and someone will reply to you. Also, thanks for reading the blog post till the end! We put quite some time into writing them.

1. **Native GUI install program for Linux. (x86\_64/i386/aarch64/mips64) (GTK/QT)** [Notes](https://www.ventoy.net/en/doc_linux_gui.html) 2. Add support for Emergency Boot Kit 3. Continue to boot when the ISO file size is invalid. 4. Fix a bug when booting puppy-4.3.1 5. languages.json update See [https://www.ventoy.net/en/doc\_news.html](https://www.ventoy.net/en/doc_news.html) for more details. **SHA-256** ``` ventoy-1.0.52-windows.zip: 0b7357e28f95a03bc70f7774c9a8b0062f1ee39057bccf29e21d18726079b0b5 ventoy-1.0.52-linux.tar.gz: ed1120bcaa63ee810fb8bd712964c73057f70c7648be3125f45e639599a631c2 ventoy-1.0.52-livecd.iso: 67b47da686d024e31be0f6085aa863a2bc0dacc8252ea15e60ac4837fbe3dc88 ventoy-1.0.52-livecd.iso.zip: 44db79eee0ff1a40d4241876d38625e770d09f270378ce799a18e5197aecd208 ```

### Added - Support for Lemmy v0.12.0 - Show cake day on a user's profile and next to their name in a comment