# Styling RSS w XLS notes
XML files can include both xml-stylesheets (XSLT) and normal stylesheets (CSS).
XSLT files are transformations, and allow you to process an XML doc into an HTML doc (among other things).
In this case, it doesn't matter if we import the CSS here or via /rss/rss.xsl -- it gets applied either way.
The XSLT will output HTML for us, but the HTML content from the RSS feed (i.e., the bodies of posts) must be unescaped.
There's a special attribute (`disable-output-escaping`) which will do that.
However, we need to run some JS, too, because not every browser supports decoding html like that.
* firefox does not seem to support `disable-output-escaping="yes"`, so it requires the JS in rss.js
* chrome does support `disable-output-escaping="yes"`, so don't remove those attrs
The JS works by testing `#cometestme`, and then (if needed) looping over elements matching `[name=decodable]` and basically `el.innerHTML = el.textContent`.
Note, `disable-output-escaping="yes"` is a legacy feature from XSLT v1.0; the new way to do it is with character maps.
When I tried those, they didn't seem to work in firefox (which is when I tried the original JS).
IDK if chrome support character maps, but if it does, then that is a good update to implement. TODO I guess.
Broadcast Nonstandard Txs Quickly [Bitcoin]<p>NB: This document is <a href="https://github.com/xk-io/xk-io.github.io/blob/master/_posts/2015-05-10-broadcast-nonstandard-transactions.md">better read from github</a>, due to fomatting issues with the code.</p>
<p>So, I recently wanted to <a href="https://blockchain.info/tx/c058286d078f059eab4231475ad6fc23c4cd1520d603128b900c13582728a961?show_adv=true">broadcast a nonstandard tx</a> and didn't want to wait for full blockchain sync on my dev machine.</p>
<p>I knew that Eligius supports the <a href="https://en.bitcoin.it/wiki/Free_transaction_relay_policy">Free Tx Relay Policy</a>, and that I'd sent them nonstandard txs before, but all the IPs I could find weren't accepting connections. Finally I found <code>68.168.105.168</code> and was able to connect and broadcast the message. Later I realised you can <a href="https://getaddr.bitnodes.io/nodes/leaderboard/?q=eligius">search getaddr.bitnodes.io for 'eligius' to find nodes</a>.</p>
<p>This is a great start, but we still need to send the transaction. By default Bitcoin Core does not relay transactions that:</p>
<ul>
<li>Are nonstandard</li>
<li>Contain outputs not in the <strong>current</strong> UTXO set</li>
</ul>
<p>At this point we are going to need to compile a version of Bitcoin Core. We will need to address the above two problems to broadcast a transaction. The second problem is included so we don't have to download the whole blockchain, allowing us to relay pretty much anything.</p>
<p>The first section of code to change is <code>IsStandard()</code> in <code>script\standard.cpp</code>. <a href="https://github.com/bitcoin/bitcoin/blob/23254131a3fdaeae9c50dafca6d0addbbf235820/src/script/standard.cpp#L183">Source Link</a>. The quickest way to fix this is add a <code>return true;</code> at the top of the function like so:</p>
<div class="highlight"><pre class="highlight plaintext"><code>bool IsStandard(const CScript& scriptPubKey, txnouttype& whichType)
{
return true;
vector<valtype> vSolutions;
if (!Solver(scriptPubKey, whichType, vSolutions))
<snip>
</code></pre></div>
<p>Sweet, now all transactions are standard for our node. The next part is to relay transactions even when we can't validate the outputs they spend. When troubleshooting before I ran into <a href="https://github.com/bitcoin/bitcoin/blob/23254131a3fdaeae9c50dafca6d0addbbf235820/src/rpcrawtransaction.cpp#L796">this error message</a> being thrown. To avoid more debugging I figured the best thing to do was just rip the whole block of code out. That is to say this:</p>
<div class="highlight"><pre class="highlight plaintext"><code><snip>
bool fHaveChain = existingCoins && existingCoins->nHeight < 1000000000;
if (!fHaveMempool && !fHaveChain) {
// push to local node and sync with wallets
CValidationState state;
bool fMissingInputs;
if (!AcceptToMemoryPool(mempool, state, tx, false, &fMissingInputs, !fOverrideFees)) {
if (state.IsInvalid()) {
throw JSONRPCError(RPC_TRANSACTION_REJECTED, strprintf("%i: %s", state.GetRejectCode(), state.GetRejectReason()));
} else {
if (fMissingInputs) {
throw JSONRPCError(RPC_TRANSACTION_ERROR, "Missing inputs");
}
throw JSONRPCError(RPC_TRANSACTION_ERROR, state.GetRejectReason());
}
}
} else if (fHaveChain) {
throw JSONRPCError(RPC_TRANSACTION_ALREADY_IN_CHAIN, "transaction already in block chain");
}
RelayTransaction(tx);
<snip>
</code></pre></div>
<p>Becomes this:</p>
<div class="highlight"><pre class="highlight plaintext"><code><snip>
bool fHaveChain = existingCoins && existingCoins->nHeight < 1000000000;
RelayTransaction(tx);
<snip>
</code></pre></div>
<p>So, all that's left to do is compile bitcoind, run it with <code>-connect=68.168.105.168</code>, wait for the connection to initialize (which can be checked with <code>bitcoin-cli getpeerinfo</code>) and then <code>sendrawtransaction</code> when you've confirmed the connection. If all goes well the tx will appear in the next eligius block! </p>
https://forum.xk.io/n/2013