35 karma · joined December 1, 2011
1. OTTs negatively affect our revenue
2. OTT apps use very less data
3. OTTs earn too much
4. Net neutrality is already dead
5. Compression algorithms further reduce our profits
6. Too much freedom of expression is bad
Here's how the telecom regulatory authority of India defines OTT:"The term over-the-top (OTT) refers to applications and services which are accessible over the internet and ride on operators’ networks offering internet access services e.g. social networks, search engines, amateur video aggregation sites etc. The best known examples of OTT are Skype, Viber, WhatsApp, Chat On, Snapchat, Instagram, Kik, Google Talk, Hike, Line, WeChat, Tango, e-commerce sites (Amazon, Flipkart etc.),Ola, Facebook messenger, Black Berry Messenger, iMessage, online video games and movies (Netflix, Pandora)."
[1] http://new-digital-india.blogspot.in/2015/04/how-indian-isps...
edit: added definition of OTT
$ dig +nocmd +nostats +nocomments @218.248.255.211 archive.org
;archive.org. IN A
archive.org. 86400 IN SOA localhost. root.localhost. 1997022700 28800 14400 3600000 86400 # 218.248.255.211 is the default DNS server for BSNL DSL customers in Maharashtra, India
$ date
Thu Jan 1 20:21:02 IST 2015
$ dig +nocmd +nostats +nocomments @218.248.255.211 -f blocked.txt
;justpaste.it. IN A
justpaste.it. 86400 IN SOA localhost. root.localhost. 1997022700 28800 14400 3600000 86400
;hastebin.com. IN A
hastebin.com. 86400 IN SOA localhost. root.localhost. 1997022700 28800 14400 3600000 86400
;codepad.org. IN A
codepad.org. 86400 IN SOA localhost. root.localhost. 1997022700 28800 14400 3600000 86400
;pastie.org. IN A
pastie.org. 86400 IN SOA localhost. root.localhost. 1997022700 28800 14400 3600000 86400
;pastee.org. IN A
pastee.org. 86400 IN SOA localhost. root.localhost. 1997022700 28800 14400 3600000 86400
;paste2.org. IN A
paste2.org. 86400 IN SOA localhost. root.localhost. 1997022700 28800 14400 3600000 86400
;slexy.org. IN A
slexy.org. 86400 IN SOA localhost. root.localhost. 1997022700 28800 14400 3600000 86400
;paste4btc.com. IN A
paste4btc.com. 86400 IN SOA localhost. root.localhost. 1997022700 28800 14400 3600000 86400
;0bin.net. IN A
0bin.net. 86400 IN SOA localhost. root.localhost. 1997022700 28800 14400 3600000 86400
;www.heypasteit.com. IN A
heypasteit.com. 86400 IN SOA localhost. root.localhost. 1997022700 28800 14400 3600000 86400
;sourceforge.net. IN A
sourceforge.net. 154 IN A 216.34.181.60
sourceforge.net. 85923 IN NS ns4.p03.dynect.net.
sourceforge.net. 85923 IN NS ns3.p03.dynect.net.
sourceforge.net. 85923 IN NS ns1.p03.dynect.net.
sourceforge.net. 85923 IN NS ns2.p03.dynect.net.
ns1.p03.dynect.net. 85918 IN A 208.78.70.3
ns2.p03.dynect.net. 172323 IN A 204.13.250.3
ns3.p03.dynect.net. 85918 IN A 208.78.71.3
ns4.p03.dynect.net. 172323 IN A 204.13.251.3
;atnsoft.com. IN A
atnsoft.com. 14135 IN A 192.185.225.228
atnsoft.com. 86135 IN NS ns6616.hostgator.com.
atnsoft.com. 86135 IN NS ns6615.hostgator.com.
ns6615.hostgator.com. 172452 IN A 192.185.225.220
ns6616.hostgator.com. 172452 IN A 192.185.225.221
;archive.org. IN A
archive.org. 86400 IN SOA localhost. root.localhost. 1997022700 28800 14400 3600000 86400
;www.hpage.com. IN A
hpage.com. 86400 IN SOA localhost. root.localhost. 1997022700 28800 14400 3600000 86400
;www.ipage.com. IN A
ipage.com. 86400 IN SOA localhost. root.localhost. 1997022700 28800 14400 3600000 86400
;www.webs.com. IN A
webs.com. 86400 IN SOA localhost. root.localhost. 1997022700 28800 14400 3600000 86400
;www.weebly.com. IN A
weebly.com. 86400 IN SOA localhost. root.localhost. 1997022700 28800 14400 3600000 86400
;www.000webhost.com. IN A
000webhost.com. 86400 IN SOA localhost. root.localhost. 1997022700 28800 14400 3600000 86400
;www.freehosting.com. IN A
freehosting.com. 86400 IN SOA localhost. root.localhost. 1997022700 28800 14400 3600000 86400
;vimeo.com. IN A
vimeo.com. 86400 IN SOA localhost. root.localhost. 1997022700 28800 14400 3600000 86400
;www.dailymotion.com. IN A
dailymotion.com. 86400 IN SOA localhost. root.localhost. 1997022700 28800 14400 3600000 86400
;pastebin.com. IN A
pastebin.com. 86400 IN SOA localhost. root.localhost. 1997022700 28800 14400 3600000 86400
;gist.github.com. IN A
gist.github.com. 86400 IN SOA localhost. root.localhost. 1997022700 28800 14400 3600000 86400
;www.ipaste.eu. IN A
ipaste.eu. 86400 IN SOA localhost. root.localhost. 1997022700 28800 14400 3600000 86400
;thesnippetapp.com. IN A
thesnippetapp.com. 86400 IN SOA localhost. root.localhost. 1997022700 28800 14400 3600000 86400
;snipt.net. IN A
snipt.net. 86400 IN SOA localhost. root.localhost. 1997022700 28800 14400 3600000 86400
;tny.cz. IN A
tny.cz. 86400 IN SOA localhost. root.localhost. 1997022700 28800 14400 3600000 86400
;github.com. IN A
github.com. 86400 IN SOA localhost. root.localhost. 1997022700 28800 14400 3600000 86400
;snipplr.com. IN A
snipplr.com. 86400 IN SOA localhost. root.localhost. 1997022700 28800 14400 3600000 86400
;termbin.com. IN A
termbin.com. 86400 IN SOA localhost. root.localhost. 1997022700 28800 14400 3600000 86400
;www.snippetsource.net. IN A
snippetsource.net. 86400 IN SOA localhost. root.localhost. 1997022700 28800 14400 3600000 86400
;cryptbin.com. IN A
cryptbin.com. 86400 IN SOA localhost. root.localhost. 1997022700 28800 14400 3600000 86400There are no facts, only interpretations.
--Friedrich Nietzsche
Even a 0-byte file has metadata. Even if it is 0-byte long, GCC knows that it is reading an input file. How did it come to know? Because you communicated some amount of information by initiating the compilation.
I absolutely agree with you. You are my hero.
The amount of information stored in an object (which is capable of storing at least one bit of information in traditional sense) depends on the size of the context.
If the object is not even capable of storing one bit of information in traditional sense, then the amount of information that can be stored is zero.
And for all objects that can store one bit or more of information in traditional sense, the total amount of information that can be stored in it = the number of bits it can store + the number of bits that can be stored in rest of the universe (context). So any one bit object can store the same amount of information that can be stored in the entire universe.
And if it turns out that our universe is enclosed in yet another larger universe, then you have to include that as part of the context as well.
Edit: typo
News Article dated 27 July, 2013: http://www.thehindu.com/sci-tech/health/policy-and-issues/ne...
Definition 1: 'Good producer' is a producer that accepts bitcoins.
Definition 2: If all the good producers together produce all that you need, then the number of producers is 'enough'.
Definition 3: 'Ideal state' is when enough good producers exist.
Theorem 1: A producer will accept bitcoins if either of the following is true: i. Ideal state has been attained. ii. There exists exchanges that trade you physical currency against bitcoins.
Observation: Once we are in the ideal state, we no longer need to have bitcoins converted to physical currency. So we don't need the exchanges to exist forever. We need exchanges only till enough producers have started accepting bitcoins.
That is grossly wrong interpretation of the theorem. I stopped reading the article right there.
Software License metric: [F] Free and Open Source, [P] Proprietary/Closed source
This metric can also be modeled as a continuous variable rather than a discrete variable. But let us stick to two values for simplicity.
Development model metric: ranges from extremely [C] Cathedral-type, .........., to extremely [B] Anarchism/Bazaar-type
FOSS proponents don't care about development model as long as it's FOSS.
Let [x][y] denote the Software License metric (x) and Development model metric (y) of a software project.
Observations:
1. [P][C] is the combination that FOSS proponents hate the most.
2. [x][B] where x ∈ {F, P}; is less peer-reviewed (anyone can commit anything), so less accountability/responsibility, highly decentralized, so no guarantee of quality.
2.1. [P][B] sounds like a contradiction!
2.2. [F][B] Poul-Henning Kamp seems to have problems with this kind of setups.
3. [F][y] where y -> B (i.e. closer to [B] than it's closer to [C]). Mostly same as [F][C] except that it is mildly better.
4. [F][C] In this setup, the cathedral authority is the bottleneck in improving the project.
5. [F][y] where y -> C (i.e. closer to [C] than it's closer to [B]). This kind of setup "works like a charm!" See the overall success of GNU/Linux in the industry! There are some people who act as maintainers of Linux, but come on, you too can become one! The more popular such a software is the more thoroughly it is reviewed. "Given enough eyeballs, all bugs are shallow."
I always thought of creating a wearable device that can report the body's condition in real time. A device that can test the blood to find out amount of haemoglobin, essential minerals, sugar, cholesterol, urea, water etc. The device could be made safe enough to be inserted just below the skin, it could be made to transmit the information via radio waves to a receiver outside the body where you can read the information. We could write a program for the receiver which will process all the information and compare it to healthy values and based on it provide real time advice to the person. Eg. When you are dehydrating the receiver will say "Hey dude, drink some water quickly, or else you'll faint in 30 minutes!" "Hey dude, you should get some Vitamin B/C/D/E/K." If the circulation of blood slows down it could say "Hey you've not exercised in ages. It is time to exercise." It will redefine how we take care of ourselves. Caring in real time!