profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/jeff-zucker/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.
Jeff Zucker jeff-zucker Portland, Oregon, USA

jeff-zucker/solid-file-client 47

A Javascript library for creating and managing files and folders in Solid data stores

jeff-zucker/solid-ide 22

A syntax-highlighting editor and file manager for Solid data stores.

jeff-zucker/solid-auth-cli 11

a node/command-line Solid client with persistent login

jeff-zucker/solid-rest-browser 6

treats a browser's localStorage as a mini Solid server

jeff-zucker/data-kitchen 4

The solid databrowser technology as a stand-alone electron app

jeff-zucker/rdf-easy 4

easy access to linked data and RDF

jeff-zucker/solid-recursive-copy 3

Recursively copy resources across web sites which are solid-compatible

jeff-zucker/linked-bookmarks 1

Distributed shared bookmarking using linked data

push eventjeff-zucker/data-kitchen

Jeff Zucker

commit sha b05d674a2b121241b915a0cfe3b3b2884bfb548b

Update README.md

view details

push time in 3 days

push eventsolid/solidproject.org

Jeff Zucker

commit sha 05d2f8340ed9dd8003d4442699300fcf61f01318

Fix links to Data-Kitchen

view details

push time in 3 days

issue commentsolid/solidos

Auth-Upgrade does not completely logout of NSS

For me the following panes do not logout : rdf, about, markdown, source, folder, sharing. I haven't tested all the app panes.

jeff-zucker

comment created time in 7 days

issue commentsolid/solidos

Auth-Upgrade does not completely logout of NSS

I can also confirm, that although contacts pane looks like it is logged out, shows a login button, I can still modify the sharing of the address book itself

jeff-zucker

comment created time in 7 days

issue commentsolid/solidos

Auth-Upgrade does not completely logout of NSS

I can confirm - contacts pane logs out correctly for me but source and folder still do not.

jeff-zucker

comment created time in 7 days

issue commentsolid/solidos

Auth-Upgrade does not completely logout of NSS

Also please try against solidcommunity.net:8443 so we know we are all working against the same source.

jeff-zucker

comment created time in 7 days

issue commentsolid/solidos

Auth-Upgrade does not completely logout of NSS

Please try with the source pane or folder pane which is where I get the errors. The panes all act differently, showing it works in one pane does not prove it works in others.

jeff-zucker

comment created time in 7 days

issue commentsolid/solidos

Auth-Upgrade login pop-up has different styles

Ah, the real problem here is that the index.html page at https://solidcommunity.net/ has the OLD login button that goes directly to a login popup rather than to the IDP popup first. So NSS needs to change the buttons in its index.html template to be the new-auth buttons.

theRealImy

comment created time in 7 days

issue commentsolid/solidos

Auth-Upgrade login pop-up has different styles

These are two different things. The top one is a login popup served by NSS that lets you login ot NSS. The bottom one is an IDP popup that is served by SolidOS. In a normal flow we will click login, see the IDP popup, choose and IDP, then be directed to the login popup of whatever IDP we chose.

theRealImy

comment created time in 7 days

issue openedsolid/solidos

Auth-upgrade - eliminate HTML Links

There are several places in SolidOS where we use HTML links rather than gotoSubject() links. The HTML links open new web pages and thereby destroy any existing login information. The root index.html does this with "gotto X's files". Creating a new meeting offers you a "open newly created meeting" button which likewise jumps to a new page. There may be more places.

created time in 7 days

issue commentsolid/solidos

SolidOS Auth Upgrade

@bourgeoa , @jaxoncreed unfortunately, same behavior on logout. I'm not sure it makes any difference, but @jaxoncreed, logout is never called from your logout button directly, it is called from the drop-down user menu of the solid-ui-header which calls _authn.authSession.logout().

jaxoncreed

comment created time in 8 days

issue commentsolid/node-solid-server

Re-consider access token lifespan

@acoburn - thanks for the helpful explanation. What is a more reasonable expiration time? Is there a process for automatically refreshing the token on expiration that is missing from NSS?

theRealImy

comment created time in 8 days

issue commentsolid/solidos

Auth-Upgrade does not completely logout of NSS

Logged out users can also modify the sharing of all resources.

jeff-zucker

comment created time in 9 days

issue commentsolid/solidos

SolidOS Auth Upgrade

@jaxoncreed, @bourgeoa. I did a git pull, npm ci, npm run build on mashlib @1.7.5-alpha-3-98ed3958 and there are zero occurrences of loginIssuer in mashlib.js.

jaxoncreed

comment created time in 10 days

issue commentsolid/solidos

SolidOS Auth Upgrade

This is after logging out and then refreshing the page :

nss-logout

jaxoncreed

comment created time in 11 days

issue openedsolid/solidos

Auth-Upgrade does not completely logout of NSS

Using a web browser to go directly to login in to solidcommunity.net:8443 and then logout leaves the user in a mixed state where the UI looks like they are logged out and they can not create new or delete existing resources. However, they can still see read, edit, and save resources that require login.

created time in 11 days

issue commentsolid/solidos

Mashing up Multiple WebIDs and Pods

I might have several pods for each identity. So I'd imagine something like this in the profile :

<#me>
  :identity 
    [
      foaf:nick "Work" ;
      solid:oidcIssuer <https://broker.pod.inrupt.com> ;
      :domain <#workPod1>, <#workPod2> .
    ],
    [
      foaf:nick "Play" ;
      solid:oidcIssuer <https://solidcommunity.net> ;
      :domain <#playPod1>, <#playPod2> .
    ] .
jeff-zucker

comment created time in 13 days

issue commentsolid/solidos

SolidOS Auth Upgrade

The root URL https://solidcommunity.net:8443/ brings up a welcome to prototype page with the old login button going to a popup.

jaxoncreed

comment created time in 13 days

issue commentsolid/solidos

SolidOS Auth Upgrade

Unfortunately, the same logout situation directly in the browser : the UI looks like I'm logged out, I can not add or delete BUT I can edit and save and I can modify the sharing.

jaxoncreed

comment created time in 13 days

issue commentsolid/solidos

Mashing up Multiple WebIDs and Pods

The Open Culture Browser is one example of mashing up data from public sources (wikidata + internet archive). But it does not deal with logins and identities.

One way of experimenting with multiple IDs is in Data-Kitchen. I believe it's possible to open multiple independent browsing contexts (each with its own webID, for example) and to pull to a central location from all the contexts. From the user's point of view, everything could happen in one window/tab even if other windows/tabs might be operating headless in the background.

jeff-zucker

comment created time in 13 days

issue commentsolid/solidos

SolidOS Auth Upgrade

Great work building all that @bourgeoa, thanks!. Please let us know when that version is available on port 8443. I built mashlib@1.7.5-alpha-1-98ed3958 and am running Data-K with it against a local auth'd version of CSS. When trying to add something to the container when not logged in, it brings up second set of login/signup buttons but they go to @jaxoncreed 's IDP list, not the old popup. AFAIK everything in Data-K works on CSS and ESS, I am not sure if Alain changed the NSS, but the behavior is the same as I reported above - it never fully logs out.

jaxoncreed

comment created time in 14 days

issue commentsolid/web-access-control-spec

Client identification

And how many people who aren't familiar with those standards are going to know or remember the difference? Am I the agent or the client? And in this case, the client is an agent which adds an additional confusion.

csarven

comment created time in 14 days

issue commentsolid/web-access-control-spec

Client identification

The term "client" has multiple possible meanings. What makes sense to me is sub properties of acl:agent:

  acl:user [a foaf:Person]
  acl:app [a dc:Software; rdfs:comment "an OIDC Resource Client"]
  acl:group [a vcard:Group] 
csarven

comment created time in 14 days

issue commentsolid/solidos

SolidOS Auth Upgrade

@jeff-zucker you may be logged out. If you try to create anything it doesn't work.

As I've previously reported, there are many many places in SolidOS where login and logout happens and we are currently experiencing a situation in which the logout only happens in some of. The UI and the create new button know I am logged out, other parts of the interface do not. I am not completely logged out because a) if in the server-side mashlib, I can still see things I should only be able to see when logged in and b) if I am in Data-Kitchen, I know I am not logged out because if I try to login to another NSS server, the existing login will interfere.

jaxoncreed

comment created time in 14 days

issue commentsolid/solidos

SolidOS Auth Upgrade

@jaxoncreed - Alain informs me that the errors I reported in https://github.com/solid/solidos/issues/38#issuecomment-916983410 were after he had uploaded all your latest. :-(

jaxoncreed

comment created time in 14 days

issue commentsolid/specification

Specify container description

@elf-pavlik - thanks for those pointers, that looks like great work. I understand the desire to move away from dependence on hierarchical containers and appreciate the work of the inerop panel in providing easy pathways to a richer view of data organization. However, I'd argue against a complete abandonment of the traditional file-system view of a Solid Pod in favor of what the databrowser does - let you navigate either by the container structure or by the internal structure of the resources and assume that information like type of resource is easily available.

I am not speaking solely of the UI - new developers will need an easy path to things like local file system as Pod and migration from traditionally arranged cloud storage. I am obssessive enough to keep my photos in containers like /photos/politricks/climate-change/2021-08-Line3_Protest/, but not obsessive enough to tag each photo. When I move this to a Pod or use Data-Kitchen to run SolidOS on it in place, I want the ability to do proper tagging, but also I want that container-structure and media-type information preserved. And I want the ability to just plop something in a container and have it have minimal level of tagging.

Therefore, I argue in favor of defaulting to giving the user information on a simple GET of a container. For me, ESS's current use of LDP type and dc:format (or equivalent mime-type ontology) is a bare minimum. This would not interfere with Data Registration or with any approach that puts other kinds of server-managed metadata in a different place.

csarven

comment created time in 14 days

issue commentsolid/solidos

SolidOS Auth Upgrade

I have just (8am PDT) tested on NSS (directly in browse not DK or browse.html). After logging in, then logging out, the UI acts as if logged out but we are not logged out. A page refresh does not cure it, manually deleting the nss cookie does get us finally logged out : nss

jaxoncreed

comment created time in 14 days

issue commentsolid/specification

Specify container description

Can we get the work of specifying the ontologies that we want to use not mixed up with security considerations? Those are orthogonal.

The part of security that is relevant here is its relative weight. "What kinds of things?" is a totally expectable, common question asked of containers and does not deserve, I think, such a heavy-handed response. Why are we not saying "if you don't want someone to know that foo.png is an image, put it in a container they can't read". Instead we are making something that should be (and is on most systems) very easy into something quite hard for the sake of protecting something that can be protected by other means.

csarven

comment created time in 14 days

issue commentsolid/specification

Specify container description

Who am I? A container. What am I doing here? I contain things. What kinds of things? I could tell you, but then I'd have to kill you.

csarven

comment created time in 15 days

issue commentsolid/solidos

SolidOS Auth Upgrade

I just built with @jaxoncreed' latest mashlib :

  • browse.html - works as expected
  • data-kitchen - works as expected
  • solidcommunity.net:8443 multiple dokeli wierdness and "oops messages" I don't see in either of the other interfaces

@bourgeoa can you use this most recent mashlib on the test server?

jaxoncreed

comment created time in 15 days