Bitcoin Forum
May 24, 2024, 02:17:55 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: « 1 ... 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 [82]
1621  Bitcoin / Project Development / Re: Donating to the Freenet Project on: November 12, 2010, 02:29:51 AM
Join FMS and setup a Bitcoin forum! Tongue

There already is one and there's been discussion about bitcoin in it in the past. One of the freenet developers (Toad) said he'd be willing to accept bitcoin donations privately on behalf of the project if the value was greater than $100 USD and people can contact him directly about it.
1622  Economy / Gambling / Re: Bitcoin Poker Room on: October 27, 2010, 10:51:23 PM
I totally agree, but I am a bit concerned about someones trying to keep privacy. So i'd like to hear opinions before I will publish list of nicknames =)
I have no problem with nicknames being shown.

One small request. I notice that if I have an email associated with my account it shows my gravatar. Is it possible to have an option to disable this?
1623  Bitcoin / Project Development / Re: Chrome Bitcoin Extension Bounty(300 BTC pledged) on: October 23, 2010, 10:28:00 AM
This is a dirty hack, although this does not seem as it. It will ruin the caching of images, at least.

I suggest use a new tag:
...
<bitcoin amount="100" address="17v4AR81oFJLAG8jHDKJKNKjSvY2QAmf1V"/>
HTML 5 defines 'data attributes' for this use:

http://www.whatwg.org/specs/web-apps/current-work/multipage/elements.html#embedding-custom-non-visible-data-with-the-data-*-attributes

So this could be:

<img src='foo.png' data-amount="100" data-address="17v4AR81oFJLAG8jHDKJKNKjSvY2QAmf1V">

This has the advantage of validating with HTML 5 validators.
1624  Bitcoin / Bitcoin Discussion / Re: Message Free Software projects to add Bitcoin Donate buttons on: October 23, 2010, 10:14:58 AM
All I got was a polite decline.
I don't think their decline is so polite anymore Smiley
1625  Bitcoin / Development & Technical Discussion / Re: Pooled/Remote Mining on: October 17, 2010, 10:58:12 PM
Is there any way for the server to see about how many k/hashs the pool is generating combined?

It would be nice if the standard 'getinfo' returned the combined k/hashs in some way. The clients seem to get the information. It periodically prints it to the console.
1626  Economy / Marketplace / Re: BiddingPond.com discussion on: October 17, 2010, 12:18:17 PM
Actually mine ships globally (something did not work properly when I was activating the auction) . I tried to edit it and it did not work neither.
But overall you are right, international shipping is key , especially with the current low user base.
Does it default to USA shipping? That might be why I see most options not having global shipping.
1627  Economy / Marketplace / Re: BiddingPond.com discussion on: October 17, 2010, 11:03:15 AM
Biddingpond is not widely used enough and hence "quite useless". Unfortunately.

One of the problems is that most auctions will not ship outside the USA, including your one. That cuts down on a lot of potential customers willing to bid.
1628  Bitcoin / Development & Technical Discussion / Re: Pooled/Remote Mining on: October 17, 2010, 10:25:26 AM
Thank you, puddinpop! Someone succeeded to generate a block?

So far there are eight clients connected to my server. No blocks generated yet but I'll be interested to see what happens when a block does finally get generated.
1629  Bitcoin / Development & Technical Discussion / Re: [PATCH] monitoraddress/blocks on: October 15, 2010, 10:35:14 AM
Does any data get passed to the POST request?  From my observations it appear no data is passed along.

From my tests, the data is passed as the body of the POST request. For example, the following Perl code using the Mojolicious web framework will extract data from the POST:

Code:
my @blocks;

any '/receive' => sub {
  my $self = shift;
  my $body = $self->req->body;
  my $json = Mojo::JSON->new;
  my $data = $json->decode($body);
  my $params = $json->{params};
  ...do something with $params...
  $self->render(json => {result => undef, error => undef, id => undef });
};

Here the $params variable contains the decoded JSON data equivalent to what 'getblock' returns if this was posted as a result of 'monitorblocks'. It will return the equivalent of what 'gettransaction' returns if it was posted as a result of 'monitoraddresses'. I wasn't sure what it expected as a result so I just return an empty JSON method result.
1630  Economy / Marketplace / Re: paypal dropped mtgox on: October 11, 2010, 08:58:12 AM
It doesn't show anything to me, are you getting the site? I just get a question about my country in a form that doesn't work.

The form didn't work for me but my browser (Firefox 3.6) popped up to say that the site wanted to request my location via the HTML geolocation API so I used that. That took me to the next page requesting my email. Then I get an email with a link that takes me to the site where you can buy coins. It's a complex process and I'm guessing will put a lot of people off using it.
1631  Economy / Marketplace / Re: paypal dropped mtgox on: October 11, 2010, 05:07:01 AM
I get my paypal money from doing tarot card readings on the phone, I don't really have the option of receiving my pament in any other form.  If I can't find an easy easy way to turn paypal into bitcoin I may have to start trying to encourage people to auction some of it on e-bay.  (hopefully with a buy it now that is not too far from the going rate)
buybitcoins.com still shows as accepting paypal payments for bitcoin purchasing.
1632  Bitcoin / Bitcoin Discussion / Re: Pros and cons of using new Bitcoin addresses for each transaction? on: October 09, 2010, 11:36:18 AM
It would be nice feature to physically remove entries from it if I'm pretty sure no one will send coins to that particular address. For example, if would be useful for shops which create one-time addresses to recieve payments.

The problem with deleting the address is, if the address was made public, someone can still send money to it. If you delete the address and bitcoins are later sent to it then those bitcoins cannot be recovered (as I understand it).
1633  Bitcoin / Project Development / Re: Next Hacker Charity Target on: October 09, 2010, 07:39:50 AM
How about Freenet?

http://freenetproject.org/

The topic of accepting freenet donations was brought up on one of the Freenet message boards (hosted on Freenet):

Someone asked if it was possible to donate to Freenet development via bitcoins. The response from a freenet developer was that 'putting it on the website would probably be pointless; nobody EVER uses anything but paypal'. However they did say they were willing to accept bitcoin donations for the project privately if they were for more than the equivalent of $100 US (presumably to reduce transaction fees when converting). If they knew there was interest in donating from bitcoin users they might be more receptive to making an option publicly available.
1634  Bitcoin / Development & Technical Discussion / Re: [PATCH] monitoraddress/blocks on: October 06, 2010, 11:45:15 AM
With the existing patch (and the git repository) if you call monitoraddress with a monitor value of 'false' (to remove a monitor) but pass a URL that is not being monitored then the bitcoin daemon process will exit. Possibly it's indexing into the map of monitor URL's, not finding it and throwing an exception.
1635  Bitcoin / Development & Technical Discussion / Re: [PATCH] monitoraddress/blocks on: October 06, 2010, 04:50:13 AM
I do not understand this step.  Did my previous steps update Bitcoin svn code to revision 161?  I do not understand "rebasing."
Poor wording on my part. At that step (after you've done the 'git rebase or git merge') you have a repository equivalent to svn revision 161 with the monitor changes applied. The 'git diff' command that follows produces a diff of only the monitor changes.
1636  Bitcoin / Development & Technical Discussion / Re: [PATCH] monitoraddress/blocks on: October 06, 2010, 04:30:58 AM
Here's another approach to automatically generate a patch (or an update repository). Clone Gavin's repository and create a branch for your own changes based on origin/monitorreceived. Then rebase your branch on top of origin/svn. Git will then automagically apply the changes in the monitorreceived branch on top of the new svn changes. You can then either work on your new branch or generate a diff to get monitorreceived's changes only. Here's the steps:

git clone git://github.com/gavinandresen/bitcoin-git.git
cd bitcoin-git
git checkout -b mybranch origin/monitorreceived
git rebase origin/svn
...now you can build the new code updated to svn...

To get a diff:

git diff -U8 origin/svn >myfile.patch

I just tested and the rebase occurs without requiring use intervention.

You also merge if you prefer instead of rebasing:

git clone git://github.com/gavinandresen/bitcoin-git.git
cd bitcoin-git
git checkout -b mybranch origin/monitorreceived
git merge origin/svn
1637  Bitcoin / Bitcoin Technical Support / Re: Remote RPC access on: September 28, 2010, 12:51:22 AM
I read the wiki and it says the interface only accepts requests from 127.0.0.1. Is this still the case? Is there a setting to override this?

This is still the case and I don't believe there is a setting to override it. It's hardcoded in the source. Instead of writing a 'proxy' app you can use SSH to tunnel. For example, if your bitcoin instance is running on 'example.com' and that machine is running an ssh server, you can tunnel to it from another machine with:

ssh -N example.com -L  9481:localhost:9481

Now you can use the RPC interface on your local machine to port 9481 and it will be tunnelled over an encrypted SSH session to the machine running the bitcoin RPC server.

You want to encrypt the connection because the JSON-RPC password is sent in clear text (it's actually base 64 encoded but basically it's the equivalent of clear text).
Pages: « 1 ... 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 [82]
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!