BitWeav just uses a public-private keypair, nothing more, for
authentication. This is the most versatile thing we have for
authentication and signing messages. The same keys can be used for
signing emails with GPG, Retroshare, etc.
I agree, UI is important over everything else. BitWeav is composed of
two projects: a backend daemon that does all the work, and a frontend
graphical client that connects to the daemon. The graphical client is a
client-side desktop app.
Le 29/09/13 05:18, Sean Lynch a écrit :
If it can be easily integrated into existing publishing
infrastructure, I'm all for it. It would be really nice to see
something more usable and decentralized than OpenID.
Would this be something that could be implemented as a browser
extension or a Greasemonkey script? UI is really the most important
thing of all; it's why centralized solutions tend to win out.
On Sep 27, 2013 8:20 AM, "Liam Edwards-Playne"
<[email protected] <mailto:[email protected]>> wrote:
The fact that I have no portable identity with which to comment
on or post arbitrary content around the web is very annoying.
Good news Sean, I think I solved your problem and uncovered
something great for BitWeav.
Tonight it was asked whether BitWeav supported OStatus. So I got
to looking through all the existing specs and stuff, and realised
how your dream of commenting with one single identity across the
web could be achieved in conjunction with BitWeav's goals.
Right now we have feeds, which are pretty much the basis of
OStatus. Atom feeds/ActivityStreams are used for providing an open
format to show a series of posts. Every website does this. Now
large websites which publish content quite often use PuSH
(PubSubHubbub) to push new posts to their subscribers (a more
efficient method of distribution than pulling really often). Now
this is cool, but how do we push content like comments back to the
website? Well that's where Salmon comes in, another open protocol
to do just that.
So visualise this. You have a feed, with a list of posts. The
posts are associated with a PuSH hub, and each post has a Salmon
endpoint for receiving comments. Thus you can perform the normal
functions of a content website, like reading and commenting, but
in using an open format. When you are offline for a while, you can
just GET the Atom feed as usual to get the newest posts.
I will use the public key as the decentralised identity. Lastly
I'm adding an extra protocol to complement PuSH and Salmon: the
BitWeav protocol. Basically it will be a P2P overlay constructed
using PolderCast (detailed in the whitepaper) that will allow for
the decentralised publish-subscribe of messages on topics, threads
and profiles.
Finally, all BitWeav nodes will host their own Atom feeds with
PuSH, Salmon and BitWeav. The hybrid of distributed and
peer-to-peer paradigms in serving content will do well I think.
What do we think? I'll draw up a proper diagram later on the website.
Le 25/09/13 08:16, Sean Lynch a écrit :
I don't think Bitcoin's SHA2-256 + RIPEMD-160 usage is based on
sound crypto. It's not terrible but it's also a little bit silly
since a collision in SHA2-256 will be a collision in the pair,
which means all you're doing is shortening the hash while
avoiding the length extension attack. There are also potential
weaknesses in the pair that may not exist in either one due to
the fact that the pairing has not been well studied. You could
accomplish the same end with less CPU and less code by using a
truncated SHA-512 hash.
Otherwise, I tend to agree with your goals and approach, though I
think it may be more impactful to simply bring the decentralized
identity aspect of it to the web. The fact that I have no
portable identity with which to comment on or post arbitrary
content around the web is very annoying. At best, the current
system could be described as federated, but even that's not
entirely true since few sites actually support OpenID and fewer
users know what their OpenID URL is.
On Mon, Sep 23, 2013 at 9:48 PM, Liam Edwards-Playne
<[email protected] <mailto:[email protected]>> wrote:
I've been working on a new open micropublishing network
that's entirely peer-to-peer, relying on a publish-subscribe
overlay to facilitate scalable distribution of messages on
hashtags, profiles and threads.
You can peruse its design in this document:
http://bitweav.org/whitepaper.pdf
Its main features:
- first of its kind to support publish/subscribe to topics
(profiles, hashtags, threads)
- doesn't use rendez-vous nodes for topics (meaning only
nodes who are subscribed to a topic will help distribute
messages on it)
- message threading and replies. multilingual support.
- more scalable approach to message dissemination using
rings, rather than gossip-based flooding (see ch. 7 of
whitepaper)
I'd appreciate any constructive criticism / discussion and if
anyone would like to help I would greatly appreciate it. I'm
currently developing the frontend graphical client,
afterwhich I will progress to implementing the backend daemon.
Cheers,
Liam Edwards-Playne.
_______________________________________________
p2p-hackers mailing list
[email protected] <mailto:[email protected]>
http://lists.zooko.com/mailman/listinfo/p2p-hackers
_______________________________________________
p2p-hackers mailing list
[email protected] <mailto:[email protected]>
http://lists.zooko.com/mailman/listinfo/p2p-hackers
_______________________________________________
p2p-hackers mailing list
[email protected] <mailto:[email protected]>
http://lists.zooko.com/mailman/listinfo/p2p-hackers
_______________________________________________
p2p-hackers mailing list
[email protected]
http://lists.zooko.com/mailman/listinfo/p2p-hackers
_______________________________________________
p2p-hackers mailing list
[email protected]
http://lists.zooko.com/mailman/listinfo/p2p-hackers
