Re: Demanding Interoperability to Strengthen the Free (Libre) Web: Introducing DISFLUID

[Aleix Conchillo Flaqué]

Hi Vivien,

This sounds great even though I don't fully understand it :-) but I'm
starting to read a little bit about Solid (and Disfluid). While I was
reading I found this:

"""
Both the header and the payload use the JSON representation from srfi-180:
objects are alists of symbols to values, arrays are vectors. It is
unfortunate that guile-json has a slightly different representation, where
alist keys are strings, but we hope that in the future SRFI-180 will be
more closely respected.
"""

Unfortunately guile-json doesn't follow srfi-180 api (it was created much
sooner), but regarding alists' keys it can support both symbols and
strings. So you can do (scm->json '((foo . "bar"))) or (scm->json
'(("foo" . "bar"))) and both would work the same.

By the way, a long time ago I also worked on guile-jwt (
https://github.com/aconchillo/guile-jwt) which is SUPER basic compared to
what you've done. I was planning to add JWK support at some point. I'm
wondering if we could take your code and merge it into guile-jwt so other
projects can use it. What do you think? Right now I don't have much time
but if you say it's fine I could work on it whenever I'm free.

Thank you!

Aleix

On Fri, Jul 30, 2021 at 4:21 AM Vivien Kraus via General Guile related
discussions <guile-user@gnu.org> wrote:
>
> Hello Guile users,
>
> I’m writing a Solid server in guile:
>
> https://disfluid.planete-kraus.eu/
> https://labo.planete-kraus.eu/webid-oidc.git/
>
> The main point of Solid [1] is to separate the web applications from
> the data they use in an interoperable way.
>
> It’s in the spirit of Activitypub, but closer to the current
> architecture of the web. So, whenever you see "Log in with <data
> silo>", you could easily demand that the application let you log in
> with your identity on your Solid pod.
>
> If that takes off, we’ll be able to run any competing web application
> with any data storage ("pod"), because the communication is
> interoperable and the vocabulary used is public. Which means that we
> will be able to easily replace proprietary program with free programs!
> The best thing is, we won’t even need to develop for a web browser.
> That’s a cool solution to the JavaScript trap.
>
> Now, we need to make sure that there is a freedom-respecting way to
> develop applications. This is why I’m writing this project. With a
> clear focus on user freedom, we will maximize our chances to avoid the
> future JS traps. In this regard, disfluid is not Solid.
>
> [1]: https://solidproject.org/
>