If that's what you got from it, then you're either assuming that a majority of people would do things differently (unlikely), or that Bitcoin being controlled by 12 developers is somehow better (no thanks)...

I already proposed a clear, well-defined solution.
It appears the Counterparty developers are only interested in abusing Bitcoin, though, rather than solving the problems.

Great news! Filter added to block this crap in less than 5 minutes, and 1 line of code.

You're supposed to clone the toppings before they get on the pizza.

warren has provided a Mac OS X build (see main post for download link)

This seems to be a server issue... the actual wiki content is correct.
But yes, I agree fixing it should be a priority.
Unfortunately, nobody working on the server has been able to reproduce it yet, so someone here experiencing the issue may need to stop by #bitcoin-wiki (freenode IRC) to help troubleshoot...

Bitcoin Core version 0.8.7 release candidate 1 (sigs) is now available for download:

• Linux: tar.gz
• Mac OS X: dmg (compiled by warren)
• Windows: installer | zip
• Source: tar.gz | git

This is a maintenance release to fix bugs only.
Users should upgrade to 0.9.0 if possible, and only use 0.8.7 if they encounter trouble with that.
Due to lack of testing, backport stable versions are unlikely to ever reach a final release.

Please report bugs by replying to this forum thread.

How to Upgrade

---

If you are running an older version, shut it down. Wait until it has completely shut down (which might take a few minutes for older versions), uninstall all earlier versions of Bitcoin, then run the installer (on Windows) or just copy over /Applications/Bitcoin-Qt (on Mac) or bitcoind/bitcoin-qt (on Linux).

If you are upgrading from version older than 0.8, the first time you run 0.8.7, your blockchain files will be re-indexed, which will take anywhere from 30 minutes to several hours, depending on the speed of your machine.

Transaction malleability-related fixes

---

This release contains a few fixes for transaction ID (TXID) malleability issues:

• -nospendzeroconfchange command-line option, to avoid spending zero-confirmation change
• IsStandard() transaction rules tightened to prevent relaying and mining of mutated transactions
• Additional information in listtransactions/gettransaction output to report wallet transactions that conflict with each other because they spend the same outputs.
• Bug fixes to the getbalance/listaccounts RPC commands, which would report incorrect balances for double-spent (or mutated) transactions.

0.8.7 Release notes

---

Wallet:

• Bug fixes to correctly compute the balance of wallets containing double-spent (or mutated) transactions
• Don't create empty transactions when reading a corrupted wallet
• Only create signatures with low S values

GUI:

• Fix richtext detection hang issue on very old Qt versions

RPC:

• New notion of 'conflicted' transactions, reported as confirmations: -1
• Reject insanely high fees by default in 'sendrawtransaction'
• Explicitly ensure that wallet is unlocked in `importprivkey`
• Add check for valid keys in `importprivkey`

Command-line options:

• New option: -nospendzeroconfchange to never spend unconfirmed change outputs

Block-chain handling and storage:

• Add a new checkpoint at block 279,000

Protocol and network:

• Added new DNS seed from bitcoinstats.com

Warning

---

There have been frequent reports of users running out of virtual memory on 32-bit systems during the initial sync. Hence it is recommended to use a 64-bit executable if possible. A 64-bit executable for Windows is available for 0.9.

Credits

---

Thanks to everyone who contributed to this release:

• Wladimir J. van der Laan
• Michagogo
• Luke Dashjr
• Philip Kaufmann
• Pieter Wuille
• Gregory Maxwell
• Gavin Andresen
• Peter Todd
• Christian Decker
• Matt Corallo
• b6393ce9-d324-4fe1-996b-acf82dbc3d53
• fanquake
• regergregregerrge

Ignore the trolls. I only edit out false claims and vandalism.
As long as you stick to facts and opinions, and don't try to censor other facts or opinions, your edits are welcome
But the 0.001 BTC thing is just antispam. Post your username and someone can whitelist you directly.

When nwoolls has time to finish it. I believe it's planned for 4.0

Looks fine for me, maybe a temporary glitch?

My understanding is that the patched kernel is only needed to enable OTG and charging at the same time.

EasyMiner is in the Google Play thing.

Actually, you can. You enter the queue based on your estimated earnings for the current round.
If your estimate drops, you can fall below the point where you need to be to get in.

That's your problem, not mine.

No, I'm trying to help Counterparty behave like a good Bitcoin citizen.
Ignore the trolls' misrepresentations of me.

You guys sure love to lie, eh?

Bare multisig is already unusable. Filtering out abuses would be possible without filtering all bare multisig anyway.
P2SH multisig (which actually has potential use) will continue to work in any case.

As I said, we had to workaround this problem.
So the Eligius coinbases today will never get big enough to trigger it.

A Counterparty dev has closed lines of communication.

Even if Counterparty dies, the Freimarket folks will be providing a replacement (if not an upgrade).
I also hold no Counterparty assets myself.
So no, I see no value to Counterparty specifically, just the functionality - which is already being worked on independently.
It's the Counterparty users who will lose out, unfortunately, unless someone steps up to move it forward.