I helped early on to review this plan for Alex and the Vectorized team, so I’m very excited to finally see it be released to the world.
Vectorized consists of quite the lineup of engineers (https://vectorized.io/team) and anyone who gets to be mentored by them will be gaining a huge advantage when it comes to Distributed System design and implementation!
Since there is relatively little information on the linked page, I'll put some questions I have here.
1. How does it work? It would appear the list is user curated. New submissions are from users (via submit) and ranking is based on hearts? Is there any future plan to be able to associate # of plays with a given episode (not sure if podcast app apis allow this).
2. In relation to #1 (an asked already by others), how can I subscribe to this in my podcast app?
Honestly, if they aren't asking for help formulating a solution, they also aren't asking for your suggestion to an alternative (even if you try to couch it in terms of a question). So just don't ask and you won't have the issue.
But do you also segregate the devices and networks you connect to for this identity, or can a sufficiently advanced adversary connect the dots where you link up with the rest of the internet?
They still retain the global rollout for the other use cases detailed in the write up, so its generally tested, though not for this one use case as you point out. I suspect the tradeoff is reasonable, however having a short pre-stage deploy before global in all cases would be a more conservative option that would prevent an emergent push from becoming an even bigger emergency!
Cool. Can we add infrared detection to determine if the car is just standing rather than parked, so you can eliminate the cases where a car is not in a parking spot, but would appear parked to this detector?
Great looking site. I just grabbed the app because I've been using the "What Knot to Do" app forever now, but find these animated single page descriptions more concise!