onestone

I simply put my apps in different namespaces on dev/stage/prod/etc. That way a kubectl command run against the wrong cluster will fail naturally.

Well, baseless naysayers are just as bad as baseless hypers.

StorPool[0]. Inoreader recently blogged about their experience with it, and why they chose it instead of Ceph[1].

[0] https://storpool.com/ [1] http://blog.inoreader.com/2018/03/success-story-inoreader-op...

Any bets on how their next IM app will be named? My pick is Hangouts Talk.

Yeah, flagged for being inaccurate.

FUD. Insufficient liquidity on some exchange might cause the price to fluctuate briefly, of course. But it quickly corrected back to $1.

> There will be no breaking changes from Beta 3 to stable, so our changelog should be short and sweet. Expect some linting, Sass variable improvements, updated docs Examples, and more build tool improvements.

Nice! We can finally use Bootstrap 4 without expecting future breaking changes.

I have several servers in GRA which were unreachable for two hours. Might have been due to the routing or DDoS-protection infrastructure.

The Ethereum "ice age" is a mechanism to ensure smooth transition to future planned hard forks. By tweaking the difficulty adjustment formula to artificially increase block times after some time (the so called "difficulty bomb") it makes mining on the old chain unprofitable, and incentivizes everyone to move to the/a new one. The general idea is to prevent extreme conservatism and stagnation w.r.t. hard forks, as we are seeing in Bitcoin.

I was the one who added Yarn to the official docker-node image[1][2]. This was the most popular docker-node feature request at the time. We managed to achieve it with a minimal size increase (with the help of the awesome Yarn team) and without affecting anything else. There was already a history of us providing some bonus features which the upstream Node project doesn't, such as a musl-libc build (for Alpine Linux).

[1] https://github.com/nodejs/docker-node/pull/337 [2] https://github.com/nodejs/docker-node/pull/403

Good luck claiming SLA refunds from them. Their "support" will stall for months and in the end forget/expire your requests.

The same loophole is used in Bulgaria. Our largest bank charges 7 EUR for receiving 1 EUR, and 19 EUR for sending 1 EUR.

Article incorrectly states that BTC-e was "Bulgaria-based", like many other articles unfortunately. There is zero evidence for that: https://bivol.bg/en/no-bulgarian-connection-found-so-far-in-...

Why is it always assumed that the "company" was based in Bulgaria? Which "company" is it? As a Bulgarian myself I've seen that mentioned several times in the past, even on reputable sites, but never seen any actual evidence.

P.S. An investigation from 2 days ago also fails to find any Bulgarian connection to BTC-e: https://bivol.bg/en/no-bulgarian-connection-found-so-far-in-...

And here from TechCrunch: https://techcrunch.com/2017/07/24/snopes-seeks-crowdfunding-...

Well no, actually. Good Nvidia cards are also nearly extinct, because they are actually still profitable for Ethereum mining. So when people couldn't find AMD cards, they settled for bying Nvidia.

Unlike the situation with Bitcoin a few years ago, Nvidia cards are ok for mining Ethereum (something like 40-50% lower hash rate than AMD, but still very much profitable).

It's also true for other countries in the eastern part of the union.

Apparently the EU Parliament is trolling Theresa May.

The truth is almost exactly the opposite of what you say actually. Yes, Arch is more difficult to install and configure the first time because it requires you to actually understand the steps it takes. But the top quality documentation really makes that not so difficult.

Arch is actually much _easier_ to maintain afterwards (once installed and configured) than almost anything else. This is because it does not add layers of useless abstraction, very much unlike DEB and RPM based distros. Packages are very close to upstream, with only minimal patches when really necessary, unlike RPM/DEB distros which heavily customize and patch most packages. Packages are also very easy to create, you can learn to do that in minutes, again very much unlike DEB and RPM which are needlessly overengineered and have whole ecosystems of helper scripts aiming to help with that complexity, but you have to spend a lot of time to actually learn them as well.

Seems clickbaity and inaccurate. List of many other "primeval" forests in Europe: https://en.wikipedia.org/wiki/List_of_old-growth_forests#Eur...

Also, I might still want to do some things differently server-side in getInitialProps(), despite most of the code being shared. For example, clients might access the API through a load-balanced frontend, while on the server I might want to prefer talking to an API process on the same machine. Authentication might also be different. Of course these things (e.g. the API endpoint) shouldn't be hardcoded, but even then you need to get them somewhere, most likely a configuration file or an environment variable. And sharing these details (names of environment variables for example) with the client is not something I particularly like.

You are right about that, I admit.

Still, using the same transpiled code both client-side and server-side is suboptimal at least. E.g. if I target Node 7.x on the server, I don't need to transpile async functions for example (and screw stacktraces in the process).

I evaluated Next.js recently, and while it looks excellent on the surface, there were a couple of red flags:

- Devs insisting (incorrectly) that they _have_ to ship the component source code _inline_ in the server-rendered HTML. I commented on this issue here: https://github.com/zeit/next.js/issues/427#issuecomment-2908...

- The same transpiled code is used both server-side and client-side. Code which should be strictly server-only, e.g. getInitialProps(), is visible client-side as well.

> Wasn't Ethereum unusable for a a decent percentage of 2017 so far?

No. Ethereum suffered DoS attacks for a couple of months, but even during the worst of them it had significantly larger tx capacity than Bitcoin.

This doesn't work well for modern websites using push-style updates, e.g. via websockets. Old nginx processes might never close after the reload, as connections are very long-lived. If reloads happen often this leads to memory exhaustion. So this is a bad solution to rely on.

Wire's audio quality is the best in my experience.

You missed Spaces (which was also recently discontinued).

I actually meant economic majority because that's what gives the token its value. A >50% hashrate majority in a PoW blockchain can censor transactions, but it's powerless if most users (or most precisely, the users who own most of the tokens) collectively decide to hardfork.

I'm saying that the main rule for all blockchains (not only Ethereum) is that consensus is decided by the majority. This is their "constitution". The majority of the stakeholders in a blockchain can decide to change the consensus rules. In a traditional legal system majority is not required, laws can be changed by relativly few people.

In otherer words, the constitution is above the law. And the constitution allows laws to be changed, in this case by the will of the majority. The same is true for all public blockchains btw.