That’s fine and easy on desktop/web browser, but for mobile devices it is not quite as easy. You would either need to use a hacked version of the app or a third party app.

Most users likely do not know about recall, and as the guy in the video shows, there doesn’t appear to be anything in a normal user interface showing that it is installed and configurable.

If you don’t want to risk getting a ban at all, the only safe thing is to not connect to the internet at all. Maybe there is some level of safety, but it could take only one mistake.

If we assume that we fully understand how nintendo catches this, we would still only ubderstand at that point in time. They could still change or push updates which could cause you a problem.

I would return it, but if you are curious you can try some of the following to get experiencing identifying bad disks.

You could try a different computer or controller to be sure.

If you can get some writes/reads to work, you can use badblocks or dm-crypt: https://wiki.archlinux.org/title/Badblocks#Alternatives

Badblocks will write known data to disk then read it to verify its good. If the disk is malicious, this can be faked. badblocks is also a little slow.

Using dm-crypt in the wiki will write zeros through dm-crypt which will result in random noise being written to disk, then compare with zeros to verify reads are good. This can not be faked easily since the zero stream is encrypted as it is written to disk.

The last I looked into it, the best way to do it was to get an older kindle so you could download the older DRM copies of books from amazon. But I think some newer books are using only the newer DRM which I don’t think has been cracked.

It has probably been at least a year since I checked. If you do end up finding an updated method, I would be interested.

Don’t buy into tape. It is costly and is inferior to hard drives by most metrics for smaller scale operations. You can easily get 8TB hard drives for less than $20/TB. While tape is cheaper than that, the drive to actually use it is expensive, plus you get all the disadvantages of the tape itself.

Fun fact: you can probably buy a whole server, external sas card and disk shelf for less than the cost of a somewhat modern tape drive.

If you are wanting to store less than 100TB of data, it would probably be cheaper to use drives, then in 3-5 years buy another set of disks and still be ahead compared to tape.

Note that v1 and v2 torrents use slightly different url fragments, so this won’t work quite as easily as you think. It would be possible tell the difference because they use different hashes with different lengths, but most people probably won’t know.

There are definitely differences, but usually they don’t matter from a simple address and routing perspective.

For example, there is no ARP in IPv6. Instead another protocol is used called Neighbor Discovery Protocol, which actually is done through ICMPv6. Therefore, if you blindly block all ICMPv6, your network may break.

Once you have a grasp on v6, it is much better than v4 because even the smallest common v6 network size of /64 is many times larger than all the addresses in v4. Every device can have it’s own global ip, so you no longer need nat at all. Everything can easily connect, assuming there is no firewall blocking it.

It can and will work, but it will not be optimal. You will be able to connect to other peers, but other peers will not be able to connect to you. This usually isn’t a big deal, but it’s not great in situations where there are not many peers, and you need every connection you can get.

DNS vc is used for any dns request, not just zone transfers. UDP can sometimes fail in some situations, in which case the client will fall back to TCP which will keep it working.

No, you should keep both udp and tcp port 53 open going out. blocking dns vc/tcp will result in dns being partially broken.

Why would you strip ipv6 if mullvad supports it. The reason people disable or block v6 are for 2 reasons, ignorance, and/or the vpn providor doesn’t support ipv6. V4 and v6 can and usually do run at the same time (this is called dual stack), so if the vpn only touches the v4 side of things, v4 will be tunneled while v6 will be unaffected.

Also, the firewall doesn’t matter if you use a torrent client that can just bind to the wg interface (assuming there is no nat being performed from the wg interface to the physical interface). The client will take one or all of the ips on the interface, which will make it impossible to leak IP directly assuming your switch or router doesn’t also have an ip in the same subnet as your wg interface ip.

I don’t know UFW, but if you run iptables-save or nft list ruleset i can take a look to see if it is sane.

But what i can tell is that it might work. You appear to be only allowing public traffic to wg. It should be noted that this setup will likely fail at some point because you are hard coding the IP. It should fail safe, but the public internet will not work.

Tbh, I don’t think encryption matters that much for are usually public chat channels.

The private communication should be safe since i think the users will usually pin the keys for each other.

As long as your ISP is handing out a block of IPs, you don’t need NAT for v6.

If you want to, then sure. For torrenting, it’s not necessary, but may be helpful. I do occasionally see ipv6 peers.

Many ISPs are no longer handing out even 1 public ipv4 address per account, and instead opting for CGnat which further breaks and stratifies the internet.

Tmobile for example is 464xlat which is even worse than cgnat since it requires tampering with dns responses.

Given the situation many ISP are in, most serious companies offering services on the internet have supported ipv6 for a long time now in order to offer the most competitive service possible. And with cloudflare now serving up a large amount of traffic, a lot of all traffic is v6.

Believe it or not, but IPv6 is here and gaining ground.

BitTorrent v2 allows this also. In v1, torrents with multiple files are hashed continuously (cat) together without respect to file boundaries. A side effect of this that many people notice is that to grab a specific file may require downloading some of the files before or after the one you want.

Under v2, each file is hashed separately, so this fixes the aforementioned problem and should allow sharing of files across torrent files.

Wouldn’t advise turning off ipv6. We are probably getting near the point where some public services will disable or offer v4 as only best effort, and when this happens, your connectivity will be broken for certain things if you disable v6. Heck, it’s to the point now where all my home hosted services are v6 only.

The better solution is to just get a VPN that supports ipv6 like airvpn or mullvad. I think pia disables ipv6 while the tunnel is up, which is better than disabling ipv6 altogether.

To validate the tunnel is working properly you can use something like this.

https://ipleak.net/

There is also a Torrent Address detection section, that when you activate it, will provide a magnet link that will show your ip to ensure that it is tunneled properly.

You can use this: https://ipfs.io/ipfs/QmbpRxBZ5HDZDVRoeAU8xFYnoP4r5eGCxdkmfFW3JbA6mq/

That is a low tech html page that can search the SQLite database someone posted. That page is hosted on IPFS, which you can access through one of the gateways, although I posted a link to the page via one of the gateways.

On that page is a button you can press for more information on how to download it to your local computer to have a speedy local copy.

How I have been using it is: search in the following format: [name] [release year] [quality like 1080p] [encode like x265]

do note that the database is not being updated since RARBG is obviously gone now, but stuff prior and including some of 2023 is all there, most what rarbg released.