nmdc:// [ REJECTED ].

[Delion]

Now hublist uses NMDC hub addresses like dchub://blahblah:411
No need for default 411 port to be stated btw.

Maybe use nmdc://blahblah.nop:411 ? It is modern and supported by all clients these days.

Seems just cool)

[Admin]

I'm nor sure if i understand this correctly.
NMDC by defaults assumes hub uses port 411 - if not specified otherwise.
This hublist doesnt assume any postr - port specification is required during registration and wont be accepted without one.

[Delion]

My initial idea was turn dchub// links into nmdc:// links to be more modern since adc:// is here for ten(!) years.
Maybe I should note also, that for nmdc:// links port is not optional, even default.

Second though of mine is that if dchub:// links are already used, they could easy be cutted to be more readable.

Look at the options:

[Admin]

is nmdc:// supported by strong dc? linuxdc++, dcgui ?

[Delion]

Hell yes! It's ancient.

[Derek]

I will look into that.
Replacing dchub:// with nmdc:// is a trivial fix.
Problem might be with what clients support that - i will have to make sure this won't cause a drama before we move on.

[Admin]

Trivial fix?
Yeah about 120 lines of code to edit in probably at least 20 files.

[Delion]

Problem might be with what clients support that

Not sure if you can find clients NOT support that...

[Admin]

Once verified with client support this will be implemented with next major script upgrade.
Prob in 2019.

[Derek]

Client support might be ok.
Problem is here:
When nmdc:// link is generated via PHP on some page browsers like chrome or firefox don't link it to dc client. They do that fine in case of dchub://

So for now dchub:// is more reliable - i suggest to hold on with that for now.