update list with current, known instances in the wild, added 7 URLs

[ewingson]

d2024-05-09 t20:53

doing this crosschecked with @csarven, @bourgeoa or maintainers, please review and merge

foreseeable the added providers are persistent enough

hope that helps

[ewingson]

I have edited precisely. though, not sure, how to use the github resolve conversation feature

[TallTed]

@ewingson — in https://github.com/solid/solidproject.org/pull/888/commits/b98072b96c5d7ad6f7958d6f4bd28c9736c04ff4, you said --

- I have deleted the OpenLink servers, because the server seems no original 
  NSS and the versions seem deprecated (v4 and v5)

I need to understand what the above means.

• "the server seems no original NSS" is not English.
• "the versions seem deprecated (v4 and v5)" suggests that the list is only meant to include specific version(s) of something, but I don't see anything that says what those versions are.

To my mind, "current, known instances in the wild" should include any version of any implementation. That should include those two OpenLink-hosted instances, which are running OpenLink forks of NSS.

/cc @kidehen @openlink

[ewingson]

@TallTed

Sarven mentioned

Seems like it is NSS with some OpenLink customisations? If that's a different software than NSS, it is better to link to that instead of NSS.

if it is a minor concern, that the two servers are running Solid 4.4.2 and 5.0.1 (which seem at least originated in Node Solid Server) we can of course again include them in the list (which then would (positively) be more inclusive).

let's look what Kingsley can contribute...

[kidehen]

Those are instances that work, and based on what @TallTed has already stated. You should only be concerned if they aren't working, otherwise, they are usable solid servers etc..

[ewingson]

@kidehen @csarven @TallTed @melvincarvalho @michielbdejong @-maintainers-

Thank you. I have added them.