[–] 4 points 2 months ago (1 child)

Thats how it works in theory, but in practice it comes down to trust more than anything else.

Its more effort to read and validate your list than it is to just go and download the installer directly. So you need people to trust you.

  • source
  • parent
  • context
  • [–] [S] 0 points 2 months ago (2 children)

    It's open source. Anyone can audit it. You can create your own sources.list, but if you distribute it, you must open the code. Also, "wid info <package_name>" shows the exact URL it downloads from. Example: wid info llvm shows the official GitHub release link.

  • source
  • parent
  • context
  • [–] 9 points 2 months ago (5 children)

    Better is a wild claim.

    You're right, gists do seem to update with the static url, however that isnt necessarily better, it now means your gist is effectively under your control, and you can replace the installers with malware packed ones. Operating a software repository/installer requires that people trust you, and that is basically impossible for a no-name dev with no history.

    You ideally should be doing checksum checks as well.

  • source
  • parent
  • context
  • [–] 5 points 2 months ago (16 children)

    Some feedback:

    let remote_url = "https://gist.githubusercontent.com/ZeSystem-Inc/20ddc1ac41d73c6033cee3b4a5ab1a85/raw";
    

    You have effectively hardcoded the list of software you support, ideally you should be able to dynamically update the list, otherwise you have no way to revoke or update versions if required. And if its hardcoded, why bother network requesting for it, just build it into the binary. Would be a little larger binary, but even faster.

    No dependency resolution – eliminates fragility.

    Meaningless, there is no dependency resolution because thats done for you by the installers.

    Written in Rust – memory-safe, zero-cost, ultra-fast.

    The task you are doing is entirely IO bound, rusts performance is irrelevant.

  • source
  • [–] 10 points 2 months ago (2 children)

    Come on, dude. You deleted the original post you made about this in /c/rust because you got so many people calling you out specifically for this, and you are recreating the post here in an attempt to whitewash and misdirect. Stop it.

    Seriously, that sort of shit should be a ban-able offense.

  • source
  • parent
  • context
  • [–] 9 points 2 months ago* (last edited 2 months ago) (5 children)

    Look at OP's history. It's an LLM that in some other post got entangled into writing limerics for commenters. I started looking for an publicly available iocaine instance but couldn't find any. So who knows, maybe sending that LLM after San might poison it just a little bit? Even if it would only be in the comment, that would still be a small win

    I get where you're coming from. But my comment is not a jab at San

  • source
  • parent
  • context
  • view more: ‹ prev next ›