Open cbm80 opened 8 years ago
Thanks again for your suggestions @cbm80!
Are irc://
, proxy://
and znc://
with parameters used (or even specified) some where already?
I recently came across this format used by 4xdcc.info:
xdcc://{network-name}/{hostname}/{#channel}/{xdccbot}/#{pack}/{filename}/msg {xdccbot} xdcc send
XDCC-Grabscher uses a similiar format with hostname
and network-name
swapped and without the message part:
xdcc://{hostname}/{network-name}/{#channel}/{xdccbot}/#{pack}/{filename}
IMHO it would be best to support xdcc://
with all options and irc://
/ircs://
without bot/pack options as commonly used.
Are irc://, proxy:// and znc:// with parameters used (or even specified) some where already?
Probably not, I just made them up :) The closest thing to an agreed upon standard for IRC URIs seems to be an old draft from 1997 for an RFC that was never approved:
http://www.w3.org/Addressing/draft-mirashi-url-irc-01.txt
This is at least what mIRC uses. There's no 'standard' for XDCC URIs that I know of.
fiy
source of the "original" xdcc link format http://xdccklipper.sourceforge.net/
4xdcc.info still uses the same search spiders.
Lars somehow switched {hostname} and {network-name} for XDCC-Grabscher. It was ment to be like in IRC-Klipper. If I remember correctly '/msg {xdccbot} xdcc send' was never part of the protocol. But I'm not sure about that.
Hoffe das hilft.
On the command-line add an option to specify an URI instead of individual options, ie.
direct connection:
irc://irc.example.com:6668/?chan=chan1,chan2&nick=xdccbot&pack=1234
transparent proxy:
proxy://user:password@irc.myproxy.com:7777/?chan=chan1,chan2&nick=xdccbot&pack=1234
znc-proxy with auto-connect and TLS:
znc://user:password@irc.myproxy.com:7777/?chan=chan1,chan2&nick=xdccbot&pack=1234&tls=true
Perhaps even add an option to put URIs into a config-file and reference them by alias, ie.
supernetwork="irc://irc.example.com:6668/?chan=chan1,chan2"
So it can be used like:
xdcc supernetwork xdccbot 1234