Skip to content

Instantly share code, notes, and snippets.


  • Brno, Czech Republic
Block or report user

Report or block urza

Hide content and notifications from this user.

Learn more about blocking users

Contact Support about this user’s behavior.

Learn more about reporting abuse

Report abuse
View GitHub Profile
bretton /
Last active May 12, 2019
Dashboard tools for Lightning servers

Lightning dashboards



NodeMonitor is a simple Python Django website that makes calls to Bitcoin (bitcoind) and Lightning Network (c-lightning lightningd) nodes and displays the results on a simple 'dashboard' style status page.

Zabbix clightning

View poc_refund_slate.json
"num_participants": 2,
"id": "d3e8ef7e-9beb-ac63-2b5f-a8c575d983f0",
"tx": {
"inputs": [
"features": 0,
"commit": "09597a4ad3118850f31b8033fc6802b3b78b3cd1c8f7eabdc5f650ec21045651ad"
nyuszika7h /
Last active Jul 9, 2019
Lossless stream rip cheatsheet

Lossless stream rip cheatsheet

This is a short cheatsheet to help you determine whether a release from Amazon, Hulu, or Netflix contains the lossless/untouched (as in no further loss of quality compared to what the streaming services provide) video/audio or not. Most newer P2P releases are correctly tagged, but for older releases, it cannot be reliably determined based on the tags alone.

In most cases, non-lossless rips from these services are screen captures (which, when done by professional releasers, should be high quality and contain little to no glitches – see the history section for details), but in some cases they may be simply reencoded from the untouched stream, for example to crop black bars or reencode from a higher-quality stream to achieve better quality. Also, generally the audio is untouched even when the video is not, but that's not always the case. There is no easy way to differentiate these cases, so I'm only describing what to look for in regards to lossless video streams, and for those

mapmeld /
Last active Jan 8, 2019
OverEncrypt - paranoid HTTPS


This is a guide that I wrote to improve the default security of my website , which has a certificate from LetsEncrypt. I'm choosing to improve HTTPS security and transparency without consideration for legacy browser support.

WARNING: if you mess up settings, lose your certificates, or decide to no longer maintain HTTPS certs, these steps can and will make your domain inaccessible.

I would recommend these steps only if you have a specific need for information security, privacy, and trust with your users, and/or maintain a separate domain which won't mess up your main site. If you've been thinking about hosting a site on Tor, then this might be a good option, too.

The best resources that I've found for explaining these steps are , , and


FWIW: I didn't produce the content presented here (the outline from Edmond Lau's book). I've just copy-pasted it from somewhere over the Internet, but I cannot remember what exactly the original source is. I was also not able to find the author's name, so I cannot give him/her the proper credits.

Effective Engineer - Notes

What's an Effective Engineer?

You can’t perform that action at this time.