Skip to content

Solid Resource IRIs are ugly and not user friendly #48

@kkalass

Description

@kkalass

Affected Package

locorda_solid

Steps to Reproduce

Use some app (for example the example Personal Notes App) and sync it with a Solid Pod.

Then, go to the solid pod and use some directory/file viewer (e.g. https://solid-file-manager.theodi.org/ ) to browse that pod.

Actual Behavior

You will find cryptic base64 encoded folders underneath data and indices

Expected Behavior

You see nicely organized, readable names as specified in our original spec.

Platform

No response

Environment

No response

Additional Context

The spec specifies that the solid type registry file should be used for mapping types to directories and specifies quite some details.

This is nice and good and so. But there is one thing that was not specified: If a user changes an entry in the type registry, we will not be able to find the old entries any more and when syncing we will create new entries under the new name. We have no guards against this.

Ideally, we find some solution or guards for this problem before implementing the type registry usage (and thus the nicer names).

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions