Feature request: Add ipfs-search.com functionality into ipfs-webui

Abierto
#2,060 5 comentarios 4 reacciones 1 asignado Ver en GitHub

@0xDanomite ya está trabajando en esto.

Desde el 1/11/2022.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

effort/days exp/beginner good first issue kind/enhancement P3 status/ready topic/design-front-end

Is your feature request related to a problem? Please describe.

Currently, IPFS Webui and Desktop to not allow for content discovery. The only way I know to discover content on ipfs is via ipfs-search.com. I would love be able to discover new ipfs content, or old interesting content, or any content on IPFS so I can better appreciate the value of all the data that exists.

Describe the solution you'd like

I want to be able to search for content on IPFS via ipfs-search's API and then see the results within the ipfs-webui on a results screen.

Rough plan we've discussed
V0
V1
  • Add cross-functionality between ipfs-search.com results and ipld-explore page functionality.
    • ideally, a user could "explore" an ipfs-search.com result within webui, or "ipfs-search" for similar content from the explore CID page. i.e. backlinks on both sides.
  • Enhanced and simplified UX that handles EITHER explore(select & explore) CID submission, or search(discover) functionality within the SINGLE input at the top of webui screens.
  • Results list
    • Items in the list allow you to access the content on ipfs-search (small target=blank icon) OR explore (explore CID) them easily, or VIEW them (videos/images/etc) within webui

Describe alternatives you've considered

  • I've considered not adding this functionality and just redirecting users to ipfs-search.com, but I believe our large userbase could benefit from being exposed to ipfs-search.com through our familiar ipld-explore-cid functionality that already exists.

Additional context

  • I've discussed this with the ipfs-search team face to face at #IPFSCamp22 and they're excited to collaborate on this and agree it would be a big win for both of us and our customers.
  • One implementation we've talked about doing is overloading the CID Explorer input field, however, this may cause UX issues with users familiar with that input. We want to make sure that we do not break their current expectations, while also exposing them gently and encouragingly to the new functionality.
Lenguaje dominante
JavaScript
Estrellas
1.6k
Forks
539
Métricas de merge de PR
Sin PR fusionados en 30 d

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de ipfs/ipfs-webui

Todos los issues de ipfs/ipfs-webui

Issues similares

Más issues de JavaScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.