Search Mailing List Archives


Limit search to: Subject & Body Subject Author
Sort by: Reverse Sort
Limit to: All This Week Last Week This Month Last Month
Select Date Range     through    

[liberationtech] Looking for Feedback | Ombuds

Nick Skelsey nskelsey at gmail.com
Tue Aug 25 08:40:20 PDT 2015


As of now, we are using Bitcoin's network to distribute all of the data, so
entire posts are stored in the block chain. But we don't have a good way to
distribute images and video, while still embedding the hashes.

If you are worried about the amount of data the block chain can support, 25
million tweet sized messages is around 6 GB of raw storage on the network.
For 100,000 people that is 250 messages each, which is more than enough to
serve its purpose for the foreseeable future.

On Tue, Aug 25, 2015 at 11:22 AM, Martin Becze <mjbecze at gmail.com> wrote:

> are you going to store hashes of posts in the blockchain or entire posts?
> also what blockchain are you using?
>
> On Tue, Aug 25, 2015 at 3:01 PM, Nick Skelsey <nskelsey at gmail.com> wrote:
>
>> I am bumping this post just once.
>>
>> I was hoping to see if anybody had any "hold on" kind of thoughts before
>> we continue on our merry way building this system out. We are working to
>> create a free public record for the Internet via user submitted statements.
>> Any bits of wisdom you have helps!
>>
>>
>> On Wed, Aug 19, 2015 at 2:41 PM, Nick Skelsey <nskelsey at gmail.com> wrote:
>>
>>> Hi All,
>>>
>>> A friend and I have been working on (yet another) anti-censorship tool
>>> and we are getting ready to release it. The tool is kind of like a BBS, but
>>> the interesting thing about it is that all public statements made through
>>> it are stored in a block chain. This is in contrast to a traditional
>>> microblogging service where the site's operator has control over a user's
>>> content. In our case, we use Bitcoin's block chain.
>>>
>>> I am soliciting questions, comments, and concerns about the design
>>> before we try to get anyone to use the tool seriously. You can read more
>>> about the design, how we plan to scale it, and some attacks we foresee in
>>> our paper [1]. Feel free to checkout the software [2] and the rest of our
>>> material online [3]. None of it is really finished, but we welcome all
>>> criticism.
>>>
>>>   Nick
>>>
>>> [1] https://getombuds.org/research/
>>> [2] https://github.com/soapboxsys/OmbudsCore
>>> [3] https://relay.getombuds.org
>>>
>>
>>
>> --
>> Liberationtech is public & archives are searchable on Google. Violations
>> of list guidelines will get you moderated:
>> https://mailman.stanford.edu/mailman/listinfo/liberationtech.
>> Unsubscribe, change to digest, or change password by emailing moderator at
>> companys at stanford.edu.
>>
>
>
> --
> Liberationtech is public & archives are searchable on Google. Violations
> of list guidelines will get you moderated:
> https://mailman.stanford.edu/mailman/listinfo/liberationtech.
> Unsubscribe, change to digest, or change password by emailing moderator at
> companys at stanford.edu.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.stanford.edu/pipermail/liberationtech/attachments/20150825/894097ce/attachment.html>


More information about the liberationtech mailing list