unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Nala Ginrut <nalaginrut@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: Sat, 31 Jul 2021 14:14:10 +0800	[thread overview]
Message-ID: <CAPjoZodiFjJw5p0GnpP=3R6VkQd==Z6Uzb3dX7JWWRtM+fHUSg@mail.gmail.com> (raw)
In-Reply-To: <5cbc279ee59779dcaca73de7745a9d0dbd5abfce.camel@planete-kraus.eu>

Looks really neat!
I'm still not familiar with Pod.
Is it possible to cooperate with a modern web framework? It seems it
doesn't require JS and browser, so I don't know if http can still work as
usual.

Best regards.

On Fri, Jul 30, 2021, 19:21 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/
>
>
>


  parent reply	other threads:[~2021-07-31  6:14 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 [this message]
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é
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='CAPjoZodiFjJw5p0GnpP=3R6VkQd==Z6Uzb3dX7JWWRtM+fHUSg@mail.gmail.com' \
    --to=nalaginrut@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).