Enter the query into the form above.
API method:
GET /api/symbols?search=hello&page=1&limit=20
where search is your query, page is a page number and limit is a number of items on a single page. Pagination information (such as a number of pages and etc) is returned
in response headers.
If you'd like to join our channel search send a patch to ~whereiseveryone/toys@lists.sr.ht adding your channel as an entry in channels.scm.
Return two values: the hash algorithm used by NARINFO and its value as a bytevector.
Write NARINFO to PORT.
Return #t if NARINFO's signature is valid and made by one of the keys in ACL.
Return the narinfo represented by STR or #f if it is not syntactically valid. Assume CACHE-URI as the base URI of the cache STR originates form.
Return the external representation of NARINFO.
Select the "best" URI to download NARINFO's nar, and return three values: the URI, its compression method (a string), and the compressed file size.
When FAST-DECOMPRESSION? is true, prefer substitutes with faster decompression (typically zstd) rather than substitutes with a higher compression ratio (typically lzip).
Return true if NARINFO1 and NARINFO2 are equivalent--i.e., if they describe the same store item. This ignores unnecessary metadata such as the Nar URL.
If the string HASH denotes a sha256 hash, return it as a bytevector. Otherwise return #f.
Return the value of a narinfo's 'Signature' field as a canonical sexp.
Return the sorted list of "preferred" nar URIs from NARINFO (preferred comes first) where each entry is a tuple containing: the URI, its compression method (a string), and the compressed file size.
When FAST-DECOMPRESSION? is true, prefer substitutes with faster decompression (typically zstd) rather than substitutes with a higher compression ratio (typically lzip).
Read a narinfo from PORT. If URL is true, it must be a string used to build full URIs from relative URIs found while reading PORT. When SIZE is true, read at most SIZE bytes from PORT; otherwise, read as much as possible. Return #f if the narinfo that was read is not syntactically valid, for instance if it contains invalid store file names.
No authentication and authorization checks are performed here!