"more than 8 in 10 open source developers are white"
According to Wikipedia 72% of the population of the USA are white, so maybe 8 in 10 is not really that much of an indication of discrimination or disadvantage. (72% boils down to "more than 7 in 10").
While OSS is not 'just' a US thing, it is probably heavily weighted toward US participation. Although India and China have huge populations of technically educated people, the language barrier is probably a factor there.
I would imagine that the region with next highest contribution is Europe, which comprehensive English teaching. (also: mostly white)
"we updated Chrome’s certificate revocation metadata immediately to block that intermediate CA"
Dumb question, why then does Chrome on my computer show "Google Chrome is up to date."? Shouldn't there be an update ready? Or is there a different (silent) way to update certificates?
What is the secret ingredient of graph databases? The presentation linked from the presentation mentions physical addresses instead of IDs. I get that that would be a speedup, but I would expect it to be more like a constant factor?
Then maybe you can save all links from a node in the node, so you can get all the links with one read access. Fine. But as soon as you get to the second or third level, I would expect the magic to be gone. Say every node has 100 links. OK, so the first 100 links you get in constant time c. But to get the second level, you already need 100 requests (one for each node and it's attached link list). So 100c time. For the third level you need 10000 reads, 10000c time. The next level would be 1000000 requests.
Just saying I'd expect things to get ugly with a graph database pretty fast, too (not as fast as with a relational db, but still).
I haven't really coded a big graph based app, but my expectation would be that get really good performance, a hand coded solution would always be required. For example trying to squeeze as much of the relevant data into memory in a compressed way. Am I wrong?
Oh and also I am not sure how good relational DBs are at query optimization. Just because the visible model is "one row per link" doesn't mean the db couldn't do some intelligent caching internally.
Data models that use deep "JOIN"s are way faster on a graph database. You're right about branching factor- if you always traverse all relations, any database will be slow. In most cases, however, you don't.
What tends to actually happen in the altcoin pump and dumps (None of the Twitter pumpers do BTC or even LTC since it would take too much money):
The pumpers build a position in a selected altcoin. They do this slowly, over a period of time, hoping that no one will notice. Only once they are satisfied with their position do they announce their "pump". They broadcast the idea of "pumping" that coin by a massive coordinated buy. The masses intend to buy in, bidding up the price and then selling off at the higher price.
The problem is that the people coordinating the pump already have their coins. And so as the people they recruited are buying, they're buying coins from the coordinators. When that activity starts to taper off, the coordinators will dump whatever they have left, completely trashing the price, often below the starting point. So the coordinators are the only ones who benefit at all.
There's various tricks they also use to make it more convincing, with bid walls and talk of "noob traps", but at this point it's happened so often that willing dupes are getting hard to find.
Most pumps these days barely move the price at all. Fontas is so infamous that his pump announcements often result in the price immediately going down.
Almost all this activity is on one exchange, BTC-E, which is the only exchange with a variety of alt-coins and the volume for a pump n dump. There have been attempts to get them going on Cryptsy, with its much wider variety of alts, but that site is so awfully coded that it runs too slowly to allow for any sort of coordinated activity.
There have been rumors that there are less public groups running pump and dumps on BTC, which would require substantially more money at this point. There's also clear signs of "dump and pumps" on BTC, where someone will sell a large amount of BTC in hopes of causing a price avalanche, and then they will buy in at the resulting cheaper price.
Given the amount of money to be made, those are almost certainly true rumors.
Having said all that, I think some of the smaller pumpers on Twitter are just looking to drive the price up on certain coins, I don't think they're necessarily looking to take advantage of their followers.
> Fontas is so infamous that his pump announcements often result in the price immediately going down.
That could be a useful trick. If you know you can consistently reduce prices, and have the capital to acquire the now cheaper commodity. Announce the scheme, prices drop, buy in. Wait for prices to recover and sell off for a profit.
According to Wikipedia 72% of the population of the USA are white, so maybe 8 in 10 is not really that much of an indication of discrimination or disadvantage. (72% boils down to "more than 7 in 10").