From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: Any interest in creating an nnfediverse backend?
Date: Thu, 24 Sep 2020 09:56:26 -0700 [thread overview]
Message-ID: <874knndsg5.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <86r1qr6u9n.fsf@dod.no>
Steinar Bang <sb@dod.no> writes:
> Is there any interest in creating one, or more, backend(s) for "the
> fediverse"?
>
> "The fediverse" is a common term for services that aim to replace
> today's social media with decentralized alternatives.
>
> I have tried two of them:
> 1. The twitter replacement mastodon
> 2. The facebook replacement diaspora
>
> Both of them are based on having no centralized node, but instead having
> decentralized server that talk to other servers and exchange postings
> (similar to USENET).
But these all must have their own APIs and protocols, right? I doubt it
will be possible to write one nnfediverse backend that could serve all
these different services -- we'd need an nnmastodon, nndiaspora... etc.
Not to say it couldn't be done! I wonder about usability, though. The
more a service moves away from "email-like" and towards the direction of
"chat-like", the less appropriate Gnus will be, I think. Mastodon is
probably fine, but I don't know how diaspora works.
It would be nice to have Gnus handle pub/sub stuff, too.
next prev parent reply other threads:[~2020-09-24 16:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-24 15:59 Steinar Bang
2020-09-24 16:12 ` Emanuel Berg
2020-09-24 16:56 ` Eric Abrahamsen [this message]
2020-09-24 18:00 ` Steinar Bang
2020-09-24 18:11 ` Andreas Schwab
2020-09-24 18:24 ` Eric Abrahamsen
2020-09-24 19:02 ` Steinar Bang
2020-09-25 2:19 ` 黃炳熙
2020-09-25 16:41 ` Tassilo Horn
2020-09-25 18:09 ` Eric Abrahamsen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874knndsg5.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=ding@gnus.org \
/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 NNTP newsgroup(s).