And I want the name generator. IMHO a name generator like this should be built in every system that requires you to choose a username. Perhaps an IDE should also have it and let you generate temporary names (for projects and, perhaps, for classes too) you can auto-refactor once you actually write some code.
> For this hackathon we used data about whether a street is lit or not from Open Street Map. Later we could incorporate official UK gov data about street lighting or even incorporate satellite imaging data.
It sounds like getting the data right wasn't the focus yet:
> Later we could incorporate many other kinds of data such as safe checkpoints trivially. The core technical challenge was wrangling the data and writing our own custom routing algorithm.
This is a common pattern for OSM. The tool to use the data helps locate areas where the data isn't complete (say you plan a route through an area you know and it doesn't make sense).
The highway=street_lamp tag indicates that there is a lamppost (which can be a navigational aid), but is a much more detailed form of mapping that should be used in addition to the lit-key on the ways themselves.
Hi there and thanks for your message!
Yes, you can upload your patients’ files on Cubbit because their privacy is guaranteed by our zero-knowledge cryptographic architecture. You can read more about it here (https://help.cubbit.io/hc/en-us/sections/360003191800-Securi...) but in short files uploaded in our network are encrypted with AES-256 and split into dozens of chunks. Each chunk is distributed in more than one copy via end-to-end encrypted channels across our network to ensure redundancy and constant uptime. The user's password is not known to us nor to the coordinator server, and its related randomly-generated encryption key is stored client-side.
Answering your second question: Cubbit differs from traditional cloud storage services in several ways:
-->Distribution: traditional cloud platforms run on data centers, Cubbit, instead, is the first cloud platform for the general public that is built on a distributed network of devices owned by the users.
-->Security: most traditional cloud platforms do not enforce the highest security standard, as their business model is based on exploiting the users’ data. Because of this, traditional cloud platforms open themselves to data breaches, leaks, and a wide variety of attacks. Cubbit instead employs encryption, distribution, and a zero-knowledge architecture to protect the users’ data.
-->Control: More often than not, user data is owned by the corporation running the data center. With Cubbit, our users own their data.
-->Eco-friendliness: Cubbit is designed to minimize the carbon footprint. Thanks to its distributed architecture, Cubbit saves a lot of energy compared to traditional cloud platforms, which are burdened by maintenance costs (the data center needs to be cooled down to work properly) and long data transfers, that in certain cases can be as energy-consuming as data storage itself.
I mean, we should help our friends to migrate to new solutions. If we don't we lose.