FlipFlop
Tester-
Content count
17 -
Joined
-
Last visited
Posts posted by FlipFlop
-
-
Haha, every software has it's trolls, and captainfreeky a.k.a. Joe is FlexHub's all time favorite troll.
Contains lot of bugs
Name two of them.
One more thing as flex is so buggy needs update and update and lot of things changes
FlexHub is being actively developed, that means we listen to the people using it (as long as they can behave, you know what i mean), and keep adding new features and improving the hubsoft. That's what the updates are about. And since version 0.2 FlexHub has become a very stable hubsoft. Ofcourse bugs are fixed with every release as well, but with the inline update system updates are easy and run smooth. It's even possible to run updates without having to restart the hub.
And indeed, as Lee already stated, supporting large usercounts has never been the goal for FlexHub. But maximum control, feature-rich, flexible and supporting NMDC/NMDCS ADC/ADCS protocol in one hub is not something many other hubsofts can offer.
-
The cooperation between FlexHub and Apex will be an interesting one, by closing the gap between client and hub development some very nice features will be brought to the DC community in the near future! Don't miss it!
Lee likes this -
-
Correct, but since not all hubs can be trusted, blocking port 80 and 2501 at least protects from allowing a client to participate in ddosing a website or hublist regserver
-
It's possible that the hubsoft blocks it since the NAT traversal involves a few minor changes to the $ConnectToMe command. What hubsoft/version is used?
One other note: it takes two clients that use NAT traversal, so you will only be able to connect passive-passive if both clients are using this implementation. So both clients have to be StrongDC++ based and recent.
-
-
-
-
There's still a bug with calculating the $Key:
[11:03:31] <FlexBot> IP: ***.***.***.*** <nick unknown> was disconnected because: Wrong key received after lock: $Key 4ÑÀ° A ѱ±ÀÀ01‘ ÑÑqÑ!‘Ñ‘ ѱ±ÀÀ01p 0
[11:03:31] <FlexBot> Lock was: EXTENDEDPROTOCOL_FLEXHUB_MULTIPROTOCOL_VQSP
[11:03:31] <FlexBot> Proper key: 4ÑÀ° A ѱ±ÀÀ01‘ ÑÑqÑ!‘Ñ‘ ѱ±ÀÀ01p 0
[11:05:22] <FlexBot> IP: ***.***.***.*** <nick unknown> was disconnected because: Wrong key received after lock: $Key ãÑÀ° A ѱ±ÀÀ01‘ ÑÑqÑ!‘Ñ‘ ѱ±ÀÀ01¶§Çç
[11:05:22] <FlexBot> Lock was: EXTENDEDPROTOCOL_FLEXHUB_MULTIPROTOCOL_4N2L
[11:05:22] <FlexBot> Proper key: ãÑÀ° A ѱ±ÀÀ01‘ ÑÑqÑ!‘Ñ‘ ѱ±ÀÀ01¶§Çç
-
-
-
-
-
There seems to be a bug in calculating or formatting the $Key:
$Lock was:
EXTENDEDPROTOCOL_FLEXHUB_MULTIPROTOCOL_ML26
Received :
$Key ÑÀ° A ѱ±ÀÀ01‘ ÑÑqÑ!‘Ñ‘ ѱ±ÀÀ01!ç@a³e´1q¡/%DCN096%/åáá
Should have been:
$Key DÑÀ° A ѱ±ÀÀ01‘ ÑÑqÑ!‘Ñ‘ ѱ±ÀÀ01!ç@
It looks like the key isn't calculated at all, just sending the same key everytime.
-
Accuracy would depend on implementation, I have no idea how that's handled in clients, but technically it shouldn't be a problem to keep track of from which hub a pm came.
But even when not 100% accurate, it would be a nice feature! I might even start to use Apex instead of RSX... :blink:
-
Would be a nice feature to be able to use ctrl or alt-leftclick on a PM tab to jump to the hub where the PM came from.
AndroidDC
in Lounge
Posted
Great app!
Only issue I've seen with last update is that chatrooms aren't working. Every incoming message from a chatroom is seen as a separate PM from the one sending the message to the chatroom. It's possible to send a message to the chatroom, but all replies will be separate PM's from users, not the chatroom.