Has nobody else noticed that Savegox does not risk any of their own money?  Their proposal instead would risk $10M of the creditor's cash.  They take 83.5% equity at zero risk to themselves.  That is quite inappropriate.

There is no mention of Sunlot risking any of its own money in this deal.  They are taking 83.5% equity in the new company in exchange for $10M of the creditors money, at no risk to itself?  How is this an appropriate deal for the creditors?

Reviewers are translators who are promoted to a higher level in a language.  Their role is very important and they must be certain to not be wrong because anything Reviewed cannot be changed by other translators.

Choosing a Reviewer or Maintainer per language isn't easy because a lot of trust is needed.  A bad Reviewer can screw up the process for everyone else.

You do not need to be a developer to help in the improvement of Bitcoin.

http://sourceforge.net/p/bitcoin/mailman/message/32255092/
Bitcoin Core 0.9.2 feature freeze is May 13th, 2014.  Now is the time for native non-English speakers to join Transifex to clean up the translations in all languages.  This is important for more than just Bitcoin because Litecoin will use these same translations.

What should volunteer translators do?
https://bitcointalk.org/index.php?topic=571414
Try the nightly builds of Bitcoin Core as it heads toward 0.9.2.  Not recommended for your production wallet.

https://www.transifex.com/projects/p/bitcoin/
Join Transifex as a translator and add your account to your language.

https://groups.google.com/forum/#!forum/bitcoin-translators
Join the Translator mailing list to receive announcements when translations are needed Bitcoin.  You will also receive notifications if other Bitcoin Project things in Transifex need translations (likely bitcoin.org).

http://sourceforge.net/p/bitcoin/mailman/message/32255092/
Please the announcement of the Development Roadmap for Bitcoin Core 0.9.2.  Feature Freeze is May 13th.  Translators should read the instructions here to learn how to help.

http://www.coindesk.com/investor-group-optimistic-fight-mt-gox-liquidation/
This was in the media again today with more details of the proposed takeover.

It seems clear that the only way creditors will receive more than the 200k BTC is if the company is generating revenue again or if the assets are sold.  Their considerably large customer database of already AML verified users is worth something to another company if they have the banking licenses to use it effectively.

However the way this investor group proposes to restart Gox seems like a terrible deal for the creditors.


Seriously?  The new investors are taking ownership stake and risking none of their own skin entirely at the expense of the creditors?  That is quite absurd.  Do people know what they are signing up for?

This might make sense if the new investors are putting in new money to the tune of $10's of millions.  The currently proposed deal is only upside, which is hardly appropriate.

http://custom.simplemachines.org/mods/?mod=936
It would be simple to support embedded Youtube tags in the new forum.  The question though is if this is desired.  Are there any safety or annoyance mitigation reasons not to have it?

It could also be in a group of tags that are disallowed for certain users like Newbies.

BBCode Examples

Glow

Does anyone ever use this tag?  Never seen it before.  It is in the editor UI.

---

Seemingly Broken BBCode (in the SMF Editor UI)

Seems broken, and for security reasons we probably don't want this to work.

Shadow

The UI has the shadow tag, which doesn't seem to do anything.

Are they deterministic and easy to reproduce from a tag?

Could folks please test UPNP with the nightly builds on both Linux and Windows?  It seems to inconsistently work for me depending on which wireless router is used.  Please report Windows or Linux and the model of your wireless router.

Translators: The latest nightly build v0.9.99.0-20140417-2f3308f contains the first translation update from Transifex in many weeks.  This would be a good opportunity to check the translations of Bitcoin Core running in your native language.  If you see strings are missing or incorrect, anyone can join Bitcoin localization at Transifex.

The forum currently allows new users to send PM spam.  This is especially bad because it sends outgoing e-mail from the server which results in bitcointalk.org being classified as an e-mail spammer.

Even if new users were disallowed from sending PM's, or at least PM's that result in e-mail, that still would not protect the forum from being listed as an e-mail spammer.  Compromised old accounts could send spam PM and get the server in trouble.

One solution that would substantially help this is spam filtering of outgoing PM e-mail.  Perhaps the outgoing message can be piped through spamassassin.  Spam score and particular rules like URIBL's can be used to flag an account and possibly stop outgoing mail that could get the server in trouble.

Electrum for Litecoin is coming very soon (currently usable in beta testing).  It supports importing a private key and scanning for unspent coins.  It does so without the need for a local blockchain.

Hi folks,

The Bitcoin Core developers have a desire to do a mostly bug-fix, cleanup and translation update release in v0.9.2 a few weeks from now.  You do not need to be a developer to help!  With these unofficial nightly builds, power users can more easily aid in testing of the master branch which will help to find bugs and polish things up faster.  Additionally translators can more easily run the latest code and see what strings need to be translated as we rapidly approach the next stable release.

WARNING: Nightly builds are potentially dangerous.  These builds are untested and may contain bugs.  While every effort is taken to maintain security of the build and web server, we are not responsible for anything that goes wrong.  It is up to the user to protect their own data, and to the community to use Gitian to independently make matching builds and to point out if something has gone horribly wrong.

Unofficial Nightly Builds
http://nightly.bitcoin.it
Builds will appear here roughly once a day.  Sometimes there will be no new build if nothing changed in master.
(This has nothing to do with the wiki.  They just provided a convenient subdomain and Cloudflare protection of the download server.)

Source and Binary Reproducibility
https://github.com/nightlybitcoin/bitcoin/branches
https://github.com/nightlybitcoin/bitcoin/releases
https://github.com/nightlybitcoin/gitian.sigs
All binary builds are byte-for-byte reproducible by using Gitian to build a particular tag in git.  For example, the 0.9.99.0-20140415-74dd52a branch denotes in a custom version tag v0.9.99.0-20140415-74dd52a with build date of 20140415 and the 74dd52a commit from master.  Sometimes the nightly build will contain PR's.  This particular tag includes PR 4042 and PR 4049 that are both important for the next release.

Bug Reporting
https://github.com/bitcoin/bitcoin/issues
If you run into any problem with these builds please search the Bitcoin Github issues to find if it is already a known problem.  If your issue is not yet reported, file a new ticket and explain the problem.  You should include the exact name of the build you are using (i.e. v0.9.99.0-20140415-74dd52a) so the developers know exactly what you are talking about.  It would be helpful if you include a link to the branch used to build it which can be obtained from the README-SOURCE within the Linux tarball or Windows download directory.  For example, a typical branch will look something like this.  Include that link in your issue ticket and it will save time of the developers.

TODO's ... any Volunteers?
* There are many things that can be done to improve these automated nightly builds.  One of the most important has to do with security of the binaries.  Since each build is byte-for-byte reproducible from each git tag with Gitian, it should be possible for two or more independent builders to validate the results in an automated fashion.  Anyone interested in doing this?

Builder Changelog
2014-05-21: MacOS X builds added.
2014-05-13: Separate builds for master and 0.9.2 branch.
2014-04-16: Add auto-commit to gitian.sigs.
2014-04-15: Add GPG signatures to git tag.
2014-04-15: Deployed.
2014-04-13: Implemented nightly auto builder.

Mostly no, unless you enjoy enabling the non-default RPC SSL that almost nobody uses.

https://litecointalk.org/index.php?topic=17974.0
openssl has been upgraded and dozens of other little bugs fixed in the release candidate.

I would love this feature, with a small addition.  Make it appear again in my view only if people that I follow replied to it.

Glad someone will make centralized decisions like rule changes meant to scare people.  That inspires much confidence in the anonymous leadership.

I like the idea.  wangbus had ideas that might enable things like this, although we haven't thought much about automated categorization yet.

https://github.com/litecoin-project/bitcoinomg/commits/0.8.7-OMG12
tag v0.8.7-OMG12 is similar to Luke-Jr's 0.8.7rc1 with the following differences.

* Removed the three OP_RETURN pruning patches.  It seemed to have made it incompatible with indexes from 0.8.x.
* Reduced the relay fee by 10x to match the behavior of Bitcoin 0.9.0.
* Added the getnormalizedtxid RPC that was not accepted in Bitcoin Core.  This is an experiment.
* Many 0.9 features backported and carried forward from earlier versions of Bitcoin OMG.

You really should be using Bitcoin 0.9.  But if for some reason you can't, this version should be fully compatible with data from Bitcoin 0.8.x while including the important bug and security fixes from 0.9.  Most of the credit for this round of patches goes to Luke-Jr.

Status Update March 26th, 2014:
v0.8.7-OMG12 contains all of the security and bug fix workarounds pertaining to transaction malleability that were included in Bitcoin 0.9.  You really should be using Bitcoin 0.9.  Use this only if you need 0.8.x for some reason and you understand how to make backups.  At the moment this branch is only lightly tested, so please report back if you run into any issues.

EDIT:
I made gitian builds of 0.9.0 that should work on the same operating systems as the 0.8.6 builds.  However the builds in https://github.com/bitcoin/bitcoin/pull/3914 might eventually be better if it becomes an official fix.