mirror of
https://github.com/jlu5/PyLink.git
synced 2024-11-01 09:19:23 +01:00
29 lines
1.6 KiB
Markdown
29 lines
1.6 KiB
Markdown
# PyLink FAQ
|
|
|
|
### Does everyone need to install PyLink Relay for it to work?
|
|
|
|
**No!** Only the link administrator needs to host a PyLink instance, as each can connect to multiple networks. Everyone else only needs to add a link block on their IRCd.
|
|
|
|
InterJanus-style links between PyLink daemons are not supported yet; see https://github.com/GLolol/PyLink/issues/99 for progress regarding that.
|
|
|
|
### Does PyLink support Clientbot relay like Janus?
|
|
|
|
Yes, starting with PyLink 0.10. Clientbot support is in alpha stages and is far from complete: [Clientbot TODO](https://github.com/GLolol/PyLink/issues?q=is%3Aissue+is%3Aopen+label%3Aprotocols%2Fclientbot).
|
|
|
|
### What are PyLink Relay's benefits over Janus?
|
|
|
|
In no particular order:
|
|
- More complete support for modern IRCds (UnrealIRCd 4.x, InspIRCd 2.0, charybdis 4, Nefarious IRCu, etc.).
|
|
- PyLink is built upon a flexible, maintainable codebase.
|
|
- Cross platform (*nix, Windows, and probably others too).
|
|
- Proper protocol negotiation leading to fewer DoS possibilities:
|
|
- Better support for channel modes such as +fjMOR, etc.
|
|
- Configurable nick length limits for relayed users.
|
|
|
|
### I turned autoconnect for PyLink on, and now I'm getting errors!
|
|
|
|
PyLink does not support inbound connections - much like regular services such as Atheme or Anope, it only connects outwards *to* IRCds. (If you don't understand what this means, it means you should turn autoconnect OFF for PyLink)
|
|
|
|
### I get errors like "ImportError: No module named 'yaml'" when I start PyLink
|
|
- You are missing dependencies - re-read https://github.com/GLolol/PyLink#dependencies
|