From: "Aleix Conchillo Flaqué" <aconchillo@gmail.com>
To: Vivien Kraus <vivien@planete-kraus.eu>
Cc: guile-user <guile-user@gnu.org>
Subject: Re: Demanding Interoperability to Strengthen the Free (Libre) Web: Introducing DISFLUID
Date: Sun, 1 Aug 2021 23:27:19 -0700 [thread overview]
Message-ID: <CA+XASoVwkBH_ryK_xPTY1Qrj2vHMsENpZyU8HjREnaUNF9MrdA@mail.gmail.com> (raw)
In-Reply-To: <5cbc279ee59779dcaca73de7745a9d0dbd5abfce.camel@planete-kraus.eu>
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/
>
next prev parent reply other threads:[~2021-08-02 6:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-30 11:21 Demanding Interoperability to Strengthen the Free (Libre) Web: Introducing DISFLUID Vivien Kraus via General Guile related discussions
2021-07-30 14:10 ` Jérémy Korwin-Zmijowski
2021-07-31 6:14 ` Nala Ginrut
2021-07-31 7:06 ` Vivien Kraus via General Guile related discussions
2021-07-31 8:58 ` Dr. Arne Babenhauserheide
2021-07-31 9:09 ` Vivien Kraus via General Guile related discussions
2021-08-02 6:27 ` Aleix Conchillo Flaqué [this message]
2021-08-02 8:20 ` Vivien Kraus via General Guile related discussions
2021-08-02 9:27 ` Aleix Conchillo Flaqué
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CA+XASoVwkBH_ryK_xPTY1Qrj2vHMsENpZyU8HjREnaUNF9MrdA@mail.gmail.com \
--to=aconchillo@gmail.com \
--cc=guile-user@gnu.org \
--cc=vivien@planete-kraus.eu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).