alfiejohn_

The Australian equivalent (DSD) did a challenge like this last month. Same deal - x86 assembly to decrypt a message and reveal a secret URL. They too had no tracking.

Here's the Australian equivalent:

  https://plus.google.com/103685227755333384561/posts/VasNhJpVFA4

Although not as tough as GCHQs

Hey Alan :)

What's the minimum requirements of setting up a shell Delaware LLC? Surely citizenship wouldn't be one of them.

Clicking on a couple of posts, or going to the verification link in my sign up email, I get:

  "System error. Please re-try your action. If you continue to get this error, please contact the Administrator."

Edit: it looks like it doesn't like Opera.

Surely this is just a honeypot?

I've found that my local Perl Mongers was a great place to meet like minded people - http://www.pm.org/ for your closest one :)

It's not just newspapers who push PR pieces. This also applies to the web (Techcrunch and Wired comes to mind).

You are obviously not married

Bridge to Engine Room: We need more DIVs

That isn't a ring topology or based on a timer?

The video can be found at:

  http://www.youtube.com/watch?v=lk-2XE00fqY

And the Q&A after the talk is at:

  http://www.youtube.com/watch?v=oDcsM8n72OU

Funny that they both managed to be close to 15 minutes on the dot and I didn't use any timers :)

If you don't understand proofs, don't read any more maths books until you've read "Prove It":

  http://www.amazon.com/How-Prove-Structured-Daniel-Velleman/dp/0521675995

Even though you'll learn to read and write rigorous proofs with this book, it's requirements are high school maths and doesn't assume anything.

You're kind of in an active-passive multi-master setup which is find for now but as replication queries increase between the two nodes, you might start to see load issues. You're going to have to drop in a third machine and a decision is going to have to be made on how to replicate your data.

The two must have books for MySQL admin and discuss MySQL's built in replication, what problems you'll encounter, how to tune etc.

  - High Performance MySQL (Schwartz et al)
  - MySQL High Availability (Bell et al)

I think using MySQL::Replication can be applied on top of what's in these books, but not using their particular setups.

There's nothing stopping you from having standby relays, active relays etc. You are free to create a topology of your choosing with minimal restrictions.

Ok. It's now on GitHub if anyone is interesting in following:

https://github.com/alfie/MySQL--Replication

I think spydum's comment is what you're looking for.

These are things that can and do happen, and you have to plan for it. Designing your applications and infrastructure with eventual consistency in mind can do wonders for both performance and redundancy.

Having a single master is sometimes not viable in some situations. But yes, eventual consistency can be both a blessing and a curse.

But if you can design your system to take this into account, it's pretty easy to scale out and everything Just Works(tm).

I can't remember specifically, but I think we evaluated Tungsten Replicator and at the time it didn't do multi-master replication.

Toby will be uploading the talk to Vimeo when he weekly upload limit gets reset.

We talked a bit about how race conditions are a part of life with multi-master replication, and the ways to best avoid it.

When you know your data, you know what you can get away with.

A talk I gave at Melbourne Perl Mongers last night...

"Pre-release" code can be found at:

http://h4c.kr/mysql-replication-0.0.0.tar.gz

It will be up on GitHub and CPAN hopefully this weekend.

It's a shame that the first comment was for a typo. Can't people get over these things?