Hublist • Frequently asked questionsYou might want to get familiar with our frequently asked questions before seeking help elsewhere. Table of contents:
- Why was my hub deleted or banned?
- Is there a registration server?
- What about plain text user search?
- What is the best way to get help?
- How to fix display of cyrillic characters in my hub information?
- Is there support for hub icon and logotype?
- Does pinger support custom login?
- How often are hubs pinged?
- Why are some hub icons left aligned?
- How to set my hubs website and email address?
- What is the meaning of different colors in userlist on my hub page?
- How to change my hub address?
- How to change location of my hub?
- Can you add another country specific client hublist?
- Is it possible to disable reports from pinger about AVDB detected users?
- What IP address does your pinger use?
- Is it possible to enable kicking of AVDB detected users by pinger?
- How does hub network grouping works?
- Next question?
1. Why was my hub deleted or banned?Usually you can find ban reason on hub information page along with the ban status, however, here are several reasons why your hub could get deleted or banned:
- Fake users
- Fake share
- Redirect array
- Private hub
- Vote cheating
- Comment cheating
- Offline long time
- Low reliability
- Stolen address
- Pinger disabled
- Pinger banned
These are our hublist rules. To unban a hub after fixing all the problems, contact our support team.
2. Is there a registration server?Our registration server is running at address hublist.te-home.net:2501, but is strictly limited to 10 connections per hour from one IP address.
3. What about plain text user search?We have full $MyINFO plain text user search available, known parameter names are nick for nick, desc for description, tag for client tag, conn for connection type, mail for email address, share for share size and ip for IP address, all of them can be used together. To use this feature you need to send HTTP GET request like this to our server:
Following columns can be enabled or disabled and will be shown in order of their appearance in this list, here you can also see their default values: conick=1, codesc=0, cotag=0, coconn=0, comail=0, coshare=0 and coip=0. Found results will be returned in following format depending on your column configuration, each user on new line without carriage return:
Results are limited to 25 users per hub. HeXHub and Verlihub + Ledokol already use this feature, and so can you.
4. What is the best way to get help?Visit our public hub to chat with operators face to face. After you enter the hub, send +enter command in PM to # Hublist chatroom and state your issues afterwards. Please remember, operators are not always there, it might take a while before you get answers.
5. How to fix display of cyrillic characters in my hub information?You need to contact an operator to change the character encoding to CP1251 for your hub. Hublist pinger uses encoding CP1252 by default. Alternative to this method is that your hub sends $HubINFO with 11'th parameter as preferred encoding:
Sample$HubINFO N€M€SIS$nemesis.te-home.net$']['€AM€LI']['€ PUBLIC$64000$0$1$0$Verlihub$']['€AM€LI']['€$Public$CP1251|
HeXHub and Verlihub already support this. Please note, our hublist also supports following character encodings:
- CP1252 - Latin - West Europe
- CP1251 - Cyrillic
- CP1250 - Latin - Central and East Europe
- GB18030 - Chinese
- UTF-8 - Unicode
6. Is there support for hub icon and logotype?Yes, your hub can send $SetIcon and $SetLogo containing full URL to hub icon and logotype, these commands should be sent before $HubINFO:
Icons are downsized to maximum of 16x16 pixels on hub information page and 16x16 pixels in lists all over the site. Logotypes are downsized to maximum of 800x600 pixels, image is also not downsized and are clickable for full size view. Image MIME must be of type image, complete list is available here. HeXHub and Verlihub already support hub icon and logotype.
7. Does pinger support custom login?Yes, our pinger supports following custom login information:
- Nick • Default: TEPinger
- Password • Default: None
- Tag • Default: <++ V:0.867,M:A,H:1/1/2,S:9>
- Share • Default: 133719586729
Due to recent protocol flood attacks on all hubs, where our default pinger nick was used, we are now forced to use random nicks on all hubs except those where pinger is registered with specific nick. There is a way to detect whether the pinger is real or not by checking out its IP address, which is always 220.127.116.11. Please contact us in order to customize pinger for your hub.