guix VS Transmission

> So what we are missing now is a 500GB framework that can write the config file for the programming language that is writing a config file for the actual program I wish to use.

That exists since 1960. It's called LISP. The e.g. https://guix.gnu.org/ uses with great success, the Guile Scheme dialect of LISP, to be precise. And FYI the "framework" is:

  $ ls --human-readable --size $(readlink $(which guile))

> inventing a brand new purely functional language programming language.

ISTM that if you dislike that, then there's GUIX.

https://guix.gnu.org/

Very briefly, AFAICT, it's "Nix but using Scheme".

And just wait till you discover Arch Linux, Gentoo, Guix, or NixOS.

https://guix.gnu.org for example. It did load before an update but it doesn't anymore.

Is it? Seems to me it's used for some pretty cool stuff, heard of Guix?

I think a "competitor" to Lua would be Guile [1], but I am not sure if it gets close to Lua in terms of lightweightness... it was designed to be used in the GNU project, with similar objects as Lua: to be light, easily embeddable. It's a Scheme (Lisp) so maybe not for everyone's taste... its "coolest" use i know of is for configuring Guix [2] (the GNU version of Nix).

[1] https://www.gnu.org/software/guile/

[2] https://guix.gnu.org

No one said Guix yet, might be worth a look: https://guix.gnu.org/

GNU Guix! A fully functional package manager and distro heavily inspire by Nix. The primary difference between it and Nix being that it is almost entirely written and configured in GNU Guile, an implementation of Scheme (Lisp) and the official extension language of the GNU Project (originally intended to be for GNU what emacs lisp is for emacs).

You should perhaps utilize guix for your projects. It provides rather acceptable rust resp. crates support and in a perfectly reproducible build environment. But be aware, that it even tries to build even the rust compiler from source by going through all this nasty steps of its iterative bootstrap process. This can be a little bit complex and time-consuming, if you need an up-to-date version of rustc.

Why bake libtransmission into the app instead of just using the transmission daemon's RPC?

What you've done actually makes it harder to use, because in order to configure any of transmission's settings (ports, connection/torrent connection limits, bandwith limits, etc) the user needs to dig around to find the transmission config folder and then manually edit JSON with a text editor - because your client doesn't expose any of transmissions numerous settings [1] to the user except for choosing the download folder.

I'm not sure why anyone would want to use this instead of Flood [2] or even old Transmission Web Control [3]

1: https://github.com/transmission/transmission/blob/main/docs/...

1: https://github.com/jesec/flood

2: https://github.com/ronggang/transmission-web-control

Grab this file. Install Transmission on Mac or Deluge on Win. Optional: run a VPN if you're in the US(mostly) and worried about your ISP sending you a cease-and-desist notice. Open the file using the app you installed. Wait. It should start within a minute or two and download progress will be seen. Speed depends on how many people are sharing it. Any issues, let me know.

Why "NO TORRENT"? Just get TransmissionBT and torrent whatever you want

Its intresting you mention that, before reading your reply I went and created a post in the Q n A section, asking for help about this very thing and I linked to the same GitHub issue you linked to here. I have yet to get a reply lol.here

transmission can run as a headless server with a web gui

Get a VPN like Windscribe(set windscribe firewall to on instead of auto), forward your port via their website. Use a good torrent client like https://transmissionbt.com/ set that port in the options, and add a blocklist https://github.com/Naunter/BT\_BlockLists/raw/master/bt\_blocklists.gz