Gotcha, that sounds like searx is a good option then. At first I thought you were giving a reason why searx isn't a suitable alternative as the gp comment is downvoted a bunch.

Can't you just not enable the Yandex backend if you're selfhosting searx?

I use the open source bitwarden server vaultwarden, but still use the official browser plugin and Android app - though I wonder if this library license change would affect open source client implementations by requiring third party extensions and apps to implement their own compatible BitWarden API. The cynic in me wonders if that could be a move to make it harder on developers of third party clients in an effort to strengthen the position of the official clients even when using a third party server like vaultwarden. I never really considered using a foss bit/vaultwarden browser extension or Android app but maybe I should if it exists.

Someone correct me if I'm interpreting the license issue wrong.

Sounds like those "soft touch" plastic surfaces. I've had a bunch of old plastic things turn sticky that way - it's really hard to get it off but what I do is alternate between isopropyl, WD40 (brushed on with a cotton swab or cotton ball and let it sit for a while to let it break down the sticky before using Clorox or isopropyl to remove the WD40), and Clorox wipes. Eventually the matte finish comes off and you're left with a shiny plastic surface. It just takes a lot of elbow grease, I often give myself finger blisters from scrubbing but it's a relief to get it off.

Edit: also the last time I did this was on some old lighters which had a soft touch plastic which turned sticky, what ended up happening was the WD40 seemed to help soften the sticky stuff which allowed me to push it around by rubbing really firmly in one direction. If you push it towards one spot it'll bunch up like softened sticker goo, then I use Clorox wipes to pinch up the bits of collected goo. It still took a lot of rubbing to get the last sticky stuff off to reveal the shiny plastic underneath but "migrating" the goo into a pile once softened by the WD40 (but degreasing the excess WD40 with the Clorox wipes before rubbing so that your finger doesn't just slip) seemed to be the strategy for my sticky lighters.

Hope that helps you figure out something that works for you

If only they would do damage control for the climate instead of just their image.

Imagine accidentally leaving one of those things open and then ripping off the door by moving the desk lift thing

Oh nice, I completely forgot about the vault export since I've never used it. I was expecting to be able to "view" the passkey data when editing an entry like how you can view the password. It's kind of inscrutable when viewing a single entry currently.

The key difference is that during normal use, the private key of the passkey doesn't leave the device (or password manager). The passkey basically comes in 2 parts, the public and private (secret) part. In order to log in, the website presents a cryptographic challenge that is only solvable using your private key - and crucially you can solve the challenge without revealing your private key. An attacker could get your answer to the challenge and still be unable to solve additional challenges without the private part of your passkey.

This of course makes it basically impossible to manually log in using a passkey and a keyboard, without any password manager to do the cryptographic calculations (unless you have a LOT of paper and time), but the security advantage of making it near impossible to be phished is generally regarded as a net positive. In order to steal a passkey there would need to be a vulnerability in the software, since passkeys make it much harder to trick a user into giving it away (since tricking the user into logging in on a fake website doesn't work due to the aforementioned cryptography, the main way to steal a passkey would be to trick the user into exporting it - which is a much higher bar).

If you mean the "passkeys" that are becoming popular as a "password replacement", it's basically speaking a public private keypair. What makes it more secure is that, under normal conditions (aside from backing up the passkey), the private "secret" part of the keypair never leaves the app or device it's stored on. It's only used temporarily to sign messages and prove that you have the secret key, unlike a password which needs to be sent securely to a server to validate.

You could in theory store a backup on a USB drive but since passkeys are new, it highly depends on the password manager you use to store the passkey. Since passkeys are more complex than something you can memorize/type, it has to be stored in a password manager of some sort to be useful, so you would need to check that password manager allows backing up passkeys. There is currently work being done to standardize the formats/protocols to transfer passkeys so it seems this is very much up in the air. For example, I use BitWarden which stores passkeys, but it seems like I can only add or delete passkeys to an entry, not export them and apparently they get exported with the passwords when the vault is exported. BitWarden also syncs your vault to every logged in device though so you could see that as a form of backup. Going one step further, even though BitWarden doesn't have a passkey export/backup feature yet (in addition to Bitwarden's vault export), the self-hosted server also stores all your passwords including passkeys in regular files which also can be backed up (this is how I back up my VaultWarden instance) - although it would probably be hard to use that backup in any other way besides restoring it onto a BitWarden server instance.

Edit: I didn't realize passkeys were exported with the vault export, since I haven't used it and noticed that editing an entry doesn't allow you to view passkey data - only remove, updated my comment to reflect that.

I concur about rechargeables - it doesn't seem common for devices that take AA or AAA to have a battery gauge and it would be nice to be able to check the level on my rechargeables stock so I can know if I should top them off without needing to put each of them into the charger.

This is apparently partially about exclusive deals that bar app developers from putting their apps on additional third party app stores.

First I'll say, if you aren't able to boot a windows installer off of a flash drive (and nothing's wrong with your flash drive and you created it without errors and there isn't a setting in bios preventing you from booting it like disabled USB boot) then it could be a hardware issue that Linux won't fix (it's not clear how you tried to reinstall windows). But if you're able to get to the windows logo or the menu for safe mode then it sounds like it "POSTs" (gets past showing the bios screen) and windows should be reinstallable. In short, I think it's unlikely to be a problem that only Linux can fix if you want to stick with windows.

That said, if you are otherwise interested in trying Linux and create a USB installer, most will allow you to exit the installer or choose to go into a temporary "live desktop" where nothing is saved, so it's a good opportunity to try out how that distro feels to use - just don't save anything important. And if you do end up installing either OS, you can use that "live mode" to use programs to back up any files from your main hard drive to another plugged in drive.

Have you tried some of the APK extractor apps on the play store? I use one of them but ironically the one I use isn't on the play store anymore. I don't have root and it works for me.

If I'm understanding it correctly it looks like you drew out the whole pattern? There's a pattern tool that lets you repeat some parts of the sketch. You can use it for hexagonal patterns by drawing a construction line from the center of the first hexagon to the middle of one of the sides. Do that for 2 adjacent sides and then select those lines as your 2 axes for the pattern tool and it'll repeat in a hexagonal pattern.

Oh nice where was it? Might help anyone else having the same problem.

I had the same impression, but it also doesn't seem like apps group cross posts (at least sync doesn't) so if you don't wait between posts they end up next to each other in the all feed.

That sounds like an ombi issue, as I understand it the minimum availability is only a per-movie setting and can't be set globally so you'll need to figure out why ombi isn't setting it correctly when adding to radarr. Unfortunately I can't offer any tips for ombi because I use overseerr

Is that petg? For some reason I usually have problems with petg and infill patterns that cross over itself so I usually switch to gyroid. I think it has something to do with the speed and flow and the properties of the filament that make it especially bad when the infill lines cross over itself. You can probably tune temps, speeds, and feeds to get it to work but I find it easier to just not use that infill pattern.

At least with radicle all the forks will still exist even if the authoritative copy is taken down. And even then I think because radicle is like BitTorrent, anybody who pinned the main repo would still be seeding it so it would be very hard to scrub it completely. The main challenge in using radicle is getting an active contributor with some reputation to maintain their copy on there. Otherwise there's no momentum and nobody will pin the countless mirrors published by randos.

Either that or charging a micro transaction for loading the page. But yeah the goal is to make it cost a small amount that is insignificant to a regular user but adds up to a huge amount at the scale of a spam farm. And it's also the same rationale behind hashing passwords with multiple rounds. It adds a tiny lag when you log in correctly but adds an insane amount of work if you're checking every phrase in a password cracking dictionary using an offline attack because it adds up. (In the online scenario you just block them after a few attempts)