sespindola

Also here in Argentina we have Banco Credicoop, which is a credit union with more than 670,000 members.

https://en.wikipedia.org/wiki/Banco_Credicoop

Forgot the links:

[1]: http://www.ettus.com/product/details/USRPPKG [2]: http://wush.net/trac/rangepublic/wiki/freeswitchConfig

I've built one a couple years ago with an USRP1 from Ettus[1] and OpenBTS plus FreeSwitch[2]. It's pretty straightforward if you know what you're doing.

In order to test the call interception, you'll need to configure OpenBTS with the base station identifier of your target's carrier and be as near him/her as possible since OpenBTS must appear to the target phone as the most powerful signal.

Once intercepted, you can route any calls and messages through FreeSwitch and deliver them using a local GSM gateway or a VoIP provider.

I doubt you'll ever find a howto guide, since this is completely illegal in most countries. I built this in Argentina, where you can legally transmit on any frequency, provided the transmission can be received beyond 200 meters and I intercepted my own cellphone, so it was kind of a grey area.

In my experience, hosted database providers are almost always either cost or latency prohibitive.

Nowadays, in PostgreSQL is quite simple to replicate a db via log shipping[1]. You can even stream the WAL to an S3 bucket.

[1]: http://www.postgresql.org/docs/9.3/static/warm-standby.html

I somehow doubt that GCHQ geeks read anti-modernist manifestos.

Depending on the age of the name pickers, I'd say they either went to the Hacienda nightclub at Manchester or saw 24 hours party people[1].

1: http://www.imdb.com/title/tt0274309/

I'm currently a fellow IBMer.

Go to w3, search for "approved OS" and take your pick. I'm currently running fedora 20 with mate desktop. Works like a charm on a T430.

They're probably using DASH[1]. The video is split into several segments and therefore the player will fill the bufer only until the end of the current segment.

Below each codeschool video you have a download link, so you can view them offline.

[1]: http://en.wikipedia.org/wiki/Dynamic_Adaptive_Streaming_over...

some physicists at Sandia labs have been working on a similar technology: the counter rotating ring receiver reactor recuperator, or CR5[1]. Though it seems to be a long way from reaching the necessary efficiency for it to be comercially viable.

It was festured in Daniel Suarez's Freedom, as the main fuel generator for a native self-sustaining community.

[1] https://share.sandia.gov/news/resources/releases/2007/sunshi...

Regretably, unless some sort of worldwide ethical commerce treaty is established in the near future, a "foxconnified" workforce will be a basic requirement in order to mass produce anything, anwywhere in the world.

Except that, in that case, Apple will loose a lot of money from the free hardware. In this case, the only real loss for EA is the bandwidth. Since it would be safe to asume that the downloaders wouldn't have bought a lot of games at the current prices.

Interesting hack.

As some of the MMORPGs have multi-million dollar economies, they'll need to increase their PCI level compliance.

This reminds me of Charlie Stross's Halting State[1].

1: http://en.wikipedia.org/wiki/Halting_State

Great movie. In 1998 the EFF built a DES cracking machine like the one depicted in the movie[1].

Though it took 9 days to run through the whole DES cypher space, instead of doing it in real-time.

1: http://en.wikipedia.org/wiki/EFF_DES_cracker

All (or most) comercial planes also have an amber LED alarm on the caution panel that says PITOT when the PITOT HEAT switch is turned off.

If that alarm was functional and activated before they entered that stall profile, it was, in my opinion, some serious misjudgement by the pilots not to turn the pitot heat on.

But then again, I've only flown a PA-38 on storm conditions, so take this with a huge grain of salt.

You can also find them in the movie. If I recall correctly, they were used by someone on the orbital Hilton and by the astronauts on the discovery.

Samsung recently used the movie as evidence of prior art against apple [1].

[1]: http://appadvice.com/appnn/2011/08/samsung-uses-2010-a-space...

Yes but, in the case of android, the assembly work is rather trivial if they wanted to offer a standard android rom.

Most of the complexity lies in the gui elements added by the manufacturers (TouchWiz, HTC Sense, etc) in an attempt to differentiate themselves from the rest and foster brand loyalty.

In any case, I don't think the software customization cost per unit in android phones it's anywhere near those MS license costs.

I disagree. I think we're heading to a "Huxleyan" distopia were any "Spring" or uprising can be preempted by promoting rampant consumerism and the infinite distractions of the internet.

Food for thought: http://www.prosebeforehos.com/image-of-the-day/08/24/huxley-...

This. Most tutorials of Backbone/Ember js apps I've seen have thin backends that commit any json objects the clients send them.

Data sanitization and validation on the backend should be as thourough as that of the client, if not more.

Given Nauru's isolation and exposure to the elements, I'd rather install a couple 7.5MW Enercom wind turbines, a few MW worth of solar panels and maybe a tidal generator instead of a nuclear reactor.

The risk reduction is negligible if someone is doing a portscan on your host. Connection attempts to non standard ports will eventually occur. The better solution is to use single packet authorization.[1]

1. http://cipherdyne.org/fwknop/

Most ISP's dns cache servers honor the TTL defined in the authoritative SOA records, unless is 1 minute or less.

I think the average TTL time for a dns zone would be measured in minutes. It needs to be that low in order to do SRV load-balancing, A/B testing, etc.

In any case, in the highly unlikely event that they manage to overload the 13 servers, there's plenty of time for every domain to temporarily extend the TTL on March 31.

Here.[1] Most of them are not single-box servers, but cluster with multisite redundancy. That's why all attacks were unsuccessful in the past.

1. http://en.wikipedia.org/wiki/Root_name_server

As mentioned on the article's comments, when I used XFS about 8 years ago, I found exceptionally prone to data corruption.

It remains the only filesystem that I couldn't at least partially recover.

For a good mix of speed, reliability and huge data capacity on Linux, I stick to ReiserFS, at least until btrfs becomes more stable.

BeOS could have been an alternative in the middle to late 90's. If only Microsoft hadn't utterly kill it by threatening hardwave vendors who considered offering it with cancelling their OEM agreements.

We already have the EFF[1]. Maybe we should consider donating to it.

[1]: https://www.eff.org/helpout

As long as you're using TOR to connect to any regular site, your traffic will eventually exit the TOR network through an exit node. If that node's ISP performs packet inspection and traffic originating from it ends up hitting an URL for illegal content on a download site, the exit node could be taken down and it's owner prosecuted.

Only hidden services using the .onion alternate TLD are safe.

Except that if the RIAA could/would actually put a musician out of bussiness, that musician could do another line of work to earn enough money to eat.

What Monsanto is doing, basically, is redisigning crops to work on their behalf. Whenever a crop can develop properly due to the proliferation of roundup resistant weeds, you have to buy the newest crop from them again, wether you like it or not.

Also there is the (theoretical) risk that someday they won't be able to keep up with resistance, which could curtail food supply, and won't make a difference wether you can purchase it or not.

It is, from an absolute standpoint.

But if people all around the world and from every angle of the ideological spectrum universally vilifies a corporation, I think it would merit to look into their affairs with suspicion.

As an Argentinian, here are my two cents on this matter:

1) From reading this article, one could asume commercial and financial regulations change by the hour, while in fact is the opposite.

   We have a gargantuan commercial code of byzantine
   complexity that has not really been modified in the
   last 50 years.

   We also have a terribly regressive and unfair tax
   system that includes 21% VAT even for food products
   and wealth tax even for salaried employees with 
   more than 1400 dollars of monthly income.

2) It is my sincere wish, from the bottom of my heart, that "entrepreneurs" (I doubt they deserve the honor if being called that) who operate "en negro" rot in jail. They are bringing all of us down with their disregard for the rule of law and they are increasing the costs of doing bussiness for those of us who pay taxes.

   Regardless of the recurrent crises, starting up a 
   successful tech company here is possible, as proven
   by Globant, OfficeNet, MercadoLibre, et al.

If you're using exclusively AWS, you should have instances in 2 different regions, at least.

Instead of relying on the elastic load balancer, you should be doing load balancing with DNS using SRV records.

If you are using SRV records and you are at the beginning of what seems to be a serious downtime, you can set all the weight of your SRV records to the instances in the healthy AZ.

In the backend, if you're using SQL, you should use a DB with a WAL-based async replication, like Postgresql.

In PostgreSQL 9, you have streaming replication integrated to the DB. If using PostgreSQL 8, you could use third party apps, like Slony-1 or PG-Pool II.

In the NoSQL databases, there seems to be a "last write wins" effect. Even in distributed beasts like Cassandra. So if you are running a NoSQL cluster, you need to determine which nodes received the most data during the outage and repair from there.

Speaking as someone who used to write Zope 2 apps, allow me to say no. Hell, no.

Zope < 3.0 was a convoluted mess of two over-engineered applications named Bobo and Principia that were hacked together.

That's why the API had functions names like:

  bobobase_modification_time 
  principia_is_folderish

That's why Zope 3 was rewritten from scratch.

Zope 3 has a sane, albeit complex, architecture. Regretably it came too late into the game and by the time it was ready, every Python web developer had moved to turbogears or something else.

The only interesting piece of technology from Zope was the ZODB. I wish it had developed as a separate product.