HN user
The service Sheldon Brown provided to cyclists worldwide cannot be overstated. It also becomes apparent every time one needs to research some bike subject involving any technology that appeared after his death.
The overhead exists when a novice is trying to use Vim the way it is intended to be used in order to learn. Using insert mode to get the same behavior as non-vim and avoid normal mode is, in my opinion, bad learning practice.
I think an important part of the Vim workflow that I haven't seen mentioned is the fact that -at least for myself- it keeps the mind engaged during "menial" operations.
When switching from dealing with the information included in the text (typically thinking about code content) to operations of moving text around and other text logistics, I often find my mind "waiting" impatiently for my hands when using non-vim editors. In contrary, when using vim (I consider myself a mid-range user), I can somewhat remain closer to the flow.
At the same time, I still remember (albeit vaguely) a significant overhead of the Vim language before becoming acclimated.
I infer it was aggressive, based on the following:
Per Christian (the Apollo app dev): "(...) Twitter's pricing was publicly ridiculed for its obscene price of $42,000 for 50 million tweets. Reddit's is still $12,000. For reference, I pay Imgur (a site similar to Reddit in user base and media) $166 for the same 50 million API calls." [1]
All assuming he is not lying (which I have no reason to believe, contrary to the reddit reps). Two orders of magnitude over Imgur pricing sounds a bit greedy, unless Imgur is also at the verge of collapse, which I'm not aware of.
[1] https://old.reddit.com/r/apolloapp/comments/13ws4w3/had_a_ca...
I understand your point.
The thing is that they should be able to introduce their API pricing without triggering the events of the past days. I'm not even remotely an expert, but the pricing seems too aggressive and seems to contradict was communicated earlier (again based on the apollo transcripts).
On the other hand they are supposed to be experts, or they should at least ask one, given the millions of users, thousands of mods, etc involved.
"You can host your own community then"; Sorry but I'm not really a fan of this "make your own (...)" attitude, especially when excusing corporate behavior against volunteers
I mean that there is a spectrum ranging from paying the bills and making profit to blatantly exploiting everyone involved. Based on the Apollo logistics, reddit API pricing seems to fall on the greedy end of the spectrum. At the same time we have examples with high-traffic websites (e.g. Wikipedia) which manage to build upon volunteer effort and be sustainable without pissing everyone off within a few days.
It looks like ipv6 matching is supported since late 2017 (version 10.0 [0]), although the changelog states that "not all ban actions are IPv6-capable now". As for IPv6 capabilities, I don't have any recent experience with the software.
[0] https://github.com/fail2ban/fail2ban/blob/0.11.1/ChangeLog
Fail2ban [0] bans ip addresses based on failed login attempts (works for more than ssh), minus the isolation layer.
Possibly the best solution would be an installation of the Logitech Media Server (LMS) on a raspberry pi (e.g. piCorePlayer [0]) or an already available home server. LMS can then handle all squeezeboxes (or squeezelite installations on other hardware) on the same network and allows control via a web interface.
After spending a few years in a similar situation, and not wanting to maintain my own server, I settled with using runbox.com. It's an economical and privacy-oriented, mail provider which allows (necessary for my needs) using your own domain. They have very quick and excellent support (the few times that I needed it) and also offer a CalDAV/CardDav service. Their web interface is lacking (I believe it is about to be updated) but this is an non-issue for me science I use mutt. I'm not aware of a mobile app (I personally use and suggest the excellent K-9 mail OSS app).
Actually Python 2 allows that, in Python 3 True, False, and None are reserved words [1].
[1] https://docs.python.org/3/whatsnew/3.0.html#changed-syntax
Then this is not really the backup though... I mean it is not a backup if you don't understand it completely.
While the difficulty of reading markup vs a compiled document is subjective, there are tools such as texstudio [1] that allow real-time preview of the document synchronized with the code [2].
[1] http://www.texstudio.org [2]: https://i1.wp.com/gauravtiwari.org/wp-content/uploads/2014/0...
Although unfortunate for the author (and a huge inconvenience), such cases display in the best possible way the problem of depending on non-federated communication tools which promote disowning your data under ridiculous privacy policies.
"could it possibly be … that the best way to get good research and publications out of scholars is to hire good people, pay them the going rate and tell them to do the job to the best of their ability?"
Sounds very reasonable. Does anybody have good examples of this approach? I have the impression that this is similar to the environment of Bell Labs during the "golden years".
The article argues a very interesting point and there might definitely be an opportunity for more competitive open hardware. At the same time, it feels kind of sad that it would take a technical constraint for this to happen; that is, rather than a change in culture.
In what ways do you find SyncThing lacking when compared to BTSync? I started using it for work (cautiously) a couple of moths ago and have found it to be very similar (with respect to stability and ease of use) with BTSync, if not superior. Note though that I haven't used BTSync since its first days.
This can become very useful, especially if expanded by others as well. If I understand correctly results refer to raspberry Pi 2? They would probably be similar for both rPi B+ and rPi 2 although it would be nice to mention the model somewhere.
The most appropriate compression algorithm to use is highly case-dependent (data structure, compression vs decompression cpu/wall-clock time, compression ratio, system memory,bandwidth, etc.). I'm sure people at kernel.org have their reasons to convert to xz.
The following link has some interesting (albeit non-exhaustive) benchmarks, comparing various compression algorithms (both serial and parallel implementations). http://vbtechsupport.com/1614/
It is interesting to point out that using -O3 optimization drops the C (and Cython) code exec time by roughly 45%.