259 karma · joined September 15, 2017
Maybe their scripts determined them hosting on Medium was costing them too much money. /s
Tor is not targeting a “normal” person, as the media has already told the “normal” people that the only things available on the “dark”/“deep” web are illegal.
> Don't reveal your DNA, because socks are a better gift.
The two are completely unrelated, IMO.
Trust who? This bullet makes no sense to me. The entire list seems to boil down to "big company bad, wear tinfoil hat." There are certainly valid reasons one would not want to have their DNA sequenced by a public for-profit company, but this list is reaching.
> A pair of socks is a better gift.
I mean, really?
This may be one of my first "buy and hold" stocks simply for the personal reason of loving the service.
I would say (being a 1989 baby), that it isn't due to a lack of wanting, it's due to the systematic mass production of anything and everything. There is nothing worth collecting anymore, because there are 10 billion other copies of that thing... I mean, there are now more than 1,000 Pokémon when there were only 150/151 when I was a child. My holo-Charizard isn't worth anything these days.
I mean Spotify has been around a lot longer. Is it weird that new users aren't growing as fast if it already held the majority?
> Police said a "broken-down" charging brick and frayed cable were also found in the 14-year-old's bed. It is not thought those devices were made by Apple.
So, teenager gets electrocuted by frayed off-brand cable. How is this news?
Quoting a company that is essentially saying they had to seek funding because of twitter limiting API access is an odd choice for this announcement.
So our sample metadata has the generic metadata about each sample (where it's from, when was it collected, etc.). Our feature metadata is the particular feature metadata (DNA amplicon sequence variant, taxonomy, all seven taxa levels pre-split). These would work perfectly fine in a standard SQL database, but the problem is when we get into our sample-by-feature table/collection. Currently, we have over 400k unique features and tens of thousands of samples. If we were to try and map the frequency of each feature in our samples in a standard row/column relational database table, our table would be un-usably large (or just entirely not work as PostgreSQL, MySQL have a hard column limit). Thus, the benefit of MongoDB's document system fixes all the issues this causes.
Each of our documents in the sample by feature table can consist of ONLY the counts of the features that were in the sample, ignoring all the other N-thousand features that may be present in others. Building a pandas DataFrame from a query of this data will just fill the absent features with NaN, and we can just fill those NaN's with zeroes and carry on working with our target subset of the database.