From: Parazyd <parazyd1@gmail•com>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] BitCoin TPB, P2P Currency/Torrent
Date: Wed, 10 Dec 2014 18:18:31 +0100 [thread overview]
Message-ID: <54888067.7090000@gmail.com> (raw)
In-Reply-To: <CAJEcgC71k7vu8b6yz5bn0OTVniFe5QWiNRr06Jn2JS9rJSCRxw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2680 bytes --]
What came to my mind today, is, implementing a blockchain as a tracker.
Nothing to do with Bitcoin as such, but with the blockchain
platform/technology.
I thought about making the blockchain contain all the magnet links and
developing it independently. But that's another story and I think it has
no place in this mailing list.
Also, you do realize that the majority of The Pirate Bay's content is
illegal and shouldn't be discussed here.
You talk about open source, and yet you insist on people doing spam
transactions in order to access certain content? That's a no-no.
On 12/10/2014 06:07 PM, Tiago Docilio Caldeira wrote:
> Dear All,
>
> I've been trying to better understand the bitcoin in the last few
> months, both in the mathematical as the programming point of view. I
> went through part of the documentation, and I got curious to find ways
> to use their data package to store some useful msg.
>
> As most of you know, one of the freedom parts of the internet was
> (temporary) knock out yesterday, the PirateBay, a "service" that was
> built in open source and the freedom to share, so I start trying to
> design an idea to allow us to create the future of p2p transference,
> using bitcoin as a currency and data provider.
>
> If you insert similar message that a torrent has inside of a bitcoin
> portion (for example, in a satochi), you could not only "tip" the
> person who would share the content (eventually, even the producer of
> it), but also, make a public (but anonymous) request of a certain content.
>
> By doing this micro transference, you would receive an entry to a
> content torrent information.
>
> What is your opinion about this? Would someone (with more pratice
> inside bitcoin algorithms) be interested in developing some front end
> with me?
>
> Hope that you like the idea, and share the vision of a open content
> world, with fair return for the people who shares the data.
>
> Best Regards,
>
> Tiago Caldeira
> bitcoin: 1BTdPcpLfpLVouDh32532SqCXibAjXoRqp
>
>
>
> ------------------------------------------------------------------------------
> Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
> from Actuate! Instantly Supercharge Your Business Reports and Dashboards
> with Interactivity, Sharing, Native Excel Exports, App Integration & more
> Get technology previously reserved for billion-dollar corporations, FREE
> http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
>
>
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists•sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
[-- Attachment #2: Type: text/html, Size: 4659 bytes --]
prev parent reply other threads:[~2014-12-10 17:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-10 17:07 Tiago Docilio Caldeira
2014-12-10 17:18 ` Parazyd [this message]
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=54888067.7090000@gmail.com \
--to=parazyd1@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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