TL/DR: police had given the materials taken during the police raids to organized criminals, who used them to fraudulently reclaim $230m of the taxes previously paid by the company.
TL/DR: police had given the materials taken during the police raids to organized criminals, who used them to fraudulently reclaim $230m of the taxes previously paid by the company.
Not all government officials and police officers are the same.
Have you heard of Magnitskiy scandal in Russia? TL/DR: police had given the materials taken during the police raids to organized criminals, who used them to fraudulently reclaim $230m of the taxes previously paid by the company.
"Building out autonomous technology and having global network is a huge advantage. Because the issue with autonomy and any software, is that you've got these edge cases [...]. If you have a network live and you developing autonomy, it's not gonna go from 0 to 1, it's gonna be hybrid networks, you can answer certain calls with autonomy (the weather is good, the roads are main line, there is no traffic, no accidents, that can be served with autonomous vehicle), versus another ride that will have to be served by person."
It is dangerous. This guy's (Alexey Navalny) brother is in jail on a fabricated lawsuit as a hostage. Alexey himself was also convicted guilty and the only reason he personally is not in jail is because he will only get more rating points from being a political prisoner.
There was a massive smear campaign against him on all major government controlled mass media where they were blaming him to be an US agent and also a corrupt person.
The only reason Putin has good approval rating now is because he managed to convince the majority of TV owners in US conspiracy.
And Ukraine crisis, sanctions, ISIS, and oil price drop did actually convince majority of Russians in that.
So as long as people blame US Putin is safe.
One similar thing I see here in US: when facts are too painful and too obvious - blame another country.
Any significant Russian leak will be instantly picked up by the western media.
There is a lot of leaks on Russia in the media. No one actually cares anymore since it's mostly corruption stories and everyone is already knows there is a lot of corruption there.
Here is the last corruption story on prime minister Medvedev: https://navalny.com/p/5255/
He hiding from the United States in Ecuadorian Embassy for many years. No surprise he is biased against US.
Unites States pretends to be the country that does 'good' things, and blames all other countries that do 'bad' things. That's why Snowden is so painful, and Assange is so painful.
I don't really get the comparison with Pony Express part. As you said they shut down because of superior technology (transcontinental telegraph). So the superior technology to Uber and Lyft will be self-driving cars or teleportation.
The second point is that Uber is not trying to scale driver's earnings but the availability of the service for your every day needs while still making sure drivers can make a living. How many people were commuting to work via taxi before Uber and Lyft? How many people do that now? Making uber ride affordable for every day needs and maintain a certain level of service and customer support that's where they were scaling.
"The deal with Didi Chuxing comes just days after China agreed to provide a legal framework for taxi-ordering apps.
Both Uber and Didi have welcomed the decision, having previously operated in a legal grey area in the country.
While the apps are widely popular, they have undermined business for normal taxis and have been met with protests by cab drivers.
The new rules will take effect on 1 November and will, among other things, forbid such platforms to operate below cost."
New regulation prohibits ride subsidizing. Meaning no way for Uber to increase its market share by subsidizing rides after November 1st.
It would only trigger compaction if sst tables have overlapping keys. And if you only write new items, goleveldb implementation would just create 3.7Mb sst tables by default without trying to merge them into bigger chunks (what's the point? they are all sorted and non-overlapping). When you have queue consumption workload it would start merging tombstones with sst tables and since tombstones are also in sorted order it would not pick up multiple sst tables at a time, and just either completely or partially remove stale sst files. I added some more benchmarks including queue packing with 200M messages of 64 byte size, and benchmarks of consumption of 200M messages. The speed is sustainable. https://github.com/bogdanovich/siberite/blob/master/docs/ben...
In case of reliable fetch failure each consumer group will keep it's own queue of failed deliveries (persisted on disk), will check that queue and serve these failed items first.
Right now it doesn't store any consumer offsets. And you can get either at-most-once or at-least-once guarantees.
But I found the idea of multiple consumer groups per queue very interesting. So basically you would still be able to fetch queue messages as you can do now and it will delete dequeued items, but you would also be able to use something like
'get queue_name:consumer_name'
and it will create a consumer group internally with a stored offset and will serve messages using that offset. In case of reliable read failure each consumer group will keep it's own queue of failed deliveries, will check that queue and serve these failed items first. If source queue head has changed and became larger then consumer group offset, then consumer group offset would just start from the source queue head.
This way you can get Kafka-like multiple consumer groups per queue as an additional feature.
It's really simple. Each queue is a separate leveldb database on disk. Messages are stored as key/value using incremental ids. Head and tail of the queue are kept in memory and get initialized on startup via db scan.
Yes, goleveldb was chosen because it's a ready to use library with a decent write and read performance, and no external non-Go dependencies. It can also be used to store multiple consumers offsets in future.
Regarding provided guarantees, with simple 'get work_queue' reads it provides at-most-once delivery. With two phase reliable reads 'get work_queue/open', 'get work_queue/close' it provides at-least-once delivery (although message is kept in memory on server during a reliable read and will be lost if you SIGKILL siberite. On SIGTERM and SIGINT siberite will gracefully abort the read and save the message).
https://en.wikipedia.org/wiki/Sergei_Magnitsky#Exposing_the_...
TL/DR: police had given the materials taken during the police raids to organized criminals, who used them to fraudulently reclaim $230m of the taxes previously paid by the company.