• 13 Posts
  • 98 Comments
Joined 3Y ago
cake
Cake day: Apr 18, 2019

help-circle
rss

And End-to-End Encryption (E2EE), which is great privacy-wise as it gives you the flexibility to choose any cloud provider despite what they claim about privacy.


Let’s do some digging and put some sources to those images

https://lemmy.ml/post/345928
https://www.businessinsider.com/i-tried-the-new-mcdonalds-russia-tastes-pretty-much-same-2022-6

https://lemmy.ml/post/345290
https://twitter.com/blaircottrell89 (Twitter account suspended, no trace of the tweet in the Wayback Machine)

https://en.wikipedia.org/wiki/Blair_Cottrell
Blair Cottrell (born November 1989) is an Australian far-right extremist, often described as a neo-Nazi.

https://lemmy.ml/post/345883
https://www.federalbudgetinpictures.com/two-centuries-of-debt-in-27-months/

2016 by The Heritage Foundation. All Rights Reserved.
https://en.wikipedia.org/wiki/The_Heritage_Foundation
The Heritage Foundation (abbreviated to Heritage) is an American conservative think tank based in Washington, D.C., primarily geared towards public policy. The foundation took a leading role in the conservative movement during the presidency of Ronald Reagan, whose policies were taken from Heritage’s policy study Mandate for Leadership.

https://lemmy.ml/post/345838
https://www.theguardian.com/global-development/2020/nov/06/child-labour-doesnt-have-to-be-exploitation-it-gave-me-life-skills

I took the liberty of archiving all these in the Wayback Machine to make sure they won’t vanish to time.


Just tried and it didn’t. I also made sure that my uBlock Origin filters weren’t interfering.


I wish it would strip all the url parameters crap that are in Amazon URLs.






Instead of playing Candy crush saga in an elevator

I’m not going to do some CV in the elevator lol

But on a more serious note, that is a nice proejct.


Seeking validation online is basically a drug for some.


And significantly increased her paycheck right before canning a bunch of developers.


Right now whatever system the maintainer prefers. I currently donate monthly to a GitHub project I really care about using the sponsor feature.


The issue is that most of us put all of our eggs in the same basket. These important repos needs to be mirrored to as many instances as possible.


oauth option

which might go away if the K-9 devs are forced to pay a yearly and expensive security audit to keep it.


And to add on this, the Lemmy platform evolves quite fast lately, so it must also be quite a challenge to keep the app in sync feature-wise.

I’m currently using Jerboa and it works well for what I do on Lemmy, thanks for your work on this :)

There’s still some stuff I can do like pinning a submission in a community, but it’s not a big issue to go on the web version to do so once in a while.


It was relatively easy for me. I wasn’t really social either, I didn’t make really any close friends while at school, and I didn’t keep in touch with them either. I just have my small circle of friends now, and I like it that way. I didn’t find high school to be particularly useful knowledge-wise, just as a mean to an end.

To be honest, I learned a lot of tech before going specializing in it out of sheer curiosity and passion, but getting the actual diploma helped me getting where I am today. Technology is a vast domain, and sure there is some stuff you need to memorize and you need to understands the basics to have a good foundation, but some of it you only get good at it by understanding a vast array of concepts, a bit like medicine (even if a bit presomptuous). Some are better than the others to quickly grasps those concepts, and they don’t really teach you how to make those connections, and frankly that’s the interesting part.

I’m pretty sure it gave me the edge against some who didn’t have any diploma at first, but now my CV is mostly speaking for itself. I don’t really have trouble finding work that pays a salary that suits my consumption habits (I’m tend to save as much as I can, to spend when I really need to), and I find my life as a whole as satisfying.



All this could have been avoided if Google made a permission for it.


To access and subscribe to it through lemmy.ml

https://lemmy.ml/c/usa@lemmy.perthchat.org

EDIT: You can also follow and submit to it through Mastodon by following and posting to the @usa@lemmy.perthchat.org group. Example: https://mastodon.social/web/@usa@lemmy.perthchat.org

The joy of ActivityPub and the Fediverse.


Regarding Neat URL, ClearURLs, anyone has a filter list for uBlock Origin to suggest that remove most tracking parameters from URLs?


Which is a feature privacy-wise. Personally I subscribe to channels I want to follow locally, make local playlists and export them periodically to retain my data.


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

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.*
fedilink

## ✨ 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)
fedilink

*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.
fedilink

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 ```
fedilink

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


**Organic Maps** is an Android & iOS offline maps app for travelers, tourists, hikers, and cyclists based on top of crowd-sourced **OpenStreetMap** data and curated with love by **MapsWithMe** founders. * [Apple App Store](https://apps.apple.com/app/organic-maps/id1567437057) * [Google Play Store](https://play.google.com/store/apps/details?id=app.organicmaps) * [F-Droid](https://f-droid.org/en/packages/app.organicmaps/) * [Huawei AppGallery](https://appgallery.huawei.com/#/app/C104325611) * [GitHub](https://github.com/organicmaps/organicmaps) ## Features Organic Maps is the ultimate companion app for travelers, tourists, hikers, and cyclists: * Detailed offline maps with places that don't exist on other maps * Cycling routes, hiking trails, and walking paths * Contour lines, elevation profiles, peaks, and slopes * Turn-by-turn walking, cycling, and car navigation with voice guidance * Fast offline search on the map and bookmarks * Dark Mode to protect your eyes ## Why Organic? Organic Maps is pure and organic, made with love: * Respects your privacy * Saves your battery * No unexpected mobile data charges Organic Maps is free from trackers and other bad stuff: * No ads * No tracking * No data collection * No phoning home * No annoying registration * No mandatory tutorials * No noisy email spam * No push notifications * No crapware * No pesticides
fedilink

🧲 Magnet Link 🧲 `magnet:?xt=urn:btih:6def4d028d76c6f02590bb062be4ad5cbf4e76fb&dn=elementaryos-6.0-stable.20210810.iso&tr=https%3A%2F%2Fashrise.com%3A443%2Fphoenix%2Fannounce&tr=udp%3A%2F%2Fopen.demonii.com%3A1337%2Fannounce&tr=udp%3A%2F%2Ftracker.openbittorrent.com%3A80%2Fannounce`
fedilink

Tails 4.20
# *Tor Connection* assistant Tails 4.20 completely changes how to connect to the Tor network from Tails. After connecting to a local network, a *Tor Connection* assistant helps you connect to the Tor network. This new assistant is most useful for users who are at high risk of physical surveillance, under heavy network censorship, or on a poor Internet connection: * It protects better the users who need to go unnoticed if using Tor could look suspicious to someone who monitors their Internet connection (parental control, abusive partner, school or work network, etc.). * It allows people who need to connect to Tor using bridges to configure them without having to change the default configuration in the Welcome Screen. * It helps first-time users understand how to connect to a local Wi-Fi network. * It provides feedback while connecting to Tor and helps troubleshoot network problems. We know that this assistant is still far from being perfect, even if we have been working on this assistant since February. If anything is unclear, confusing, or not working as you would expect, please send your feedback to [tails-dev@boum.org](mailto:tails-dev@boum.org) (public mailing list). This first release of the *Tor Connection* assistant is only a first step. We will add more improvements to it in the coming months to: * Save Tor bridges to the Persistent Storage ([#5461](https://gitlab.tails.boum.org/tails/tails/-/issues/5461)) * Help detect when Wi-Fi is not working ([#14534](https://gitlab.tails.boum.org/tails/tails/-/issues/14534)) * Detect if you have to sign in to the local network using a captive portal ([#5785](https://gitlab.tails.boum.org/tails/tails/-/issues/5785)) * Synchronize the clock to make it easier to use Tor bridges in Asia ([#15548](https://gitlab.tails.boum.org/tails/tails/-/issues/15548)) * Make it easier to learn about new Tor bridges ([#18219](https://gitlab.tails.boum.org/tails/tails/-/issues/18219), [#15331](https://gitlab.tails.boum.org/tails/tails/-/issues/15331)) # Changes and updates * Update *OnionShare* from 1.3.2 to [2.2](https://github.com/micahflee/onionshare/blob/develop/CHANGELOG.md#22). This major update adds a feature to [host a website](https://docs.onionshare.org/2.3.2/en/features.html#host-a-website) accessible from a Tor onion service. * Update *KeePassXC* from 2.5.4 to [2.6.2](https://github.com/keepassxreboot/keepassxc/blob/master/CHANGELOG.md#262-2020-10-21). This major update comes with a redesign of the interface. * Update *Tor Browser* to [10.5.2](https://blog.torproject.org/new-release-tor-browser-1052). * Update *Thunderbird* to [78.11.0](https://www.thunderbird.net/en-US/thunderbird/78.11.0/releasenotes/). * Update *Tor* to 0.4.5.9. * Update the *Linux* kernel to 5.10.46. This should improve the support for newer hardware (graphics, Wi-Fi, and so on). * Rename *MAC address spoofing* as *MAC address anonymization* in the Welcome Screen. # Fixed problems ### Automatic upgrades * Made the download of upgrades and the handling of errors more robust. ([#18162](https://gitlab.tails.boum.org/tails/tails/-/issues/18162)) * Display an error message when failing to check for available upgrades. ([#18238](https://gitlab.tails.boum.org/tails/tails/-/issues/18238)) ### Tails Installer * Made the display of the **Reinstall** button more robust. ([#18300](https://gitlab.tails.boum.org/tails/tails/-/issues/18300)) * Make the **Install** and **Upgrade** unavailable after a USB stick is removed. ([#18346](https://gitlab.tails.boum.org/tails/tails/-/issues/18346)) For more details, read our [changelog](https://gitlab.tails.boum.org/tails/tails/-/blob/master/debian/changelog). # Known issues * Automatic upgrades are broken from Tails 4.14 and earlier. To upgrade from Tails 4.14 or earlier, you can either: * Do a [manual upgrade](https://tails.boum.org/news/version_4.20/index.en.html../../doc/upgrade/index.en.html#manual). * Fix the automatic upgrade from a terminal. To do so: 1. Start Tails and set up an [administration password](https://tails.boum.org/news/version_4.20/index.en.html../../doc/first_steps/welcome_screen/administration_password/index.en.html). 2. In a terminal, execute the following command: ``` torsocks curl --silent https://tails.boum.org/isrg-root-x1-cross-signed.pem \ | sudo tee --append /usr/local/etc/ssl/certs/tails.boum.org-CA.pem \ && systemctl --user restart tails-upgrade-frontend ``` This command is a single command that wraps across several lines. Copy and paste the entire block at once and make sure that it executes as a single command. 3. Approximately 30 seconds later, you should be prompted to upgrade to the latest version of Tails. If no prompt appears, you might already be running the latest version of Tails. See the list of [long-standing issues](https://tails.boum.org/news/version_4.20/index.en.html../../support/known_issues/index.en.html).
fedilink

By now, the process of creating custom lithium-ion battery packs is well-known enough to be within the reach of most makers. But it’s not a path without hazard, and mistakes with battery protection and management can be costly. Happily for those who are apprehensive on the battery front there’s a solution courtesy of a group of engineering students from the University of Pittsburgh. [Their project was to convert a pedal bicycle to electric assisted power](https://hackaday.io/project/180098-diy-ebike-battery-system), and in doing so they didn’t make their own pack but instead used off-the-shelf 40V Ryobi power tool packs. The bike conversion is relatively conventional with the crank replaced by a crank and motor assembly, and a pair of the Ryobi packs in 3D-printed holders on the frame. The value in this is in its reminder that these packs have evolved to the point at which they make a viable alternative to a much more expensive bike-specific pack, and that their inclusion of all the balancing and protection circuitry make them also a much safer option than building your own pack. The benefits of this are immense as they bring a good-quality conversion within reach of many more bicycle owners, with all parts being only a simple online order away. Take a look at the video below the break for more details. Those Ryobi cells [certainly seem to have carved themselves a niche](https://hackaday.com/2020/02/20/diy-power-station-puts-ryobi-batteries-to-work/) in our community! [![https://i.ytimg.com/vi/FgjxSFlo72g/maxresdefault.jpg](https://i.ytimg.com/vi/FgjxSFlo72g/maxresdefault.jpg)](https://youtu.be/FgjxSFlo72g)
fedilink