Alternatively, give users a notification that this will work faster with IPFS enabled.

Opening a URL with a search query in it will enter the query in the search bar but will not execute the search.

Example:
https://ipfs.io/ipfs/Qmf8pSQazshENpn8opE395z5bBWUoD43Gv1mQCASeSdqhW/#/search?search=canary

Should immediately show the results for 'canary'.

When i open this page it infinity loading more and more same results

https://ipfs-search.com/#/search?page=21&search=%22%D0%A5%D0%B0%D0%B1%D1%80%22

The API has been extended (a while ago) allowing us to discover the file type without fetching the type or relying on the information from the search. Discovering the file type makes the previews work more often and would make the overview nicer.

The filetype is currently supplied to the hint card. We can remove it, calculate it where needed, cleaning up the code in one go.

As described here: https://github.com/ipfs/go-ipfs/blob/master/docs/gateway.md#filenames

All direct URLs should have an extra parameter filename with the file name in order to let the browser find the file type and display the content correctly

Example:
https://ipfs.io/ipfs/<hash>?filename=<filename>.<extension>
Or even with extension only
https://ipfs.io/ipfs/<hash>?filename=.<extension>

This seems easy to implement because we always have the filename or the mime type provided by the metadata

On the main page: http://ipfs-search.com/ there are API, Code and Contact hyperlinks. I propose that you add and "Help" one. The suggested content can be the following:

1. What is this engine about
2. What kind of search language is supported
3. What is the format of the results
4. Examples

Best regards.

When i search for file in ipfs-search i see that it have long path in the name.
Example:
\distributed_lab\Новичок\extra\habr\SPHINCS — Википедия_files\444px-Binary_hash_tree.png

I want to browse folder that contain that file but have only file hash. Can you additional show directory hash in file properties? It can be hash of root directory (\) and directory that contains that file (SPHINCS — Википедия_files).

There should be either 1 or First and it is not clear why '...' is there (it is not clickable - perhaps it should be?).

The current build instructions result in a failing build (#2), which makes it impossible to update the production version and it inhibits outside contribution.

Please, provide updated build instructions (Docker-based or otherwise) or any other means of reliably creating production and development builds.

As it returns folders as well.

@vandrongelen @dokterbob An issue for keeping up with drafting the next release as mentioned in #36. Helps us keep it separate from specific issues. Feel free to comment or add to this issue ^_^

• Merge changes of #36
• Approve or clean #7 #32
• Ship it!

When no references in result.

Example: https://ipfs-search.com/#/search?kind=audio&search=beck
API query: https://api.ipfs-search.com/v1/search?q=beck%20metadata.Content-Type%3A(audio*)&type=file&page=0

Indicate when JSON is loading.

In the list view, it is not evident to users that rows can be clicked on, it seems that only the hashes can be clicked - resulting in users clicking on hashes and often missing out on our very handsome preview functionality.

As they load slow, users aren't aware they're waiting for something

When on the landing page and selecting a 'kind', without typing a query, it triggers a search - which it shouldn't.

Is it possible ?

As in the current go-ipfs implementation, the current search engine reports the byte sizes of the objects. While this is good in some cases, it is not convenient to be read by humans at all. Hence, my proposal is to introduce more friendly like formatting. For example the effect should be as the common POSIX switch -h is used as in ls -lh, du -h.

Depending on the choice 1000 base or 1024 can be used. IMO stick to https://en.wikipedia.org/wiki/Orders_of_magnitude_(data) conventions.

if less than 1000 bytes →XYZ B
if less than 1000^3 bytes →XYZ KB (if X KB →X.Y KB)
if less than 1000^6 bytes →XYZ MB (if X MB →X.Y MB)
....

Best regards.

Currently, clicking to pages > 0 are not working well. If I then reload the browser, it kind of seems to work again.

Related: #8?

The title of the page should be IPFS Search or ipfs-search.com.

Ideally/eventually it would be: <query> · ipfs-search.com and ipfs-search.com when there's no query.

The website currently includes a whopping 900 KB JS file. Could we reduce this to something reasonable, like 150-300 KB?

1. Preview images width bigger than container width.
2. Can't see current page
3. Can't see what last previwed link

Need to set style rule for img:

img{
    max-width: 100%;
}

Before

After

Need to show current page

.page-link.current-page {
    background-color: lightgray;
}

Before

After

Show last previwed result

.selected{
    background-color: lightgray;
}

Before

After

At least having a link to formatted metadata would be nice, or having some or all fields available there would be really cool.

See: https://api.ipfs-search.com/#metadata

Example: https://ipfs-search.com/#/search?kind=file&page=8&search=test
Url open page with no search results. But "test" will be in search field. When i hit Enter in search field results will be shown but from first page.

Might be a good idea to have these to make IPFS on par with most search engines.
Also would be good to have a separate search page to tailor to these file types.

Set up a reproducible build for an NGINX server that hosts the ember app. The common structure of https://github.com/mu-semtech/ember-proxy-service can be followed.

When try to preview some video files clowdflare-ipfs return 403 error with this message:

ipfs: video streaming is not allowed

Need to add alternative sources for video by using source tag.

<video controls preload="metadata">
 <source src="https://clowdflare-ipfs.com/ipfs/...">
 <source src="https://gateway.ipfs.io/ipfs/..." > 
</video>

If CF return 403 than video switch to gateway.ipfs.io.

E.g. bytes, kilobytes, etc.

The 'Show metadata' button should explicitly be clickable and not selectable so it behaves as expected. Because it looks like a button, we should probably convert it into a button tag. If that would make it hard on the styling, we could revert to CSS in order to make it behave as we'd want it to.

NPM has a package-lock.json to indicate specific dependencies which tends to be rather large. Assuming dependencies use semantic versioning themselves, the lockfile provides little value.

There is value to be gotten from this lockfile when dependencies change incorrectly. The value of this safety-net may be negated by the change of file format across NPM versions. We have disabled the use of this lockfile globally and across all of our projects for now.

Should we disable the package-lock.json explicitly for this repository so people that clone it don't encounter the file and accidentally end up with a bunch of changes?

Having installed the app according to the instructions and then running ember serve or ember build results in a site where typing in the search bar or clicking on the filter does not yield characters typed or the filter control opening and gives the following JS error:

Uncaught TypeError: Cannot set property placement of [object Object] which has only a getter
    at defineProperty (ember-metal.js:886)
    at EmberPopper.CoreObject (core_object.js:129)
    at EmberPopper.EmberObject (object.js:28)
    at EmberPopper.FrameworkObject (object.js:72)
    at EmberPopper.Class (core_object.js:207)
    at EmberPopper.Class (core_object.js:207)
    at new Class (core_object.js:207)
    at new EmberPopperBase (ember-popper-base.js:60)
    at new EmberPopper (ember-popper.js:8)
    at Function.create (core_object.js:220)

It seems that on page load, I'm also getting the following error:

jquery.js:3818 jQuery.Deferred exception: Cannot set property placement of [object Object] which has only a getter TypeError: Cannot set property placement of [object Object] which has only a getter
    at defineProperty (http://localhost:4200/assets/vendor.js:44215:30)
    at EmberPopper.CoreObject (http://localhost:4200/assets/vendor.js:55473:46)
    at EmberPopper.EmberObject (http://localhost:4200/assets/vendor.js:55872:75)
    at EmberPopper.FrameworkObject (http://localhost:4200/assets/vendor.js:55916:78)
    at EmberPopper.Class (http://localhost:4200/assets/vendor.js:55551:72)
    at EmberPopper.Class (http://localhost:4200/assets/vendor.js:55551:72)
    at new Class (http://localhost:4200/assets/vendor.js:55551:72)
    at new EmberPopperBase (http://localhost:4200/assets/vendor.js:89894:22)
    at new EmberPopper (http://localhost:4200/assets/vendor.js:90245:21)
    at Function.create (http://localhost:4200/assets/vendor.js:55564:16) undefined

Tested in Chrome, running NodeJS 10.13.0, ember-cli 3.5.1

Pretty soon, we could introduce filters for:

• first_seen
• last_seen
• duration (audio/video)
• megapixels (images)
• file_size

What might this look like and/or function?

This is (due to underlying issues in IPFS) always 0.

https://ipfs-search.com/#/search?kind=directory&search=test doesn't actually filter by directory.

Example output should be: https://api.ipfs-search.com/v1/search?q=test%20_type:directory

Notify the user when backend is down.