• 0 Posts
  • 9 Comments
Joined 2 years ago
Cake day: July 5th, 2023

  • Heres a python script I made up from just modifying another script I use, it depends on qbittorrent-api, but to use just fill out the connection info and add all the trackers you want to remove in the TRACKERS array, I’ve included 2 rarbg trackers just as an example.

    #!/usr/bin/env python3
    import qbittorrentapi
    import sys
    
    TRACKERS = [
            "udp://9.rarbg.to:2770/announce",
            "udp://9.rarbg.me:2730/announce"
     ]
    
    conn_info = dict(
        host     = "qbittorrent.localhost",
        port     = 80,
        username = "admin",
        password = "PASSWORD"
    )
    
    def main (argv, argc):
        qbt_client = qbittorrentapi.Client(**conn_info)
    
        try:
            qbt_client.auth_log_in()
        except qbittorrentapi.LoginFailed as e:
            print(e)
            return 1
    
        for torrent in qbt_client.torrents_info():
            #urls = []
            #for tracker in torrent.trackers:
                #print(tracker)
                #urls.append(tracker.url)
            
            torrent.remove_trackers(urls=TRACKERS)
    
            #torrent.add_trackers(urls=TRACKERS)
    
        qbt_client.auth_log_out()
        return 0
    
    if __name__ == "__main__":
        sys.exit(main(sys.argv, len(sys.argv)))
    


  • Ive been torrenting on I2P with qBittorrent for a lil while now, its not as fast as the clearnet, the fastest speed down ive ever got so far is 1.7MB/s, and this was on a torrent with loads of seeders. Its possible to increase your tunnel quantity and lower the amount of hops each tunnel has for better performance, but you will have less anonymity with less tunnel length.

    But so far its been nice, there is no need to think about NAT/Firewall, as all peers can communicate with each other, but it doesnt have as much content as the clearnet, so I try to cross-seed what I can. But when im torrenting, I try to go I2P-first, and then fallback on the clearnet if I couldnt find what I was looking for.






  • WARNING: doing this will absolutely DESTROY YOUR SYSTEM, PERMANENTLY!!!

    But if you wish to continue, you can erase all the EFI variables using the rm utility, I dont think you will be able to completely zero out the chip on the system from inside of Linux as its read-only.

    But to delete all the EFI variables, cd into /sys/firmware/efi/efivars, if this directory is not availiable, either the efivarfs is not mounted, or you are booted in legacy BIOS mode. But once you are in this directory, run chattr -i ./* as root or sudo to remove the immutable bit on all the files, then run rm ./* as root. This WILL break your system. Only do this if you know how to restore your system using like a chip programmer.


  • This happened to me too. I had to grab the box that comes up and resize it like I would with a normal window, mine glitched a lot when I tried it, try resizing it as far as you can, it will try and glitch back, but just keep fighting it until it becomes a usable size, then log out of Plasma and log back in, and then you can size it back down to a normal size. Hopefully there will be an official fix for this soon