• 0 Posts
  • 15 Comments
Joined 2 years ago
cake
Cake day: August 16th, 2023

help-circle



  • Related, Pirate Bay used to (might still?) have a section where they mock all of the threatening letters that cite a different jurisdiction. Usually the US DMCA, but also similar laws from other countries.

    They never posted any letters that cited Swedish (IIRC) law, because those were valid threats.



  • The Tesla connector was NOT openly available until late 2022, and wasn’t a fully published standard until 2024. They originally wanted a hefty licensing concession from other vendors. Specifically, they would only license it if they joined a patent pool.

    In fact, the current NACS connector isn’t even electrically the same as the one Tesla used in 2021. Superchargers are backwards compatible, but they have to support multiple standards. It also means that older Teslas can’t use the growing network of NACS chargers without an upgrade.


  • 2 options- USB-C wired NICs are cheap and readily available, so you could easily use a wired connection.

    But I think what you want to do is setup a WAP. You can do this with (nearly) any standard wireless router that meets your specs.

    First, do not connect this to any part of your network yet. Instead, connect to and access its setup config. I know apps are trendy, but I have no idea if you can do this from there. You can if you use its internal website instead, often 192.168.1.1.

    Once here, you need to do the following:

    1. Give it a new IP in the same subnet as your existing router/network. If your main router is 192.168.1.1 and subnet mask 255.255.255.0, your new WAP can be 192.168.1.2. Make sure that your main DHCP range also does not include this address.

    2. Disable the DHCP server entirely on your WAP. You don’t want them to interfere with each other.

    3. Configure the wireless to have the exact same settings as your main router. Your clients (phones, laptops, etc) will automatically choose the best connection point based on signal and noise.

    4. Once configured, connect it to your existing network using a LOCAL port. Do not use the WAN/Internet port.

    If needed, you can also connect other devices to the other local ports.


  • I agree with you about respectful dissent. I have found that Lemmy, far moreso than other platforms, is afraid of hearing anything that challenges their beliefs and assumptions.

    That said, their statement didn’t even cover that. I would describe the need to be comments that are made in good faith, to better drive the conversation/understanding in a community.

    Flat earthers rarely post in good faith. They are overwhelmingly trolls attempting to derail a conversation.

    But someone that posts to a vegan community about a new study about the health effects of eating meat is sometimes acting in good faith. Articles like this can drive genuine conversation. It all depends on context.

    Same for politics. Look at how badly posts were down voted for showing (valid) polls with Trump winning.

    Hell, look at the various technology communities. If you don’t have the approach of “Windows bad! Linux good!”, you will be down voted or moderated.

    Even in communities/topics loaded with trolls (climate change, LGBT, anything politics), there’s still room for dissent in good faith.





  • Thank you for the extra context. It’s relieving to know you don’t just have a bunch of USB “backup” drives connected.

    To break this down to its simplest elements, you basically have a bunch of small DASes connected to a USB host controller. The rest could be achieved using another interface, such as SATA, SAS, or others. USB has certain compromises that you really don’t want happening to a member of a RAID, which is why you’re getting warnings from people about data loss. SATA/SAS don’t have this issue.

    You should not have to replace the cable ever, especially if it does not move. Combined with the counterfeit card, it sounds like you had a bad parts supplier. But yes, parts can sometimes fail, and replacements on SAS are inconvenient. You also (probably) have to find a way to cool the card, which might be an ugly solution.

    I eventually went with a proper server DAS (EMC ktn-stl3, IIRC), connected via external SAS cable. It works like a charm, although it is extremely loud and sucks down 250w @ idle. I don’t blame anyone for refusing this as a solution.

    I wrote, rewrote, and eventually deleted large sections of this response as I thought through it. It really seems like your main reason for going USB is that specific enclosure. There should really be an equivalent with SAS/SATA connectors, but I can’t find one. DAS enclosures pretty much suck, and cooling is a big part of it.

    So, when it all comes down to it, you would need a DAS with good, quiet airflow, and SATA connectors. Presumably this enclosure would also need to be self-powered. It would need either 4 bays to match what you have, or 16 to cover everything you would need. This is a simple idea, and all of the pieces already exist in other products.

    But I’ve never seen it all combined. It seems the data hoarder community jumps from internal bays (I’ve seen up to 15 in a reasonable consumer config) straight to rackmount server gear.

    Your setup isn’t terrible, but it isn’t what it could/should be. All things being equal, you really should switch the drives over to SATA/SAS. But that depends on finding a good DAS first. If you ever find one, I’d be thrilled to switch to it as well.



  • Nollij@sopuli.xyztoPiracy@lemmy.mlAI for torrenting?
    link
    fedilink
    English
    arrow-up
    2
    ·
    4 months ago

    You are comparing it to a hash, following some extra rules on what the data could be. You have exactly the length of hash before you can reliably count on duplicates (and collisions happen much sooner). In torrent v1, this is SHA-1, which has a 160-bit (or 20 byte) hash. Which means for every single additional random bit, you have doubled the number of possible matches.

    If your torrent has an uncommonly small chunk size of 256KiB, that’s 261,144 bytes. Minus the 20 from above, and you have a likely 256^261124 chunks that match your hash. That’s a number so large that Google calls it infinity. It would take you forever just to generate these chunks by brute force, since each would need to be created, then hashed, then the results stored somewhere. Many years ago, I remember someone doing this on CRC32 (32 bits/4 bytes) and 6 byte files. It took all night, and produced dozens of hash-matching files. You’re talking many orders of magnitude bigger.

    But then what? You’d still need to apply the other rules on what the data could be. Rules that are probably more CPU-intensive than the hash algorithm.

    The one trick that AI might be able to use to save the day is that it may contain in its corpus the original file. In effect, that would make the AI an unlikely seeder.