Search Results for "repository"

...Because the links relate to torrent access, users must evaluate legality, safety, and copyright compliance in their own location before using any listed resource. From a software perspective, the repository is best described as a curated, static web directory.

1337x Proxy List is an open-source repository that curates a collection of proxy and mirror sites designed to provide access to the 1337x torrent platform when it is blocked or restricted in certain regions. The project aggregates and maintains a list of working proxy URLs that allow users to bypass ISP or government restrictions by routing traffic through alternative domains.

...Its value is mainly in aggregation, because it brings many mirror options into one easy-to-scan page. The repository is lightweight and mostly useful as a static publishing project. It may also be studied as an example of a simple GitHub-hosted link directory with minimal technical complexity.

Proxifly Free Proxy List by Proxifly is a public repository that provides automatically refreshed lists of working proxies. It collects HTTP, HTTPS, SOCKS4, and SOCKS5 proxies from around the web and validates them on a frequent schedule. The repository separates proxy data by protocol and provides the lists in multiple file formats. Its main value is freshness, since the list is updated every few minutes and removes duplicates.

Jackett works as a proxy server, it translates queries from apps (Sonarr, Radarr, SickRage, CouchPotato, Mylar3, Lidarr, DuckieTV, qBittorrent, Nefarious, etc.) into tracker-site-specific HTTP queries, parses the HTML or JSON response, and then sends results back to the requesting software. This allows for getting recent uploads (like RSS) and performing searches. Jackett is a single repository of maintained indexer scraping & translation logic, removing the burden from other apps. Trackers marked with (invite needed) have no active maintainer and may be missing features or be broken. If your client supports multiple feeds it's recommended to add each indexer directly instead of using all indexers. Using the all indexer has no advantages (besides reduced management overhead). ...

...It supports hypermedia APIs but also any "legacy" API by documenting its relations using OpenAPI. The protocol has been published as an Internet-Draft that is maintained in this repository. A reference, production-grade, implementation gateway server is also available in this repository. It's free software (AGPL) written in Go. A Docker image is provided. Current solutions for these problems (GraphQL, JSON:API's embedded resources and sparse fieldsets, etc.) are smart network hacks for HTTP/1. But these hacks come with (too) many drawbacks when it comes to HTTP cache, logs and even security. ...

...By leveraging Rust, this implementation emphasizes memory safety, concurrency, and efficiency, making it suitable for both client and server use on devices ranging from small embedded systems to large servers. The repository includes multiple binaries such as sslocal for local SOCKS5 proxy clients and ssserver for remote proxy servers, giving developers flexible components to build customized proxy setups. It also supports modern asynchronous networking patterns, optional DNS handling, transparent proxy modes, tunneling, and advanced cipher methods.

...The C# .Net Application is the Core Proxy Server, and it uses the Driver to run a Virtual Disk Drive through it. Almost all necessary code is completed, so you can download and run it. All the code including the kernel driver is included in this repository. Please note that the work is in progress. Necessary code has been completed. There might be bugs, so you may inform them to me or fix them yourself. 1. turn on the windows test signed drivers mode. then reboot is required. 2. run the script install.cmd 3. run the script start.cmd 4. then FilediskProxyNet.exe. 5. only administrator account.

...The project created the SHIWA Simulation Platform which enables users to create and run embedded workflows which incorporate workflows of different workflow systems. The platform consists of the SHIWA Science Gateway and the SHIWA VO. The SHIWA Science Gateway contains the SHIWA portal, the SHIWA Workflow Repository, the SHIWA Proxy Server, the GEMLCA Service and the GEMLCA Repository. To find out more about the SHIWA Simulation Platform, and learn about how to get access to execute the workflows deployed in the repository, please go to the SHIWA project page: http://shiwa-workflow.eu. The SHIWA Workflow Repository manages workflow descriptions, and implementations and configurations of workflows.