nefariousoctopi

A lot of the comments here suggest that some of the functionality can be replaced by extensions like vimium-ff [1]. If you only compare the list of features then maybe. If you try using the extensions, you immediately notice that the keybindings don't work outside of fully loaded page, have horrible lags and delays and misses a keyboard event from time to time.

For the curious folk, the GitHub page [2] seems to do a better job at telling the how of things.

My question is why Lisp for scripting? What's the technical reason behind choosing it? Or is it just personal preference? I use emacs myself and my only complaint is elisp. In this time and age it looks very alien-ish to most people and judging by my colleagues, It can be a major deterrent from using emacs.

Second thing is that quite frankly at that price point Advantage looks a and feels a bit flimsy (especially the middle part between the key wells) though it has seemingly no impact on typing.

And lastly, I have a bit broader shoulders than average and I need hands a bit more apart than the key wells on Kinesis and maybe a bit more tilted sideways (well at least I think, I am not a doctor). It is orders of magnitude better than it used to be on a regular keyboard, but I still have sore muscles around shoulder blades and back of my neck sometimes.

All of these issues seem to be solvable by a split. I still hope that Kinesis would release a split concave keyboard by themselves since among all of the concave keyboards it is by far the most user friendly (no assembly required, no QMK compiling, remapping is doable on the keyboard itself), but I am starting to oogle the likes of Dactyl, Dactyl-ManuFrom or Bastyl[1] (which is modified Dactyl with less DIY required for more $$).

If I go the DYI way I am also thinking about mounting trackball on it similar to the Tracktyl (trackball helped me immensely with my wrists). What I am a bit afraid of is that once I start doing customizations I'll need/want something easily modifiable/adjustable to experiment with quickly. This design [2] in combination with Bastyl-like flexible PCBs seems like a neat idea I'd like to try.

Be not mistaken, Advantage is, not entirely unlike a good office chair or a mattress, still worth every penny, but IMO the split concave keyboards are the "future future". I would not even think of building a keyboard before Advantage, but now I do and there is no turning back for me.

The average latency does not tell us much since it does not really represent anything meaningful - i.e. it is not the latency of typical user/request as you might expect since the average is being skewed by the extremely high tail-latencies [2] or by the multiple modes (the peaks in latency histogram). The typical latency would be more likely better represented by median latency (not in the multimodal distribution case afaik).

As for why not go just go with median latency: you usually need to make multiple requests in parallel and end up waiting for the slowest request of the group. The 95th, 98th or 99th percentile is commonly used to cover for this (sorry can't find a suitable reference). This is also preferable in case of the multimodal distribution (well at least for monitoring and/or general performance diagnosis purposes since you usually care about the worst/tail cases).

Unfortunately, this does not solve verification of the apk signature. As far as I understand it, Android uses something similar to "trust on first use" [2] with apk signatures, so verifying the signature before first installation should be sufficient for most people.

What caught my eye is, if you scroll down long enough on dedicated servers page [1], you will eventually see GaaS - "Geek As A Service". This made me giggle far more than I am wiling to admit :)

It might be interesting to integrate IPFS into standard BitTorrent clients.