And it is easy to give god credit when things are going swell.

It's called confirmation bias.

But take a look around, things go badly for the "godly" and things go well for the "godly".
Things go poorly for the "un-godly" and things go swell for the "un-godly"

Look at it objectively - don't use the good times as "evidence" of his providence and then come up with pat answers when they take a turn to shit.
That's the fallacy of confirmation bias, making excuses for the evidence to fit your pre-formed conclusion.

But back to what he was saying - where was God when he wasn't employed?

Where was the damn church? That at least is real. Were they willing to help him, or only if he got on knees and prayed where they could see him to affirm their own faith?

The church is full of people who only care about themselves, and use God as an excuse for their selfishness.

A clear modern example - Wolves on Isle Royale in Lake Superior.

This Island use to lack wolves but in 1949 a pair of wolves made it to the island crossing an ice bridge. The Island then had a wolf population starting from a single pair.

Then in 1997 another wolf, a male, crossed an ice bridge - and because he was fresh genetic material and not inbred, he and his offspring quickly dominated and now every wolf on the island is his decendant.

For the island, he currently is the source of mitochondrial Y - yet genes from the first male wolf are still present.

On a much larger scale the same is true for our species, we have numerous genes that do not come from our Mitochondrial X and Mitochondrial Y ancestors.

Hello all -

I've put together some custom package repositories for RHEL/CentOS 7 - only x86_64 available

http://awel.domblogger.net/7/php/

That has php 5.6.0 - which isn't something I would suggest putting on a server (I would but I like pain) as it is fresh and does break some webapps, but if you develop php webapps, you should probably have 5.6.x on a dev server.

http://awel.domblogger.net/7/media/

That has FFmpeg and dependencies, I had a need for an FFmpeg build capable of eating almost anything and spitting out HTML5 formats - I think that one does it.

http://awel.domblogger.net/7/gstreamer/

That depends upon the media repository for dependencies. The GStreamer in RHEL/CentOS 7 is old, too old to decode VP9 - so that GStreamer replaces the stock GStreamer with current.
It also provides many plugins that RHEL/CentOS + EPEL do not.

http://awel.domblogger.net/7/misc/

Misc. crap - basically rebuilds of Fedora 20 src.rpms that for whatever reason are not in EPEL

http://awel.domblogger.net/7/crypto/

My crypto-currency repo

Right now the only real thing of interest there is namecoin - the bitcoin RPMs are just rebuild of http://www.ringingliberty.com/bitcoin/ so just use his if bitcoin is all you are interested in.

The namecoin right now is only daemon (that's all I ever use anyway) but I will build the qt in a week or so.
And I will then add quarkcoin and then start work on getting armory packaged.

-=-

Anyway - for CentOS/RHEL 7 users - I thought those might be of interest to some of you.

CentOS 7 really is a decent Desktop OS once you replace the Gnome 3 shit with Mate and update the GStreamer.

All of the repos use EPEL for dependencies, but no other external repos are needed.
All packages are built with mock and signed.

It's definitely working now and local. Thank you.

Thank you!

Turns out I was blocking 8883 and 6667 on the machine that is up to date. Fixed that and the incoming rate shot up but I still don't see the other host in getpeerinfo so I'm not sure if maybe I got lucky and it found another peer very close but outside my lan.

Well it's not showing up in getpeerinfo so i don't know...

Tried this in the debug console -

addnode 192.168.0.103 add

Is that correct?

Guess I'll quickly find out...

Setting up bitcoin-qt on a new laptop.

Need to tell it to use my desktop as a block source so it goes faster.

There use to be a ~/.bitcoin/bitcoin.conf file where I could do that, but I don't see that file.

What is the current method for telling it to use the "caught up" client I have running on another machine on my gigabit wired LAN ??

Looking via google seems to all point to old documentation for 0.8 client - which used ~/.bitcoin/bitcoin.conf

Then the experts you know are morons.

CIA?

No.

If there is government involvement in the beginning of bitcoin, it was more likely NSA.

I'm less and less convinced that Satoshi was a government codename and am more and more convinced that Satoshi was a single person.

QFT

Yeah, and it doesn't matter if that bitcoin is used with a .com or .cc or .io or ...

Have fun with your squatting.

With respect to validating the address, hopefully there is an SSL page available so you know there probably wasn't a MITM between wikipedia and your browser.

Using a fresh address for each donation I believe is the right thing to do.

Static addresses on things like forum posts are fine, but when you can provide a fresh address it avoids issues where third parties analyze donation rates and sizes.

Any service or any service that acts as a store of value?

I prefer the top one. Even though my avatar has the bottom one.

Thank you!

I think where shorter matters is with mobile clients.

No mobile platform is really secure. You don't want to keep a lot in a mobile wallet, it is better to load your mobile wallet when you are going out with intent to spend but otherwise (just like a leather wallet) don't keep a lot in it. Unless you are only going to spend in one place, or you transfer to it using lots of outputs, confirmation time impacts when your change address from Merchant A is available to buy something from Merchant B.

It also matters for things like phonesex, but that's a different topic.

While increased orphans is a problem, if a transaction is in one block it is likely to be in the competing block too.

What short block times need to do is require X confirms before the input is spendable.

What is the advantage over a deterministic paper wallet?

My understanding is you can make a deterministic paper wallet with Armory where you can continue to create fresh addresses to send to w/o needing the private key in your client.