Really nice to see BFT starting to be taken seriously in CRDT research. I had done some research in this area last year and came to a lot of the same solutions (i.e. BRB protected CRDTs when dealing with VClock based CRDTs):
We ended up moving away from VClock crdts entirely for our work and going with grow-only hash-graph CRDTs as they have don't need the BRB overhead (as Martin has found in his research as well).
Yes, but the really hot part is not emitting visible light. ;)
If you're curious about why the bottom glows: ExB drift pushes electrons to the bottom. I'm sure that doesn't make sense, but unfortunately there isn't really a shortcut to understanding here. Some books are pretty accessible though (I'm a fan of The Future of Fusion Energy).
You contacting the plasma would cause it to collapse, but you would already by cooked. It's a chicken and egg question, because a plasma is never going to get started with a person inside; it needs a near perfect vacuum.
I read through the whole article and didn't realize the video was there until I read this comment chain. I had just glanced past the video assuming it was an ad.
> n ∈ N (p), where N (g) is the set of gnomes who can hear g, including himself. Note that h ∈ N (g) ⇐⇒ g ∈ N (h).
> Each gnome g tracks the spread of the proposal in the following way: once all his neighbors n ∈ N (g) say their k-neighborhood (or bigger) is aware of the proposal
If I understand this correctly, a single node crashing would stall it's entire neighbourhood. @gritzko, can you confirm?
Nope. Missed a heartbeat means gone. We discuss churn later in the article.
Its effects are complicated, but as long as d holds, everything else holds.
I will stop looking into this now, I have to get back to my work. The colorful language doesn't make it easy for someone who follows the literature to review your idea.
I still have doubts that you can handle a dropped message or how much control a faulty node has over decisions, but I'll leave that to you to work out.
These companies should realize they are playing an iterated prisoners dilemma game with their customers. Just because your services aren't right for me today, doesn't mean I won't come back in the future and pay for your services again now that I know what you do.
But I doubt I'd come back if my last experience with a company has been a bad cancellation procedure.
Wrong attitude, and wrong. If I am trying out a few things that don't pan out, I may want to cancel. Then I may want to come back in a few months. Also, this space is moving quickly, so if they aren't improving the product quickly then they will die quickly, so I am sure the people using these tools are trying things out every now and then. Also, you are tainting your word of mouth. Just because I cancel doesn't mean I can't recommend it to someone else who may have different needs. But if it's a pain to cancel I won't be doing that.
I'd say the chance is much higher for B2B businesses. Say my Shopify store fails so I cancel my subscription. But I'll likely come back and try my luck again with Shopify on my next idea since I've learned the platform.
What about word-of-mouth recommendations? If a service doesn't work for me and I cancel, I may still recommend it to someone else. Not so much if I know they're going to hate me for it if they try to cancel.
With the risk of generalizing, this is what I do with some streaming services. I subscribe then cancel after 2-3 months after I've finished watching what I was interested in. I do this with HBO, Showtime, Hulu, Netflix, etc..
I do the same with Leetcode, cancelling my subscription after I'm done prepping then resurrecting it if needed.
3% conversion on a product that costs $20k is normal? I don't think so.
As to your cynical meta-analysis, these people are doing something really difficult. I'm very happy to celebrate with them in any of their little victories, good on them! I hope to see more from them in the future
Maintainer here, it's meant to be a visual representation of a 2-tuple of natural numbers.
But I get your point, there was another commentator here who expressed similar frustrations. When I find some time, I'll see about picking a clearer example for the README