A few years ago there was a discussion about making bike helmets mandatory in Germany. At least one scientist [1] did a cost-benefit analysis and argued against such a law. For example, while fewer people would die of head injuries, many more people would stop riding bikes (or do it less often), leading to an increase in cardiovascular diseases.
tl;dr: two reasons: if each minor step in the negotiations is made public, lobbyists and NGOs will constantly bug the negotiators. Furthermore, if one side publicly states which lines it will never cross in the negotiations, it loses leverage because the opposite side now knows on which points they can expect less resistance, and will use this knowledge as a tactical advantage.
That the TTIP-like deals take years is not by accident, but by design: the nasty stuff is to be included in one big package and obscured, to be accepted "by the democracy" only because it's a part of the whole "and look, there's some pork there too." Otherwise the smaller deals, which would actually be in the clear interest of both sides would happen much more often.
> I don’t recall the author now, but the gist of the argument made was that we’re too protective of our code - if you give someone responsibility, show that you trust them, more often than not, your intuition about people abusing their freedom is way off.
Maybe it was some of Pieter Hintjens writing and/or the C4 process:
Felix and I met some time before he wrote that blog post, and I explained our C4 process to him. His pull request hack, which I merged into C4 not long after, is neat though github doesn't provide the tools to do it easily.
Was going to suggest the same thing :) I haven't had the sort of success that the OP did, but that PR Hack post def inspired my way of operating! Yay Felix
Instead of copying & pasting, you should be able to click on the timestamp of the comment and then click "Vouch" (which I just did for XORcat's comment).
Well, Null Island has whatever size Null Island has (which is hard to ascertain, given that it doesn't exist) -- but the coordinate (0,0) doesn't have any area at all, it's a point.
We've done some stuff with sensor networks - eg our FOSDEM 2015 demo was hooking up cars via OBD2 ports to stream their engineering telemetry into Matrix for visualisation/analytics etc: https://archive.fosdem.org/2015/schedule/event/deviot04/
However, this is still fairly PoC. Our latency is deliberately high at the moment (given all events are persisted on all participating servers, and signed etc) - typically around the 100-300ms mark depending on server performance involved. If you want lower latency stuff (eg VoIP or MIDI) the architecture is that you use Matrix to be a signalling layer to negotiate the realtime protocol (eg RTP).
