Alain Bourgeois

@jeff-zucker I agree it is not high priority. But when you get in, and thinks it is quite simple and don't find the code logic you somehow are frustrated. @zg009...

This is not in the tests, but to improve the code to use https://github.com/nodeSolidServer/node-solid-server/blob/1034123e268365230342894db825f8f419af1b32/lib/models/account-manager.js#L50-L51 in place of `/profile/card#me`

replaced wirh url.origin and updated tests that should have failed on relative webId and did not.

I think I understand your point. But to my understanding in the described situation we do not have a Solid Resource until there is a valid pod, and then here...

The image below set the situation. I reproduced the error I was logged in http://bob.localhost:8080 clicked on /test.html (existing resource) inside /settings/ (this is a private folder) 

You are right I reproduced the issue with CSS v1.7.4

Temporarily Proposals : (do not create when there is an issue) 1. do not create account if the data folder do not exist 2. blank and @ in podName either...

Preparing end January 2025 migration : 1. - disks - [x] solidcommunity.net data should be on disk 1 - [x] disk 3 shall be for weekly backup of solidcommunity.net running...

- NSS backup to disk 4 - users `# ls -al /mnt/volume_lon1_04/solidcommunity.net.bak/.db/o*/users/users | wc -l` --> 65471 - containers `# ls -d /mnt/volume_lon1_04/solidcommunity.net.bak/data | wc -l `--> 63111 ``` root@solidcommunity:/mnt/volume_lon1_01#...

- migration to CSS ``` NSS userFiles 65468 Invalid NSS config invalid Json 4 deprecated config filename 3309 invalid config keys 2293 invalid NSS pods username with dot 1213 no...