317 karma · joined June 6, 2013
mail@aaren.me
I advocate for LVT in the abstract but get stuck on explaining implementation in a relatable way.
p.s. really appreciate your persistent posting on this :)
Sadly it doesn't work on android firefox.
I'm just trying to counter the idea that the excitement around ethereum is somehow manufactured by 'clever marketing'.
Why didn't these companies develop their products on Bitcoin? Are they incapable of due diligence in this space?
https://azure.microsoft.com/en-gb/blog/ethereum-blockchain-a...
If more of these networks spring up, then maybe something good will come of BT's tardiness in laying decent infrastructure. Granted, B4RN is strongly enabled by being able to easily lay fibre under farmland, but there are other models that are more appropriate in urban areas - see e.g. the guifi network [2] in Catalonia.
[1]: http://b4rn.org.uk [2]: http://guifi.net
It would be great if this installer could leverage the trust I have in my system to painlessly acquire and then validate the tails iso, without having to deal with
I just tried feeding a regular debian iso to the installer and it didn't complain at all. This shouldn't be possible - what if this was a bad tails iso?
I don't know much about supersonic fluids. For anyone interested in following this up, here is a paper on "Reproduction of Virtual Sound Sources Moving at Supersonic Speeds in Wave Field Synthesis":
[fzf] is ctrl-r on steroids.
[fzf]: https://github.com/junegunn/fzf
It's a fuzzy pattern matcher for your shell history (and lots more).
It would be good to be able to transparently edit a .ipynb in a text editor - I've been meaning to wrap notedown in a vim plugin but haven't had time. This still leaves the version control problem though.
Note that I recently enabled the reverse (editing markdown in the browser as if it was a notebook), enabled by setting the following in ~/.ipython/profile_default/ipython_notebook_config.py (or similar):
c.NotebookApp.contents_manager_class = 'notedown.NotedownContentsManager'
This is useful for more interactive work, e.g. iterating on plots, whilst still having everything stored in markdown. See [1] for more info.Markdown syntax for generic containers (Div and Span) hasn't been implemented yet but the discussion is fairly mature now:
Second: The PR for image attributes is here: https://github.com/jgm/pandoc/pull/1806
There isn't a PR for internal referencing yet because the implementation hasn't been worked out yet and it isn't a simple change (should there be a native representation, should it be a filter, which syntax should we use, what about the existing citation syntax...).
Internal referencing and attributes on figures are two things that are currently being discussed for pandoc. The discussion has been going on for quite a while though - hence people making forks.
Discussion on internal referencing: https://github.com/jgm/pandoc/issues/813
Discussion on image attributes: https://github.com/jgm/pandoc/issues/261
(except for really simple cases)
The alternative to Gitlab that I've found on windows are a bit lacking. Bonobo is nice but very basic.
http://www.ecofan.co.uk/woodstove-ecofans.html
It's a heatsink with a peltier sandwiched in the middle that drives a fan. Works pretty well for wood burners. Also it's just fun to get electrical energy from your stove :)
One problem I've got is black internal borders on some of my menus (e.g. network-manager panel menu), but it doesn't affect me much and I really can't be bothered to read the docs to sort it out. Any ideas?
This was the good thing about Crunchbang: a lightweight debian install that looked good and needed hardly any configuration to work well.
https://github.com/junegunn/fzf
It's a fuzzy searcher for Ctrl-r that shows all possible results, updating as you type.