risavkarna

{
    "contributors": null,
    "coordinates": null,
    "in_reply_to_user_id": null,
    "truncated": false,
    "text": "#VerguenzaK los aplaudidores y reidores de la presidentA",
    "entities": {
        "hashtags": [
            {
                "text": "VerguenzaK",

risavkarna

SET SCHEMA CHALLENGE3;

DROP TYPE UNKNOWN_TWEET_T;
CREATE TYPE UNKNOWN_TWEET_T AS TABLE 
(	
  "ID" BIGINT NOT NULL,							-- Unique identifier for this Tweet
  "TEXT" nvarchar(800) NOT NULL,            	-- The actual text of the status update
  "TRUNCATED" TINYINT NOT NULL default 0,  		-- (1 = True, 0 = False) Indicates whether the text was truncated, for example, as a result of a retweet exceeding the 140 character Tweet length. Truncated text will end in ellipsis, like this ... 
  "SOURCE" nvarchar(255),                   	-- Utility used to post the Tweet, as an HTML-formatted string. (e.g. 'web')
  "CREATED_AT" DATETIME not null,				-- UTC time when this Tweet was created.

risavkarna

SET SCHEMA CHALLENGE3;

DROP TYPE UNKNOWN_TWEET_T;
CREATE TYPE UNKNOWN_TWEET_T AS TABLE 
(	
  "ID" BIGINT NOT NULL,							-- Unique identifier for this Tweet
  "TEXT" nvarchar(800) NOT NULL,            	-- The actual text of the status update
  "TRUNCATED" TINYINT NOT NULL default 0,  		-- (1 = True, 0 = False) Indicates whether the text was truncated, for example, as a result of a retweet exceeding the 140 character Tweet length. Truncated text will end in ellipsis, like this ... 
  "SOURCE" nvarchar(255),                   	-- Utility used to post the Tweet, as an HTML-formatted string. (e.g. 'web')
  "CREATED_AT" DATETIME not null,				-- UTC time when this Tweet was created.

risavkarna

SET SCHEMA CHALLENGE3;

DROP TYPE UNKNOWN_TWEET_T;
CREATE TYPE UNKNOWN_TWEET_T AS TABLE 
(	
  "ID" BIGINT NOT NULL,							-- Unique identifier for this Tweet
  "TEXT" nvarchar(800) NOT NULL,            	-- The actual text of the status update
  "TRUNCATED" TINYINT NOT NULL default 0,  		-- (1 = True, 0 = False) Indicates whether the text was truncated, for example, as a result of a retweet exceeding the 140 character Tweet length. Truncated text will end in ellipsis, like this ... 
  "SOURCE" nvarchar(255),                   	-- Utility used to post the Tweet, as an HTML-formatted string. (e.g. 'web')
  "CREATED_AT" DATETIME not null,				-- UTC time when this Tweet was created.

risavkarna

SET SCHEMA CHALLENGE3;

DROP TYPE UNKNOWN_TWEET_T;
CREATE TYPE UNKNOWN_TWEET_T AS TABLE 
(	
  "ID" BIGINT NOT NULL,							-- Unique identifier for this Tweet
  "TEXT" nvarchar(800) NOT NULL,            	-- The actual text of the status update
  "TRUNCATED" TINYINT NOT NULL default 0,  		-- (1 = True, 0 = False) Indicates whether the text was truncated, for example, as a result of a retweet exceeding the 140 character Tweet length. Truncated text will end in ellipsis, like this ... 
  "SOURCE" nvarchar(255),                   	-- Utility used to post the Tweet, as an HTML-formatted string. (e.g. 'web')
  "CREATED_AT" DATETIME not null,				-- UTC time when this Tweet was created.

risavkarna

package hw1.rwFileSystemFile;


import java.io.BufferedReader;
import java.io.IOException;
import java.nio.charset.Charset;
import java.nio.charset.StandardCharsets;
import java.nio.file.Files;
import java.nio.file.Path;
import java.nio.file.Paths;

risavkarna

int SpaceObjectRegister::getValue(void* value, std::string name){
  string objtype = name.substr(0, name.find('['));
	string id_type = name.substr(name.find('[')+1, name.find(']')-name.find('[')-1);
	int index = atoi(id_type.c_str());
	void* _value;
	varsRegister->getValue(_value, id_type);

	ArgumentType _type;
	if (objtype == "Martians") {
		if(*(int*) varsRegister >= 0 && *(int*) varsRegister < Martians.size()){

risavkarna

OpenSSH_5.2p1, OpenSSL 0.9.8r 8 Feb 2011
debug1: Reading configuration data /Users/risav/.ssh/config
debug1: Applying options for 172.18.240.*
debug1: Reading configuration data /etc/ssh_config
debug2: ssh_connect: needpriv 0
debug1: Executing proxy command: exec ssh rkin2@ssh.be-ibbt.bonfire-project.eu "nc 172.18.240.58 22"
debug3: Not a RSA1 key file /Users/risav/.ssh/id_dsa.
debug2: key_type_from_name: unknown key type '-----BEGIN'
debug3: key_read: missing keytype
debug3: key_read: missing whitespace

risavkarna

OpenSSH_5.2p1, OpenSSL 0.9.8r 8 Feb 2011
debug1: Reading configuration data /Users/risav/.ssh/config
debug1: Applying options for 172.18.4.*
debug1: Reading configuration data /etc/ssh_config
debug2: ssh_connect: needpriv 0
debug1: Executing proxy command: exec ssh rkin2@ssh.be-ibbt.bonfire-project.eu "nc 172.18.4.195 22"
debug3: Not a RSA1 key file /Users/risav/.ssh/id_dsa.
debug2: key_type_from_name: unknown key type '-----BEGIN'
debug3: key_read: missing keytype
debug3: key_read: missing whitespace

risavkarna

CoPla System: A Pervasive Collaboration Platform

================================================

/etc/init.d/discussion start

This md is a bunch of notes I have regarding my original plans for a django+spring powered Collaboration Platform (CoPla), its semi-open platform to build the CoPla (Meta*CoPla) and the unique networking support (CoPlanet) essential to the CoPla at a later stage. Apart from these three, there could also be a blog to showcase or publish the highlights and achievements of CoPla (ShoPla?).These awful names can be changed if you suggest better ones. This body of text only contains a high level description of the current vision and shall be updated with similar content alongside other more formal documentations.

• Only the gist of these ideas is final, everything else is upto our group to realize or discard. Even the core idea is open to discussion if needed.
• Like the code for Emacs was written in Emacs, CoPla has to be written in (Meta)CoPla.. so let's get started on ma