From: Csepp <raingloom@riseup.net>
To: Attila Lendvai <attila@lendvai.name>
Cc: Simon Tournier <zimon.toutoune@gmail.com>,
Maxime Devos <maximedevos@telenet.be>,
Vijaya Anand <sunrockers8@gmail.com>,
pukkamustard <pukkamustard@posteo.net>,
guix-devel@gnu.org
Subject: Re: [GSoC 23] distributed substitutes, cost of storage
Date: Sat, 08 Apr 2023 02:46:44 +0200 [thread overview]
Message-ID: <87355bkwo2.fsf@riseup.net> (raw)
In-Reply-To: <KtH3n8sbX9krb8FeKfUfLMDQQxUChy1OAM_XGPkWph0OZN0pM72gPVIUmw73-ErVg6Gkrir4lxn-SQiXBoyfOrU3ocn457P7n2gkXLHEMe4=@lendvai.name>
Attila Lendvai <attila@lendvai.name> writes:
>> Could you be provide some details for helping my curiosity?
>
>
> this page also has a much shorter whitepaper:
>
> https://www.ethswarm.org/why
>
> it started out as a storage layer for Ethereum, and as such one of its
> main task is to store the blockchain data, but it's not limited to
> that. there's nothing special about the blockchain data from this
> perspective, and reflecting that, the Swarm project is not under the
> Ethereum umbrella anymore.
Haven't read the Swarm thing, going more off of the general vibe of
these cryptocurrency related projects that keep popping up:
Using some kind of (optional) web of trust for clients makes more sense
to me than making people pay with cryptocurrencies.
I should be able to set up two computers on a LAN in the middle of
nowhere without having to care about some blockchain's global
consistency.
NDN can do this right and has been able to for a while.
Personally, I would try that and other established non-ponzi
technologies first for distributed substitutes.
Not being "permissionless" should not be considered a must have.
I have some more thoughts about this but I really should be sleeping. I
already spent way too much redrafting this email.
next prev parent reply other threads:[~2023-04-08 1:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-25 19:00 [GSoC 23] distributed substitutes, cost of storage Attila Lendvai
2023-03-26 20:06 ` Vijaya Anand
2023-03-26 21:19 ` Attila Lendvai
2023-03-28 20:19 ` Vijaya Anand
2023-03-29 8:45 ` Andreas Enge
2023-03-29 9:26 ` pukkamustard
2023-03-29 9:34 ` pukkamustard
2023-03-30 11:08 ` Maxime Devos
2023-04-04 10:53 ` Attila Lendvai
2023-04-04 18:51 ` Maxime Devos
2023-04-05 7:19 ` Attila Lendvai
2023-04-06 8:13 ` Simon Tournier
2023-04-07 22:45 ` Attila Lendvai
2023-04-08 0:46 ` Csepp [this message]
2023-04-08 16:05 ` Attila Lendvai
2023-04-08 9:30 ` Simon Tournier
2023-04-08 15:53 ` Attila Lendvai
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87355bkwo2.fsf@riseup.net \
--to=raingloom@riseup.net \
--cc=attila@lendvai.name \
--cc=guix-devel@gnu.org \
--cc=maximedevos@telenet.be \
--cc=pukkamustard@posteo.net \
--cc=sunrockers8@gmail.com \
--cc=zimon.toutoune@gmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).