• 21 Posts
  • 221 Comments
Joined vor 3 Jahren
cake
Cake day: Apr. 18, 2019

help-circle
rss

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.


I suppose my standards about what I find interesting enough to publish on Lemmy are high, so I don’t post unless that bar is met.


I personally get the Blu-Ray ISO of the movie containing the languages I want and convert them to the format I want using HandBrake. It’s easier to find what I want this way instead of looking for a premade file.


I like Lemmy, but Reddit does have a lot of momentum, and unless there’s a huge controversy or a significant portion of the community is displeased enough to seriously look into alternative, I don’t see Lemmy catch up with Reddit. But that can be a good thing too, as a small community is usually more tight-knitted.


My dog definitely doesn’t follow the alignment, as he mostly do a circle of poop around him, by rotating while shitting 😂

Or he either look at me, asserting his dominance while pushing one out.



Termux used IPFS for their package management temporarily while there we looking for another host, and IIRC it worked well enough.

https://github.com/termux/termux-packages/issues/6846



I searched up

where?

You don’t have to look very far in time to see how inbreeding caused a plethora of issues to the Habsburg’s lineage in roughly 16 generations. Incest would make existing issues likely even worse, considering how close genetically the parents would be compared to inbreeding.


I just block the accounts that spam that kind of stuff, it’s not like I’m gonna engage with them anyway so…


Still going strong on my 15 years old account. I don’t really seek confrontation, so my comments are at most average.


There’s rainy weather but I’m working from home in my pajamas and enjoying a cup of coffee with music in the background while working on my laptop.

I’m also preparing diner between support tickets. I’m enjoying the relaxed vibe.


There’s nothing that stops people from modding their games how they want, they just can’t host that kind of mod on NexusMods. If they’re adamant about it, they can self-host it or host it elsewhere.


No, it’s basically a CLI-based protocol, but I suppose someone might be able to build a web version by converting the source (Python) to WASM, which seems to be a work-in-progress.


From what I see, wormhole is using the wormhole-crypto protocol, while RiftShare is using the magic-wormhole protocol­.

Similar name, different protocol.


I went to Uni and worked as a reservist in the Canadian Armed Forces during week-ends and summers. The pay was good enough, they kept me fed, kept me in shape but it required a good discipline to make sure to meet my obligations with both.

I managed to get my degree with almost no student debt.


m-p{3}toCanada*Permananently Deleted*
link
fedilink
1
edit-2
2 Monate

In addition to engraving, you can submit your bike info in the 529 Garage service. That way if you bike is stolen you can send a broadcast to let all the other users in the area to keep their eyes open for a bike matching your description. That can only increase your chance of recovering your bike.

I believe they also provide access to their database to law enforcement.


Only as a mitigating factor if the stolen good is an essential product.


Most decentralized protocol requires something to start from, and those servers are known as a bootstrapping node.

BitTorrent for example, will use router.bittorrent.com:8991 to get the DHT populated, and once you have some nodes you can keep going (without the bootstrap server) from these trusted nodes as long as they keep responding.

If the bootstrap server goes down, then only new nodes will be able to use the DHT, while the current network will remain operational.





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
fedilink

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
fedilink




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

[iOS](https://apps.apple.com/app/verify-ontario/id1584425317) [Android](https://play.google.com/store/apps/details?id=ca.ontario.verify)
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
20

### 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