I don't even start the video. They are almost always just marketing and hyperbole anyway. I assume that if they went through all the troubles of creating a video they must also have the information in much-easier-to-produce text form. This has come back to bite me only a few times when somebody points out information in an introduction video that is not covered in the "Introduction" page of the manual, but I consider the win of not having to sit through boring hour-long sales pitches much greater than the abysmal information loss.
Video can be by-product of internal training, I often suggest we record such meetings for people that were sick/fture workers. It's better than nothing.
While you do want HA you also want to keep things simple. You get great HA with just one backup machine. The times you lose two machines are so few that you might crash the site with software failures far more often anyway.
Databases have inherent locking problems that takes more resources to resolve with more machines, more so in some database systems than others. When scaling you often hit a point where you get down to macro logistics, so imagine a car highway: You can get more throughput by adding more lanes. But what that all cars are going to merge to one lane at some point in the middle of the trip (because of a tunnel, bridge or something: it's impossible to have more than one lane at that point)? Now you won't get any throughput benefits of the multiple lanes after all! Just more latency because you get queues up until the single lane and because of the queues all cars are going slow and need to accelerate on the single lane, so the average speed is low too. You are also having too much resources after the single lane because you can never fill all those lanes. It might be better to have one beefed-up single-lane road all the way that people can go fast on. Basically: Remove locks and you get better overall performance.
Yes, this is on the expense of HA. Yes, the costs of scaling up grows asymptotically faster than the costs of scaling out. So this is definitely a trade-off in some sense.
No voice? That lost all of my interest. So now I need to tap out a message on my expensive, somewhat fragile smartphone with dirty fingers while losing all sight of the road for a minute. Instead of a sturdy walkie-talkie where I can hear the voices of my friends, talk efficiently in real sentences and I can look where I'm going all the time.
I get it's not for everyone, but what we learned as we developed this is that more people wanted asynchronous data comms as opposed to real-time voice. And when I say "more," I mean like, 75% of testers preferred the former.
From a networking perspective, as well, it makes our ad hoc reconfigurable network more scalable if we're focused on short-burst transmissions that are, technically speaking, delay-tolerant. This means that even if you're at a huge event with tons of people using goTenna, even if a gajillion of them press "send" at the exact same femtosecond, all the messages can get through in a matter of seconds if not milliseconds.
Note that 12 kg is 26.5 pounds, so they are all somewhat related to each other but not exactly.
The number of significant digits on the Castille version is ridiculous compared to the others. Could it be that Castille still uses this unit and therefore have such a specific translation value?
And the user still has no way of ensuring the safety of the underlying transport. How do I know the form is going to be sent over a secure link after a push the button? Who will get this credit card? It doesn't say anywhere. But the blog post tells me the info is going to be sent to a third party, but that is not explicit in the form. I hate that "security" is all about meaningless icons, not about being transparent to the user.
Security has always been mostly illusions to help us overcome our fears to get through the day rather than real defense. So what if we all have our security blankets to chase away the monsters?
The real security is using a credit card where you can undo the transactions after the fact, which is amazing if you stopped and thought about it.
It's pretty strange to get root access to a server, even though it's just a Docker VM. We can install anything we want, compile any C code we want, DDoS and spam anyone we want... The machine is also crazy loaded right now, with 100% load on all cores (according to htop that I installed from the package repo), almost run out of RAM and disk space decreasing fast.
Yes, I'm from Runnable. People have tried fork bombs. We are pretty good and cleaning them up. Please do not try this and let other users enjoy the platform
Nice, but some users are not "honorable". And you make it super easy and quick to make accounts, no confirmation, just enter some email address. (not that i'm complaining about that part, i like easy signups... but it may open you to abuse).
I'm an early beta user. Your web app is run in a virtual machine. You can store stuff to disk, in memory or in your own database (the PHP container gives you a database per default). I am not sure what happens to stuff in RAM if they choose to migrate you to a new host machine, though.
