The point of the article is that the phone numbers that robocalls come from are trivially spoofed. So, it's plausible that these are real people's phones being spoofed, and it would be quite rude to them to publish…
I’d be really interested to hear more of this story! How you isolated the problem down to the level of the PSU is going deeper into the machine than I’ve personally been, so this story could be a great teacher.
The REXML patch doesn't seem to work as authored. Try qualifying the 'DocType' as 'REXML::DocType'.
Psh, obviously trigger_doomsday_device will only respond to an http POST. Once again the president has been saved, thanks to HTTP Pedantry.
Since PostgreSQL is already a well known (relational) product, I don't think that PostSQL is viable terminology.
No mention of Rackspace, Linode, or Slicehost? How about any of the bevy of newer "cloud" providers?
0.6 beta 3 is the new hotness. https://svn.apache.org/repos/asf/cassandra/tags/cassandra-0....
The point of the article is that the phone numbers that robocalls come from are trivially spoofed. So, it's plausible that these are real people's phones being spoofed, and it would be quite rude to them to publish…
I’d be really interested to hear more of this story! How you isolated the problem down to the level of the PSU is going deeper into the machine than I’ve personally been, so this story could be a great teacher.
The REXML patch doesn't seem to work as authored. Try qualifying the 'DocType' as 'REXML::DocType'.
Psh, obviously trigger_doomsday_device will only respond to an http POST. Once again the president has been saved, thanks to HTTP Pedantry.
Since PostgreSQL is already a well known (relational) product, I don't think that PostSQL is viable terminology.
No mention of Rackspace, Linode, or Slicehost? How about any of the bevy of newer "cloud" providers?
0.6 beta 3 is the new hotness. https://svn.apache.org/repos/asf/cassandra/tags/cassandra-0....