you're holding over 4b IFC?

Go read what he wrote about this coin on PPCoin forums.

He's kind of being a "D-bag" about it.

I had some harsh words for him the other day, and he has since helped people to understand what the coin is doing (a little) instead of just being smug and repeating over and over "go read my paper" when he knows 999/1000 people can't understand it.

He stated clearly in his own forums that this is a pump and dump coin, meant to fragment the POW cryptocurrency market and after release he will be back to "working on" PPCoin.

I went in GitHub an hour ago and the only work he has done for this coins since release is to accept some GUI updates and string replacements that SOMEONE ELSE did for him.

He couldn't be bothered to grep and replace bitcoin in the source, that's how much he puts into this.

Now he comes out and tells people to stop trying to fix it - who's the D-Bag?

People like to say this.  But really mining is not part of ripple. XRP are not meant to be coins, they are wrappers or, as mah87 so nicely put it, they are like stamps.

So, in effect this is like complaining that the post office pre-mined all the stamps.

XRP are tools for tracing transactions in a block-chain like ledger. They own the ledger, they're going to support the server infrastructure to make it available, and they're selling the "stamps" that allow people to send "packages" through their system.

What that has become twisted into by the crazies around here, well that's something else.

yes

I often think there's not enough LMGTFY on this forum - glad to see another fan 

WTF now you're kind and reasonable (and correct)?

nice to meet you!

It's fungible we see people can put value and trade it.  But like a stamp it will have more value in what you can do with it than in it's own price.  Wow that is one of the best explanations I've seen.

Thanks for that 

 

Some people finally starting to realize XRP isn't currency?

 

what happened at cryptsy is changing hands from miners to traders.

once enough traders hold it we will see if it comes to life.

Right now there are more infinitecoins than anything except zimbabwe dollars (which is dead I think) and XRP (which isn't really a crypto )

once the coins are more distributed without so many miners holding 100 to 500m things will get a little more active.

Maybe not a lot though, we'll see  

Sheer stupidity (and coding late) on my part.

The FLO version has some different code form the version in GIT and when I made the last security updates last night and moved the updated API file to FLO i neglected to fix the include path.

Which also means I forgot to test it, and the sample links in the release post have been bad all day too.

It happened to be a day where I was AFK all day, too.

My sincerest apologies for frustrating you and also your link above is now functional.

I've got my hands pretty full, I'm not looking to get involved in something like that at this time.

It's not a bad idea, but it needs a dedicated and capable administrator to make it work. Preferably one with connections into your eventual target audience, and a lot of time to dedicate to the project.

I'm just a troll

There is no need to wallet mine this it is a scrypt coin.

Wait, didn't that happen?

Then when it didn't work, I seem to recall him shoring them up a bit with a little purchase of stock.

Totally off topic but that was a pretty ironic example.

Thanks for reporting this.

I suppose I'll have to run through every command and see which ones have parameters but will respond to a 0 parameter request.

That's work for tomorrow.  The fix for listreceivedbyaddress is committed to the repo.

Difficulty aside (this is not trivial) there would be ongoing costs associated with the system.

There are some sms notification services that could eat a lot of time off of your development but would add a great deal to the cost of the service.

It would take a pretty ballsy developer with some deep pockets to try and release something like this, an entire new crypto ecosystem.

New wallets, a new block chain, new miners, new pools, everything.  Right down to the p2p network itself.

The more I think about it the hairier it gets. All to shed off any last pretense of anonymity.

I don't see it happening.

New update for the FLO Block Crawler today an API upgrade.

Documentation:
https://github.com/CallMeJake/BlockCrawler/blob/master/bc_api.php

Endpoint:
http://lotto.coinworld.us/FLO/bc/bc_api.php?request=getinfo

This new API has considerably more functionality than the one I made the other day. I'll leave the original FLO only API up in case anyone has already integrated with it.

The Block Crawler project in GitHub has now been updated with the new API as well.

And congrats on making the exchange!

Who loves ya, baby?

BIG update for Block Crawler today.

I've added a very flexible API.  This one is the key to your status panels and basic integration with existing web services, chat bots, etcetera. Documentation for using the API and adding or removing security precautions is in the file "bc_api.php".

Installation is a matter of dropping the file in the directory with your existing bc_daemon.php file.  Done. Sample URLS with valid responses, errors, and security blocks are in the release thread.

Block Crawler Release Thread: https://bitcointalk.org/index.php?topic=244041.msg2687426#msg2687426

Block Crawler Repository: https://github.com/CallMeJake/BlockCrawler

Please let me know if you have any questions or find a problem.  As ever, your compliments and donations are appreciated!

OK-

I have too many irons in the fire, this update has been delayed however it is here now and better than originally planned.

I have added the API for Block Crawler to the repository.  Unlike my original work for FLO, this is a pass-through API which takes standard JSON-RPC method requests directly. In most cases the information is returned in a JSON wrapper however int he case of calls which return a single value from the daemon, the API returns a single value as well.

This means that you get a JSON object if you request "getinfo" but you just get an integer response if you request "getnetworkhashps".

This means that this API will also return previously unknown methods such as "getprimespersec".

It also includes several blocks, as the pass-through would allow malicious access to some commands such as "stop"

I also blocked balance requests, peer detail requests, transaction lists, and account lists. Duplicating these blocks in the code should be very simple if you wish to limit the API functionality further for your installation.

Requests which require one or more parameters are unsupported, the method will be allowed but the daemon will simple return an error message which the API will return to the user.

Some sample URLS for the FLO endpoint:

        http://lotto.coinworld.us/FLO/bc/bc_api.php?request=getinfo

        http://lotto.coinworld.us/FLO/bc/bc_api.php?request=getnetworkhashps
 
       http://lotto.coinworld.us/FLO/bc/bc_api.php?request=getconnectioncount

Unsupported method (requires parameter):

        http://lotto.coinworld.us/FLO/bc/bc_api.php?request=sendtoaddress+1234faerAFf314f4f3c34df314DD

Blocked methods:

       http://lotto.coinworld.us/FLO/bc/bc_api.php?request=stop

       http://lotto.coinworld.us/FLO/bc/bc_api.php?request=getbalance

This should allow you to create status panels, feed other web services, and generally make casual requests to the daemon behind your Block Crawler.

Enjoy!

Absolutely!

MPMrWEKCRfq1n971RSS9mR8eHYz3CuhWPc

thanks for the promo