Flexhub ADC Ping Fixed - but oh Jesus!!

[akruk]

Yup. Flex pings fine now in both adc and nmdc.
Moved all adc listening flexhubs to adc section just to find out that:

Users of different protocols can chat and PM, searching and downloading isn't possible between different protocols.

WTF?
Most users on flexhub powered hubs use neomodus - upon entering them in adc - all u get is a list of 0 share users and no search. Chatroom basically.
So at this point all my work seems to be pointless as i think since all flexhub users are on nmdc - we should treat them as nmdc hubs.

If i am right - we should revert all flexhubs back to nmdc.

[Demona]

Sorry for your loss of time.

Yeah.
Dexo's go-hub does the transition better and can be listed as ADC soft. Flexhub? Nope!
Def. we should not list flexhubs in adc category unless most users in the hub are connected using ADC protocol. This needs to be reverted to what it was before.

[Admin]

I agree.
That's too damned bad, because flexhub in adc supports utf-8.
I hate nmdc.
I will do the "revert" probably in a day or so.
Sorry - bussy!!!!

[Delion]

Most users on flexhub powered hubs use neomodus

Yepp. Once I tried to do the same thing as you and noticed that too.

Dexo's go-hub does the transition better and can be listed as ADC soft

Wow wow, not so fast!
All go-hub based hubs I saw were filled with about 90% NMDC users. And remember, there is still no mechanism for protocol switching. So I don't see a lot of reasons consider them as ADC hubs yet.

However, there is another cool option for both flexhubs and go-hubs.
The pinger could ask, count and report NMDC and ADC users separately

At least for flexhubs the protocol used is clearly reported within the user's description with [ADC], [ADCS], [NMDC] or [NMDCS] tags.

Please consider this as a feature request.

[Admin]

Ok, so i went ahead and connected to all of them flexhubs. Checked if they have adcs ports sepcified and i left only few flexhubs that actually do have adc users in them.

@akruk
So at this point all my work seems to be pointless as i think since all flexhub users are on nmdc - we should treat them as nmdc hubs.

No it wasn't pointless. I had this issue for years. I'm not very good at DC protocols i i wasnt able to create a fix. U did great and thank you. As u can see some flexhubs have some adc users like MIMIC hub from Czech Republic for example and now they are finally listed in correct section.

Wow wow, not so fast!
All go-hub based hubs I saw were filled with about 90% NMDC users. And remember, there is still no mechanism for protocol switching. So I don't see a lot of reasons consider them as ADC hubs yet.

Does it mean that go-hub is just like flexhub? Meaning can a adc user search and download from nmdc users and vice versa?

However, there is another cool option for both flexhubs and go-hubs.
The pinger could ask, count and report NMDC and ADC users separately

Yes - but what is the point? And still how do i categorize hubs that are basically chatrooms for users that have mismatched protocols..

[Delion]

Meaning can a adc user search and download from nmdc users and vice versa?

Sure not. DC client only uses a protocol specified in a hub address.

As u can see some flexhubs have some adc users like MIMIC hub from Czech Republic

Lol. That's only because it was a testbed for the 'uhub mimic mod' project.

Yes - but what is the point?

The hybrid hubs could be used both as NMDC and ADC hubs, but not simultaneously. So just user list checking always gives the wrong total user count.

The way to fix it is to count NMDC and ADC users separately.

[Dexo]

Dexo here, let me clarify a few misconceptions about go-hub

All go-hub based hubs I saw were filled with about 90% NMDC users.

That's correct, but it's only because a few main installations are made by admins who maintain an NMDC hub. So they tend to keep the protocol when redirecting users to go-hub.

So I don't see a lot of reasons consider them as ADC hubs yet.

Technically, go-hub is an ADC hub. It uses SIDs and CIDs internally, just like any other ADC hub, but it emulates those IDs for NMDC clients.

I highly encourage to try running go-hub with ADC to break those statistics The nice thing is that recently I added support for redirects, so you can now tell go-hub to automatically redirect NMDC->ADC (and/or ADC -> ADCS, NMDC -> ADCS).

Does it mean that go-hub is just like flexhub? Meaning can a adc user search and download from nmdc users and vice versa?

Sure not. DC client only uses a protocol specified in a hub address.

This is incorrect. AFAIK, go-hub is the only hubsoft that support searches across protocols. This means that ADC clients receive search results from NMDC and vise-versa. Having said that...

And remember, there is still no mechanism for protocol switching.

This is actually correct for clients. There is no clients that can connect to ADC peers given search results from NMDC hub. But it's possible and planned. Given current state I think ncdc client may be the first one that will implement it.

go-hub also has an ability to proxy files for ADC to NMDC and back. But this increases the load on the hub significantly and is disabled by default. This is useful for having the hub and the client to run through Tor, though

[Delion]

but it's only because a few main installations are made by admins who maintain an NMDC hub

Technically, go-hub is an ADC hub

DC client only uses a protocol specified in a hub address

Well, this is exactly the same situation as with flexhubs. And technically, from the DC client point of view, that's all still 100% correct.

This means that ADC clients receive search results from NMDC and vise-versa

Dexo, I asked you to join this conversation to find out how to send correct info about protocol users on hybrid hubs. Not hub users, but protocol users.

[Dexo]

Well, this is exactly the same situation as with flexhubs. And technically, from the DC client point of view, that's all still 100% correct.

Correct, until it is fixed on clients, which may happen this year

Dexo, I asked you to join this conversation to find out how to send correct info about protocol users on hybrid hubs. Not hub users, but protocol users.

I'd rather report all users anyway - it will save Hades from doing additional work when we finally fix clients.

[Admin]

So just to make is simple for me. Go-hub does support multiprorocol chat and searches but does not support multiprotocol downloads. ATM. Right?