SolidOS for devs: https://github.com/solidos/solidos SolidOS Pod: https://solidos.solidcommunity.net/
How should I test logged-in functionality, then?
or login in to a local auth'd CSS or to inrupt.com - anything but the old NSS
actually local CSS won't work
I can unfold the folders until I get to the Meetulator poll at https://timbl.com/timbl/Public/2021/Solid%20Editors%20weekly/ and then I get redirected to https://solidcommunity.net:8443/authorize?client_id=b0d3c11e4970c5654...5&redirect_uri=https%3A%2F%2Ftimbl.com%2Ftimbl%2FPublic%2F&response_type=code&scope=openid%20offline_access&state=6ce6b...4e7999f&code_challenge=vDGoIpzuhl5...Qo&code_challenge_method=S256&prompt=none&response_mode=query
Logged in to 8443 I get the same redirections and on the resulting page "Error: Update: Can't make changes in uneditable https://timbl.com/timbl/Public/2021/Solid%20Editors%20weekly/index.ttl u"
A problem with changing the login out calls?
Meeting pane builds for me at the moment
For example, The meeting
https://timbl.com/timbl/Public/2021/Solid%20Editors%20weekly/ should in fact show me https://timbl.com/timbl/Public/2021/Solid%20Editors%20weekly/index.ttl#this but it gets redirected to https://timbl.com/timbl/Public/2021/Solid%20Editors%20weekly/#this which is nonsense. I am logged in with a username from the test version. I get thousands of copies of this:
logIn: Already logged in as <https://timbl.solidcommunity.net:8443/profile/card#me>
mashlib.js:126298 (Logged in as <https://timbl.solidcommunity.net:8443/profile/card#me> by authentication)
the browser suppresses those messages after the first few hundred.
@timbl @jeff-zucker @SharonStrats @jaxoncreed @theRealImy
new mashlib@1.7.5-alpha-3-98ed3958 running on https://solidcommunity.net:8443
This version includes updated auth-upgrade of meeting-pane and issue-pane.
All panes are using solid-ui auth-upgrade
new mashlib@1.7.5-alpha-3-98ed3958 running on https://solidcommunity.net:8443
This version includes updated auth-upgrade of meeting-pane and issue-pane.
All panes are using solid-ui auth-upgrade
@/all - let's begin opening issues on the auth-upgrade branch so that we can track them separately and see how many there are to help evaluate how close to being ready to push we are. Here's first one : solid/solidos#56
2 replies
@timbl - do you get those same results if you login to inrupt.com? It's hard to tell whether the problems are from being served via NSS or from being accessed from an NSS IDP or both.
Just a note: I am porting this month Alexandre Bertails Banana-rdf to Scala3
https://github.com/bblfish/banana-play
https://github.com/bblfish/banana-play
That should allow one to efficiently write the same code that compiles to Java (Jena or rdf4j) or JS libs.
Same framwork should then also enable compilation to native.
Currently I am thinking of creating types for relative URLs, relative. Triples and Relative Graphs, so that code can always be clear about what is possible with a particular graph. E.g. It should not be possible to serialise a relative graph to NTriples.
or maybe checkuser does
window.location.href = curUrl.toString(); which causes the page to reload… is this code to add on a msiing “#this” lost the log in maybe … you can’t just set the window.location.href without causing navigation to occur … not sure of the conditions for that\
3 replies
"Do we a have a refresh mechanisam in plce?” — yes we should not
"either use a cookie or re-log-in at the IDP to get a new one from the IDP” — see the spcec
What does the spce say a bout ow lobfg to set it?
Issue: Aaron should be in sync with the spec, he should be ghappy with what it says.
Meeting minutes 15.09:
- the auth upgrade is blocked by the login and logout problems: issues are recorded on SolidOS starting with Auth-upgrade name: https://github.com/solid/solidos/issues
- Sharon to start of some docu about it (wiki) - about what decisions were made why -
- ask Jackson for a code review - Timea to organize - invite Angelo too -
- node version - M1 chip does not support lover than 15; encryption libraries also needs 15 or upwards.
- token expiration in NSS is set to 2 weeks, we discussed about it and we were wondering what the spec says.
- onboarding feature - Timea started a discussion about it with different people including: Tim, Aaron, Kyra, Ruben..
- anyone wanting to share about onboarding is welcomed to write up Timea.
- we talked about refresh UI elements for the PR solid/profile-pane#15
- also make Folder pane implement this.
- need also to be documented.
- Sharon asking for PR on stand-alone contact-pane: solid/contacts-pane#57
- Tim explained and asked for PR: solid/solid-ui#430 - will be merged to auth-upgrade branch
- Sharon to look into time zones and a new meeting time
- Timea access to website solidos.community.net - to update team meeting times when we have new ones.
- testing for auth-upgrade will be ongoing.
Doing a refreshTrr for the wrole UI is not ideal. A lot of recaluculation… and mainly it won’t be the values of things which will have chnages a bit, it will be that now a different set of things ara avaliable. So where there was a “log in to chat” button there will be instead a message send widget, and so on
Any pane which can do more things if the users is loged in should listen for a login status change and change the to allow all the new extra possibilities.
The infinite chat does this.
That’s where the function turnOnInput tuns on the functionality which equires login
(often read does no but write does)
The philosophy of the mashlib is very much everything is local. You start a little workflow to do domething in a part of the screen where you are doing something else which needed it. You use what real estate you need in that spot to do whatevr it is, and then if you are finished, all the UI folds up , or leaves some more state in the thing you are building.