Search (Query URI)

[sjehuda]

Suggestion

Register a query URI for searching.

Use case

search:McCarthy+REA
search:The+Eternity+Service
search:XMPP
search:TempleOS
search:MXLinux

Extra info/examples/attachments

See ledgerism.net which I currently mirror to my site, yet I do not want to have any mention to a so called "search engine", especially when I search most of my information via BitTorrent software.

See search:McCarthy+REA at

• gemini://woodpeckersnest.space/~schapps/gldialtone/todays.gmi
• https://portal.mozz.us/gemini/woodpeckersnest.space/~schapps/gldialtone/todays.gmi

Discussion

qbittorrent/search-plugins#325

[cheater]

I don't get it.

Can you explain step by step what should happen, where you type in the searches, are there additional UI elements or APIs involved, etc?

[sjehuda]

I want to be able to utilize a query URI (or pseudo-protocol scheme)
called "search".

Instead of people to waste characters by writing: Search for "this
term" at "this service", they can use a query URI so that search be
conducted on their preferred indexers.

CURRENT

ch:

sj, I have found a series of research documents which you might be
interested of. http://searx.i2p/?q=accumulate+water+from+humidity

sj:

Thanks. I2P is not available at the moment. I will search on another
indexer.

PROPOSED

ch:

sj, I have found a series of research documents which you might be
interested of. search:accumulate+water+from+humidity

sj:

I am now seeing the results in Gnutella and qBitTorrent. I know some
of the authors. Thank you for sharing!

[cheater]

you're doing a terrible job of explaining this. start from the beginning.

[sjehuda]

Pardon.

I will try again.

---

Example magnet-link.

magnet:?xt=urn:btih:c63a772102952fd53ece929b0e877c507c529d60&dn=MX-23.4_x64.iso&tr=http%3A%2F%2Fl2.mxrepo.com%3A6969%2Fannounce&tr=http%3A%2F%2Fit.mxrepo.com%3A6969%2Fannounce

If I open that magnet-link, my system will open it with qBitTorrent, and qBitTorrent will open a prompt dialog to add this torrent, while it (attempt to download the torrent and) lists the content indexed by the torrent.

Example search.

search:MX-23.4_x64.iso

If I open that search-link, my system will open it with qBitTorrent, and qBitTorrent will open a its built-in search interface for term "MX-23.4_x64.iso".

---

I hope that this is better explained.

[cheater]

ok, so you would like to be able to type search:blahblah into a browser address bar (or click such a link), and then have qBt pop up with a new tab with search results?

That's pretty cool, I could see myself using that as well using something like the "Search from Popup or ContextMenu (SPC)" addon in firefox. This way I could e.g. select the text for a title like "Arch Linux", right click, and type in a few accelerator keys and have qBt pop up with a search result. That would be pretty amazing.

So I'm +1 on that.

I would name the namespace something other than search though, e.g. torrentsearch. So the link you'd have to have is e.g. torrentsearch:Arch Linux.

[sjehuda]

Thank you for the detailed message.

ok, so you would like to be able to type `search:blahblah` into a browser address bar (or click such a link), and then have qBt pop up with a new tab with search results?

Yes. Precisely.

That's pretty cool, I could see myself using that as well using something like the "Search from Popup or ContextMenu (SPC)" addon in firefox. This way I could e.g. select the text for a title like "Arch Linux", right click, and type in a few accelerator keys and have qBt pop up with a search result. That would be pretty amazing. So I'm +1 on that.

Thank you.

I would name the namespace something other than `search` though, e.g. `torrentsearch`. So the link you'd have to have is e.g. `torrentsearch:Arch Linux`.

I suggest both, search and torrentsearch. For the last 5 years, I conduct over 90% of my seraches via BitTorrent, ,hence I think that "search" would suffice. If you decide to adopt "torrentsearch", which is fine, then I suggest to consider both. For start, I think that it would be best to adopt only "search", then wait for other clients to align with this odea, and then further implement it to other namespaces.