diff --git a/README.md b/README.md index 6a58e30a..dc3ad966 100644 --- a/README.md +++ b/README.md @@ -69,9 +69,9 @@ Any change in the english texts can be done through a pull request on github. If ## Advanced Usage -### Alerts +### Alert banner -You can easily put an alert on the website by changing the ALERT and ALERT\_CLASS variables in _config.yml. +You can put an alert banner on the website by changing the ALERT and ALERT\_CLASS variables in _config.yml. You can both set one fallback alert for all languages and many translated alerts for specific languages. Example: @@ -88,6 +88,32 @@ ALERT_CLASS: This will produce an english red alert box for all languages, and a translated red alert box for french language. Possible classes are: **error** (red), **info** (blue), **success** (green) and **warning** (yellow) +### Network alerts + +Network alerts should be placed in `_alerts/YYYY-MM-DD-SHORTITLE.html` and adhere to this format: + +``` +--- +title: "11/12 March 2013 Chain Fork" +lastmod: "Fri Mar 16 22:58:00 UTC 2012" +alias: "chainfork" +active: true +--- + +
+A chain fork is happening. Please stop mining on bitcoin version 0.8.0. Your bitcoins are safe but it is recommended that you postpone your Bitcoin transactions for the next hours. +
++More information will follow. +
+ +``` +* `SHORTTITLE` is used to construct the URL. +* `title: ...` will be used as the title in the layout. +* `lastmod: ...` will be used as the last modification date in the layout. +* `alias: ...` (optional) a short alias to be used for Bitcoin-Qt alerts. Ex. "dos" will produce /dos.html +* `active: ...` (true or false) define if the alert should appear as ongoing in the network status page. + ### Release Notes Release notes should be placed in `_posts/releases/YEAR-MONTH-DAY-SHORTTITLE.md` and adhere to this format: diff --git a/feb20.html b/_alerts/2012-02-18-protocol-change.html similarity index 85% rename from feb20.html rename to _alerts/2012-02-18-protocol-change.html index 7faa1309..7e6a8a0a 100644 --- a/feb20.html +++ b/_alerts/2012-02-18-protocol-change.html @@ -1,11 +1,9 @@ --- -layout: base -lang: en title: "February 20, 2012 Protocol Changes" +lastmod: "Mon Feb 20 00:10:00 UTC 2012" +alias: "feb20" +active: false --- -In June 2010 the Bitcoin reference software version 0.2.10 introduced a change to the protocol: the 'version' messages exchanged by nodes @@ -36,8 +34,3 @@ channel on Freenode IRC. If there are unexpected difficulties this page will be updated with relevant information.
-A potential security vulnerability has been discovered in the Windows version of Bitcoin-Qt. If you are running Bitcoin-Qt versions 0.5 @@ -227,9 +225,3 @@ href="https://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.6.0/test/ href="https://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.5.3/"> 0.5.3.1 för Windows och 0.5.3 för Linux
- -A denial-of-service vulnerability that affects all versions of @@ -61,8 +59,3 @@ Could this bug be used to install malware on my system?
No.
-A bitcoin miner running version 0.8.0 created a large block (at height 225,430) that is incompatible @@ -37,8 +35,3 @@ The core developers have investigated what caused the old versions to reject the blocks, and have released a 0.8.1 version that avoids creating blocks that are incompatible with older versions. A full post-mortem document has been published.
-If you are using an old version of Bitcoin-Qt (or bitcoind, the server bitcoin software), @@ -68,8 +66,3 @@ that bug, we determined that the bug can happen even if the entire network was still running old versions of Bitcoin-Qt/bitcoind. Therefore, the only option is to require everybody to either upgrade or workaround the bug.
-