Leo Gaskin

> (I was on holiday and missed the notification, apologies) No worries, thanks for responding. > To clarify, you would hit the same problem when doing it by hand (without...

In that case, yes I would suspect that any application that uses the API in this manner would hit the rate limit in the same way niv does. There however...

@nmattia Would this switch also replace the code `niv` currently uses to check if a github repo has been updated? The last time I tried to use `fetchFromGitHub` as a...

I'm assuming you want to reimplement the `update` functionality using the `fetchFromGitHub` fetcher, because otherwise `niv` itself would still have to make calls to the GitHub API itself, which means...

To me, the original proposal sounds very reasonable, but I do have some theoretical concerns. I realize that these might not be actual flaws in the design, but I'd still...

> Mh, actually this would also trivially solve #102, since we'd be passing the path to sources.json explicitly. @masaeedu you seem to have an agenda here... wink So essentially the...

@masaeedu As @nmattia has already mentioned, his proposed approach to import everything into files that are edited by the user (e.g. `default.nix`) would make updating automatically very janky. As for...

> If you debug/tweak your sources.nix file, how do you usually update it? Wouldn't updating destroy your changes? @masaeedu Generally my changes to the `sources.nix` file are only experimental, so...

@HalosGhost I definitely see the advantage in using a well-established protocol. However, IMO this is somewhat of a special case: * Sixel in its "original form" was not at all...

@jmriego I think the ideal course of action to prevent the sort of thing you are talking about would be asking if any of the existing projects would be willing...