-
Notifications
You must be signed in to change notification settings - Fork 103
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
update list with current, known instances in the wild, added 7 URLs #888
Conversation
d2024-05-10 t08:47
d2024-05-10 t09:24
d2024-05-10 t10:01
d2024-05-10 t10:05
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Couple of things. Not sure about the correctness of some of this information, e.g., the software that's being used. Is that based on public information or informed by the provider? Some of the services require paid sign-ups, so can't tell.
Generally, we should aim to have the consent of the provider to be listed in this table. Or at least inform them that they are being listed so that they can have a chance to correct this information.
d2024-05-18 t06:59 - I have left Inrupt Pod spaces in the list, because in the current state, it already is also in there. - I have updated the startpage of solidweb.org with a comment about enabled/disabled corsProxy. - I have linked to the correct terms and conditions of the european Trinpod service. - I have deleted the KIT page, because registration is disabled. - I have deleted the OpenLink servers, because the server seems no original NSS and the versions seem deprecated (v4 and v5) ---- the KMI Open University site has no impressum, so I'm not sure how to inform them that we added their instance.
I have edited precisely. |
d2024-05-18 t07:38 corrected trinpod US hosting company, as suggested by Fred (owner)
d2024-05-18 t07:44
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
how do we find consensus ?
+1 for keeping it in the list...
@ewingson — in b98072b, you said --
I need to understand what the above means.
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. |
Sarven mentioned
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... |
d2024-05-31 t18:03
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.. |
@kidehen @csarven @TallTed @melvincarvalho @michielbdejong @-maintainers- Thank you. I have added them. |
d2024-06-04 t03:45 yes. makes sense. thx.
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