Yes, but we can always try to solve the inconviences of our world in multiple venues. Let's try politics and simultaneously use the ingenuity we have to solve the problem while politics resolves.
I'd bet by stopping the water supply (out), disabling wifi and power, we can solve the destruction of evidence issue which could warrant the police actions.
Additionally, we could send a robot in place to search for unsafe conditions prior to the entry by armed police.
What other issues do we need to solve make this not happen while we wait for politics to catch up?
Given a jury without sufficient education and a case with as much technical nuance as this and then a reasonable doubt that the same technical nuance could indicate a frame job... Seems like an ok move...
I'm not sure how much competition Wikipedia has as a free online encyclopedia.
Any other encyclopedia and any wiki-formatted knowledge store could be considered close competition. Wikipedia's in the business of providing high-level (and often low) level information, and there are tons of players in that space - just perhaps not as generalized and overreaching.
Wikipedia is a non-profit. They don't really make more money by having more people use the site
Which doesn't mean that it can't compete with other entities, just that it does so under a special set of rules. It's still in the best interest of Wikipedia to keep up traffic.
It's amazing how much non-programming work is required to get an application release-ready. Add to that list domain acquisition, email configuration, staging environments, legal documentation, status pages, error tracking, user and subscription management and feedback mechanisms.
Our startup is tackling this domain, and we'd love to hear more of these "petty issues" web and mobile apps need to resolve before shipping - we've found that, while seemingly minor, they present a huge hindrance to the launch of developer side projects.
Do you recommend 'installing' config/environments/* information from a provisioning utility when you're dealing with configuration values that should remain secret and outside of version control?
I find the teams I work with generally end up transmitting secrets over untrusted centralized chat protocols. I'm glad to see folks stepping into this space and popularizing and simplifying this sort of security!
For environment-based configuration values and multi-member teams, I wrote conf_conf [1].
I'd bet by stopping the water supply (out), disabling wifi and power, we can solve the destruction of evidence issue which could warrant the police actions.
Additionally, we could send a robot in place to search for unsafe conditions prior to the entry by armed police.
What other issues do we need to solve make this not happen while we wait for politics to catch up?