RyeMan

Your proxy settings will depend on your provider but if you search for network.proxy you'll see all the setting you need in there. You'll connect either through http (ip+port) or socks. Socks adds an additional layer of authentication which is generally preferred but likely won't be offered by free options.

Yes, your proxy service will absolutely see what sites you are visiting. None of these suggestions will protect you from a malicious proxy service. Https is still honored assuming the end point is using a valid cert and your proxy has not tampered with it in any way. If the cert gets altered you'll get a warning from your browser, you then have to trust yourself to know when to back out.

Unfortunately container tabs are not yet supported for Android Firefox. FoxyProxy is by no means malicious, it certainly has good intentions and for the most part it does what it says it does. The problem is that due to many fundamental design choices it is too easy for information to leak. Plus the URL regex matching can be very finicky to work with. I used FoxyProxy for years but gave up on it after a while since I could never get a consistent and reliable experience out of it.

At this point I just alter the proxy settings in Android ff directly - no extension. Unfortunately ff profiles are also not supported on Android yet so if you don't want your main browser to always be attached to a proxy you can install other releases of ff such as Nightly and just configure that with proxy settings. If I am recalling correctly, you can also configure ff to apply proxy to either normal or private browsing too.

Word of caution, If you are actually staying within the Onion network then sure Tor is a great option... The problem is most users just use the exit nodes to reach the clear web. This is a convenient feature of Tor but it's also the least secure use case. There are a very limited numbers of exit nodes so they are often overused and the majority of them are maintained by government controlled entities since it takes a certain level of legal protection to operate an exit node.

FoxyProxy has many DNS leaking bugs associated with the extension, especially when using SOCKS5 proxies. That extension has not been a recommended choice for a while now.

As others have said, a free proxy is not a good alternative, they are harvesting just as much data as your ISP, if not more (and possibly selling the info back to your ISP). Free proxies also have little incentive to be honest so there is a higher chance they could also be manipulating your traffic in various ways.

A better solution for mitigating data harvesting from your ISP is to just simply adjust your personal DNS settings. This can be configured globally on your router sometimes and/or each client device. Change your default DNS to a more privacy conscious provider such as Mullad, Quad9 or even Cloudflare. Those DNS providers also offer the option of making encrypted DNS requests using DNS over TLS (DoT) and DNS over HTTPS (DoH) which can be configured in your browser and sometimes your router.

At the end of the day, your ISP will still know you connected to a specific end point but they can't determine what exactly you are doing there, they only know you connected to something like Lemmy.world but would not be able to determine which communities you are visiting.

If a proxy still feels like the only solution then just buy a VPN subscription from a reputable source, its usually pretty cheap and way more effective at preserving privacy and security than any free proxy that is available. Mullvad is generally a pretty good and inexpensive choice plus they also have pretty decent proxy support.

As an alternative to FoxyProxy, check out the extension Container Proxy which allows you to containerize a tab and route all the traffic through a configured proxy which can also be configured on a site-by-site basis. Still, not perfect, but certainly a step above FoxyProxy.

Yeah if there is no physical damage then it's a level 1 recovery which tends to have better results. A "cooked" drive doesn't explain anything about the failure type but I have worked in computer repair for a number of years and it was very common for people to believe their HDD was fried when in fact it was not, sometimes misbehaving software can behave very similarly to a failing HDD. In those cases it's very simple to do a full data backup off the drive with folder structure still intact, coming from someone who's been behind the counter at BestBuy, they probably just did a regular data backup (while charging you for a recovery) if your data was still perfectly intact. They love to sell their data recovery service because it's expensive as hell and techs are actually told not to spend time on renaming and restructuring the data so the techs literally just run some freeware, walk away from your PC and then just hand you a USB (that you also pay for separately) with whatever results got spat out when it's done. Don't let them fool you though, Level 1 recovery pretty much anyone can do with some freeware (plenty of good options out there) and spare time. If the drive failed from too many bad sectors and you caught it early then yeah level 1 recovery is still possible but you may still experience some file structure corruption depending on how early you caught it. It becomes a game of luck depending on where the bad sectors exist and how many there are.

If your drive is experiencing mechanical failure, and it's bad enough, you can hear it very clearly if you put your ear near the drive while it's spinning. If you hear a grinding and/or clicking noise that's usually a pretty solid indicator the the drive is experiencing mechanical failure and a level 2 recovery will be necessary which usually requires a clean room and some very specialized knowledge and tools.

Also, I should mention, this only applies to mechanical hard disk drives, solid state memory is a completely different beast and data recovery is oftentimes impossible on these types of drives.

They definitely charge more than $100, data recovery is one of the most expensive services at Best Buy. Level 1 data recovery, depending on the staff there they may try and perform that in house but level 2 always needs to be shipped out to a clean room and will easily push $1,000+. Also, the reality of data recovery is unless the data being recovered is highly important, it's almost never worth it. During file recovery, file structure and naming gets destroyed so the results are hundreds of folders with nonsense names filled with hundreds of files with nonsense names and sometimes even missing an extension type, it's a total mess with no guarantee that the data you need was actually recovered.

The speeds have improved tremendously, over the last couple of years some significant improvements have been made. There's still more bandwidth overhead using I2P over a traditional connection but it has been significantly reduced and is not as noticeable anymore. That being said, there's still some configuration that's necessary to maximize your bandwidth. The biggest complaint I hear about the standard i2p install is that it uses extremely conservative bandwidth settings by default but it can all be easily adjusted to maximize performance on your router. I've used I2PD quite a bit but overall I actually much prefer standard Java I2P because it's far more feature rich, more frequently maintained, and settings are muuuuch much easier to configure and understand. There are still many brilliant optimizations in Java I2P that have not made it into I2PD such as the most recent peer analysis techniques that can automatically block/ban misbehaving peers among other things too. I personally think I2PD is best if I just need to host a low resource tunnel.... But back to the speed!

As was already mentioned the more people who participate, the more I2P thrives. One of the most notable differences is that most I2P nodes right now are just enthusiasts running on recycled hardware at a residential address whereas clear net torrents are much more mainstream and many common/popular torrents have at least one peer hosted at a data center with virtually unlimited bandwidth, that one peer usually contributes to over 50% of your download speed on a standard torrent.

I have my router bandwidth setting on my 24/7 router set pretty high and my router usually idles at about 850 KBps... My most recent peak was about 1.3MBps, very acceptable speeds I think. I get the best i2p torrent download speeds using Snark which is built into Java I2P, the only important setting to change is increase tunnel quantity to 10 to maximize your download bandwidth. I have seen some of my downloads seed at about 200+ KBps and I have downloaded at almost a full 1MBps which are comparable speeds to standard clear torrent downloads.

So, in a nutshell, it's not necessarily slower than a standard torrent download (well, maybe a little bit) but what it does have is significantly more variability in bandwidth and download speed depending on how many hops or peers are in between you and your target destination. More hops creates more variance (and more anonymity), you could be directly connected to someone in a data center but the next hop could be connected to a raspberry pi running off of public Wi-Fi which will be the bottleneck in that connection.

Absolutely. Go to https://geti2p.net/ to get started. There are some super simple Windows installers that make everything just a few clicks. If you're on Linux it's built into the package managers for Ubuntu/Debian but from my experience it's a lot better if you can get the Java source version working because then it can self update and you'll always have the most current release.

Once it's installed and running let your new i2p router run for a minimum of about 30-45 min to explore the network and build good connections with peers. The longer it runs the more stable it becomes but it should be usable after about 30 minutes on your first start up (subsequent start ups are a little faster after your router gets to know the network a little better). And that's it! You're now running an i2p router!

The only part where things get a little hard is with the proxy settings... Unfortunately there just aren't enough active devs or funding in i2p to support a dedicated browser like Tor so this is the only side of i2p that tends to get more involved. You need to configure a browser to proxy http requests through the port used for i2p http: 4444. If the i2p router is on the same machine as the browser then it's just a matter of entering your local address (127.0.0.1) and port (4444) into your proxy settings. If your i2p router is remote, you need to use ssh port forwarding on port 4444. Alternatively, there is a Firefox plugin that one of the core i2p devs (idk) maintains which automatically containerizes and proxies all .i2p addresses while leaving normal web traffic alone, it's called "I2P In Private Browsing". Only warning that the dev for that project cites is that the plugin, although open sourced, has not gone through any security auditing so there's no guarantee that no information gets leaked to the clear web - so basically just avoid this if maximum privacy is your goal.

After your router is started up and proxy settings are configured, you're good to go! Check out some starter sites like i2pforum.i2p to join in on i2p related discussions and development. notbob.i2p also offers a nice sortable directory of some sites hosted on i2p. Or.... Host your own hidden service(s)! The standard i2p install comes with a prepackaged and preconfigured Jetty web server, just start the service from your local tunnels page and you're now hosting a hidden website!

The possibilities are pretty much endless from here, anything that communicates on TCP/UDP can be tunneled through I2P. Which by the way is a huge advantage over Tor since Tor does not even support UDP. Unlike Tor, I2P also has a much better incentive for node operators since every user is a node, the more people who use I2P, the faster and better it becomes.... A Tor node only gets spun up when someone chooses to donate their resources to the network out of the grace of their heart. This also applies to P2P downloading. In fact... It helps to grab a popular download from an I2P indexer when starting a fresh router as that helps introduce your client to new peers. Torrenting is not even an option on Tor as it is basically DDOS'S the network of limited nodes..

qBittorrent I have not tried personally but I would think that if you have i2p set up on qbit already then enabling the setting "automatically add these trackers to new downloads" and add in a few open i2p trackers. Postman requires an account so unless the exact same torrent has already been posted there you won't be able to bridge.

For Prowlarr, it's a little more complicated. You can add Postman just like any other indexer but you then need to configure your proxy settings in Prowlarr for it to be reachable. If you are running your i2p router on the same machine you can just enter your local address (127.0.0.1) with port 4444 and it'll connect. If your router is on a remote machine the easiest solution is to then use ssh port forwarding (autossh is handy here). Ssh forward the remote 4444 port to local and then use the same address and port. The final step is setting your ignored addresses, I have a bit of a list but the idea is to filter out all non .i2p addresses so an example would look like: *.com, *.net, *.info, ......

EDIT: I should also add, if you are sticking with I2PD and are more concerned with just downloading and not incorporating the *arr suite there is a standalone Snark download that's floating around somewhere that can plug into I2PD. I haven't used the standalone personally but I do know that Snark is by far the most optimized client exclusively for i2p torrents. Snark is also baked into the standard i2p install by default.

That includes NVMe.... Just spent two weeks troubleshooting a constant random reboot on my newly built pc.... It ended up being the m.2 port on the motherboard that was faulty, not even the drive itself. I've been building computers personally and professionally for over 20 years and that was a first for me. Everyone I talked to and every support forum insisted RAM or power supply were the problem but nope! Not this time!

But the lesson here is, if you have a recurring problem that has no obvious cause... Test EVERYTHING. Start with the common stuff that fails and work your way down: Power Supply -> RAM -> CPU -> GPU -> HDDs -> SSDs -> USBs

Tips for RAM: It's usually best to first boot into a ram testing tool like memtest86 and just let that do its thing. That alone is usually all you need to know if you have a memory issue. Sometimes though, results may not make sense, I've seen situations where a new stick of RAM fails at almost every block and it turned out to be the slots on the motherboard that were faulty. In that case if results seem a little fishy you can remove all but one stick of RAM in the first slot, run another test, then move that stick of RAM down to the next slot. Repeat until all slots have been tested, you can also be extra thorough if needed and repeat the same test with the other sticks of RAM. That usually helps rule out if it's a motherboard issue or an issue on the stick of RAM.

CPU/GPU: usually any old stress test will make any hardware issues apparent with these two.

SSDs: these can be a little tricky to test especially if you are booting from them but in my case I found that completely removing the NVMe drive solved all my problems (well a mobo rma was the real fix). I couldn't even boot into a live Linux USB without crashing and rebooting when my NVMe was plugged in. One not so obvious clue that the SSD was acting up was that event logs related to the crash were never written to the drive... Because I/O was outright failing.

USBs: yes, USBs are on that list. One of my first significant computer issues that I had ever encountered occurred from a faulty USB hub that stopped my PC from even booting up. I took it to two different repair shops they all told me nothing was wrong with my computer, but every time I brought it back home and plugged everything back in... I couldn't boot. It was a lucky chance that I figured out it was the USB hub, that was not a fun one.

Now I didn't even add motherboards to the list because quite frankly I'm not sure how they rank but they are the absolute worst piece of hardware to troubleshoot but luckily it's usually pretty rare that they fail. There are so many connections and settings built into motherboards that it quickly gets overwhelming trying to troubleshoot anything related to it. From my experience, if you have individually tested every bit of hardware and everything passes its test, most often it's the motherboard that's failing, especially if you have already ruled out software/firmware issues for sure. Motherboard issues aren't always obvious and can often fail in very bizarre ways.

And as a final bit of advice I'd like to throw out there from my years of experience in PC building.... NEVER CHEAP OUT ON A POWER SUPPLY. It affects every single component in your PC and when they fail it can get ugly. I bought a super cheap off-brand power supply one time and pushed that thing to the absolute limits and when it failed it took down more than half of my PC with it, fried my motherboard, CPU, and RAM. Additionally, the risk of fire is not zero when these things fail. Always use ONLY the cables provided for that power supply and nothing else. Those cables are rated specifically for the wattage that can be supplied by that power supply. Also, it's good to get a power supply that's roughly 100+ watts more than what your PC needs. This helps in maximizing the efficiency of the power supply as well as increasing longevity due to less thermal wear.

I2P has its own DHT so all you need is an InfoHash to start downloading assuming there's at least one reachable seeder. MuWire is an application that lets you search the DHT. The developer recently abandoned the project though... I haven't tried it in some time but it probably still works.