@Rob oh that's really cool, I can certainly do that. How would that rpc call work?
Got you for the seed. Maybe at some point then depending on how I modify my infrastructure and if we get really popular!
I will probably put it at dnssseed.biblepay-explorer.org when/if that happens.
@Klondike
It automatically removes it for aesthetic reasons if your screen is under 992px (original iquidus design choice).
I will have a look at it but mobile browsing is not on top of the list for me as it can get really tricky .
Ok cool, if you have the infrastructure Alex for a port forward, maybe you can forward 40000 to something.biblepay-explorer.org? If you do just let me know and Ill add it to the base. It would be nice to have more than me in there, because that external node is maxxed out with connections. Now that I think about it, I can easily add my vultr4.biblepay.org node to dns seed (that will be a future sanctuary), OK thats done so we are good.
Anyway, on the Bible Verse RefTagger Pop-Ups: This would probably only work for you if you memorize them inside the code first and dump them in. But for fun lets look at the calls:
exec books
This call gives you a list of all 66 books in the bible and the corresponding short names used in BiblePay during hashing.
So once you know the short names you can type:
exec bookname rev
And receive "REVELATION"
Or exec bookname mat and receive "MATTHEW".
So what you can do is if you saw for example "REV|1|1" in the biblehash you could expand that to "REVELATION 1:1" and place that on the page, include the reftagger javascript (by looking at the source of that prior page) in the BX, and then anytime someone hovers over the verse they would see the full reftagger verse popup
.
EDIT: Note: You only have to include the reftagger stuff at the top of the page, so no ajax work to do in the page. In the page, you just have "REVELATION 1:1" in the text somewhere, and reftagger picks that up automatically.