Quantcast
Channel: NodeXL: Network Overview, Discovery and Exploration for Excel
Viewing all 4386 articles
Browse latest View live
↧

New Post: Calculating pagerank in NodeXL

August 6, 2013, 9:20 am
$
0
0
Tony

Thanks for the advice. I still may be able use NodeXL but being able to vary the convergence criteria is useful.

Martin O'Shea.
↧
Search

Updated Wiki: CompleteReleaseHistory

August 7, 2013, 8:38 am
$
0
0

Complete NodeXL Release History

1.0.1.247 (2013-08-02)
  • If you import a Twitter search network and tell NodeXL to calculate Twitter search network top items (NodeXL, Analysis, Graph Metrics), then the following columns now get added to the Vertices worksheet: Top URLs in Tweet by Count, Top URLs in Tweet by Salience, Top Domains in Tweet by Count, Top Domains in Tweet by Salience, Top Hashtags in Tweet by Count, Top Hashtags in Tweet by Salience, Top Words in Tweet by Count, Top Words in Tweet by Salience, Top Word Pairs in Tweet by Count, Top Word Pairs in Tweet by Salience.
  • When importing a Twitter network, if Twitter unexpectedly closes the network connection, then NodeXL will now try to reestablish the connection. (The symptom of this problem is a message that includes the text "[IOException]: Unable to read data from the transport connection: The connection was closed.")

1.0.1.246 (2013-07-19)
  • An importer for a new Graph Server has been added. The Graph Server is currently private.
  • Bug fix: If you used NodeXL, Analysis, Subgraph Images and one of your vertices had a name that was "reserved" by Windows (con, lpt, nul, and several others), you would get an error message that included the text "[ExternalException]: A generic error occurred in GDI+". Note that subgraph image file names now always start with "Img-", as in "Img-con.png".

1.0.1.245 (2013-06-19)
  • This release wraps up a set of enhancements and bug fixes that were previously included in a series of experimental private releases. All changes since the last public release (1.0.1.238) have to do with importing Twitter networks.
  • An experiment involving "shared term" edges in the Twitter search network is still in progress, and those edges are not included in this release. (They were not included in version 1.0.1.244, either.)
  • This release is functionally identical to version 1.0.1.244.

1.0.1.244 (2013-06-17, private release)
  • In the Twitter search network, vertices are now added to the graph for people who were replied to or mentioned by the people who actually tweeted the specified term.
  • Bug fix: In the Twitter networks, if you checked "Expand URLs in tweets" and a malformed URL was provided by Twitter, you would get a "Partial Network" message and then the graph would have no edges. The Partial Network details included the text "[UriFormatException]: Invalid URI: The format of the URI could not be determined". Now, NodeXL doesn't attempt to expand the bad URL.
  • Bug fix: When getting a Twitter search network, you would sometimes get a "Partial Network" message with details that included the text "[KeyNotFoundException]: The given key was not present in the dictionary." (This was caused by Twitter giving NodeXL a tweet that included no information about the tweeter. NodeXL now ignores such tweets.)

1.0.1.243 (2013-05-19, private release)
  • The Twitter Search Network now uses experimental shared term thresholds. This is part of an effort to obtain meaningful edges without running into Twitter's new rate limits.

1.0.1.242 (2013-05-01, private release)
  • The shared word user threshold can now be specified in the network configuration file used by the Network Server program. (For advanced users of private releases only.)
  • Bug fix: If you specified shared hashtag, URL, word, or word pair edge relationships in the Import from Twitter Search Network dialog box, the graph summary (NodeXL, Graph, Summary) did not mention the fact that the graph included those edges. (Private releases only.)

1.0.1.241 (2013-04-25, private release)
  • Bug fix: If you imported a Twitter network that included the empty hyperlink "http://" somewhere in the network's text, Excel would refuse to save the workbook. The error message started with "Errors were detected while saving..." This is an Excel bug that will also arise if you type "http://" directly into a cell. This change does not fix the latter problem.

1.0.1.240 (2013-04-24, private release)
  • If you check "add statistic columns to the Vertices worksheet" in the Import from Twitter Search Network dialog box, no additional time will be required to get the network. This used to require additional Twitter requests, and it was marked as "slower" in the dialog box.

1.0.1.239 (2013-04-08, private release)
  • Same as 1.0.1.238, but with additional edge options.

1.0.1.238 (2013-04-08)
  • Bug fix: In versions 1.0.1.236 and 237, if you entered a space (or a colon, or a few other special characters) into the "Add a vertex for each..." textbox on the Import from Twitter Search Network dialog box, you would get a message that included the text, "The Twitter Web service refused to provide the requested information."

1.0.1.237 (2013-03-25, private release)
  • Same as 1.0.1.236, but with additional edge options.

1.0.1.236 (2013-03-25)
  • There are some major changes in NodeXL's Twitter importers. See Changes in NodeXL's Twitter Importers for more information.
  • When you use dynamic filters (NodeXL, Analysis, Dynamic Filters), filtering an edge will automatically filter its adjacent vertices if the filtering causes those vertices to become isolates.
  • If you set the Visibility of vertex X to "Skip" and vertex X has adjacent vertices that are connected only to vertex X, then those adjacent vertices are now skipped as well. Previously, the adjacent vertices would remain in the graph as isolates.
  • For programmers: The NodeXL source code is now available on the CodePlex "Source Code" tab. The source code will no longer be provided as separate releases on the Downloads tab.
Go to Page 2 >>

↧
↧

Created Unassigned: twitter import auth 1.0.1.245 [24594]

August 7, 2013, 2:19 pm
$
0
0
hello there -
i recently upgraded to 1.0.1.245 on my xp machine.
when i attempt to import from user search network i am forced to authorize
when i launch this a get a pop-up from excel saying 'access is denied' and the detail text is repeating )))))))))'s.

thought it was a browser issue but have since disabled any blockers.
any thoughts would be welcome ... perhaps theres a log i can provide?

thanks.
↧

Updated Wiki: CompleteReleaseHistory

August 7, 2013, 9:16 pm
$
0
0

Complete NodeXL Release History

1.0.1.248 (In progress)
  • If you import a network from the NodeXL Graph Server, the graph summary (NodeXL, Graph, Summary) now includes more information, including the date range of the tweets in the network.
  • The Data Import section of the Graph Summary for all Twitter, YouTube and Flickr network is now broken into paragraphs for clarity.

1.0.1.247 (2013-08-02)
  • If you import a Twitter search network and tell NodeXL to calculate Twitter search network top items (NodeXL, Analysis, Graph Metrics), then the following columns now get added to the Vertices worksheet: Top URLs in Tweet by Count, Top URLs in Tweet by Salience, Top Domains in Tweet by Count, Top Domains in Tweet by Salience, Top Hashtags in Tweet by Count, Top Hashtags in Tweet by Salience, Top Words in Tweet by Count, Top Words in Tweet by Salience, Top Word Pairs in Tweet by Count, Top Word Pairs in Tweet by Salience.
  • When importing a Twitter network, if Twitter unexpectedly closes the network connection, then NodeXL will now try to reestablish the connection. (The symptom of this problem is a message that includes the text "[IOException]: Unable to read data from the transport connection: The connection was closed.")

1.0.1.246 (2013-07-19)
  • An importer for a new Graph Server has been added. The Graph Server is currently private.
  • Bug fix: If you used NodeXL, Analysis, Subgraph Images and one of your vertices had a name that was "reserved" by Windows (con, lpt, nul, and several others), you would get an error message that included the text "[ExternalException]: A generic error occurred in GDI+". Note that subgraph image file names now always start with "Img-", as in "Img-con.png".

1.0.1.245 (2013-06-19)
  • This release wraps up a set of enhancements and bug fixes that were previously included in a series of experimental private releases. All changes since the last public release (1.0.1.238) have to do with importing Twitter networks.
  • An experiment involving "shared term" edges in the Twitter search network is still in progress, and those edges are not included in this release. (They were not included in version 1.0.1.244, either.)
  • This release is functionally identical to version 1.0.1.244.

1.0.1.244 (2013-06-17, private release)
  • In the Twitter search network, vertices are now added to the graph for people who were replied to or mentioned by the people who actually tweeted the specified term.
  • Bug fix: In the Twitter networks, if you checked "Expand URLs in tweets" and a malformed URL was provided by Twitter, you would get a "Partial Network" message and then the graph would have no edges. The Partial Network details included the text "[UriFormatException]: Invalid URI: The format of the URI could not be determined". Now, NodeXL doesn't attempt to expand the bad URL.
  • Bug fix: When getting a Twitter search network, you would sometimes get a "Partial Network" message with details that included the text "[KeyNotFoundException]: The given key was not present in the dictionary." (This was caused by Twitter giving NodeXL a tweet that included no information about the tweeter. NodeXL now ignores such tweets.)

1.0.1.243 (2013-05-19, private release)
  • The Twitter Search Network now uses experimental shared term thresholds. This is part of an effort to obtain meaningful edges without running into Twitter's new rate limits.

1.0.1.242 (2013-05-01, private release)
  • The shared word user threshold can now be specified in the network configuration file used by the Network Server program. (For advanced users of private releases only.)
  • Bug fix: If you specified shared hashtag, URL, word, or word pair edge relationships in the Import from Twitter Search Network dialog box, the graph summary (NodeXL, Graph, Summary) did not mention the fact that the graph included those edges. (Private releases only.)

1.0.1.241 (2013-04-25, private release)
  • Bug fix: If you imported a Twitter network that included the empty hyperlink "http://" somewhere in the network's text, Excel would refuse to save the workbook. The error message started with "Errors were detected while saving..." This is an Excel bug that will also arise if you type "http://" directly into a cell. This change does not fix the latter problem.

1.0.1.240 (2013-04-24, private release)
  • If you check "add statistic columns to the Vertices worksheet" in the Import from Twitter Search Network dialog box, no additional time will be required to get the network. This used to require additional Twitter requests, and it was marked as "slower" in the dialog box.

1.0.1.239 (2013-04-08, private release)
  • Same as 1.0.1.238, but with additional edge options.

1.0.1.238 (2013-04-08)
  • Bug fix: In versions 1.0.1.236 and 237, if you entered a space (or a colon, or a few other special characters) into the "Add a vertex for each..." textbox on the Import from Twitter Search Network dialog box, you would get a message that included the text, "The Twitter Web service refused to provide the requested information."

1.0.1.237 (2013-03-25, private release)
  • Same as 1.0.1.236, but with additional edge options.

1.0.1.236 (2013-03-25)
  • There are some major changes in NodeXL's Twitter importers. See Changes in NodeXL's Twitter Importers for more information.
  • When you use dynamic filters (NodeXL, Analysis, Dynamic Filters), filtering an edge will automatically filter its adjacent vertices if the filtering causes those vertices to become isolates.
  • If you set the Visibility of vertex X to "Skip" and vertex X has adjacent vertices that are connected only to vertex X, then those adjacent vertices are now skipped as well. Previously, the adjacent vertices would remain in the graph as isolates.
  • For programmers: The NodeXL source code is now available on the CodePlex "Source Code" tab. The source code will no longer be provided as separate releases on the Downloads tab.
Go to Page 2 >>

↧

Commented Unassigned: twitter import auth 1.0.1.245 [24594]

August 8, 2013, 8:47 am
$
0
0
hello there -
i recently upgraded to 1.0.1.245 on my xp machine running excel 2010.
when i attempt to import from user search network i am forced to authorize
when i launch this a get a pop-up from excel saying 'access is denied' and the detail text is repeating )))))))))'s.

thought it was a browser issue but have since disabled any blockers.
any thoughts would be welcome ... perhaps theres a log i can provide?

thanks.
Comments: ** Comment from web user: tcap479 **

When you select the "...Take me to Twitter's authorization page" option in an Import from Twitter dialog box, NodeXL has to open the page in a new browser window. Something on your computer is preventing that page from opening.

As an experiment to try to narrow down the problem, please try this:

1. Open the Windows Start menu.

2. In the Windows Start menu, select "Run".

3. In the Run dialog box, enter the following URL and click OK:

https://api.twitter.com/oauth/authorize

A web page that says "Whoa there!" should open in a new browser window. Does that happen?

-- Tony

↧
↧

Updated Wiki: CompleteReleaseHistory

August 8, 2013, 9:50 am
$
0
0

Complete NodeXL Release History

1.0.1.248 (In progress)
  • If you import a network from the NodeXL Graph Server, the graph summary (NodeXL, Graph, Summary) now includes more information, including the date range of the tweets in the network.
  • The Data Import section of the Graph Summary for all Twitter, YouTube and Flickr network is now broken into paragraphs for clarity.
  • NodeXL will now pause for an extra 15 seconds when Twitter rate limits are reached. This is an attempt to work around a problem where Twitter occasionally refuses to provide more information even after NodeXL pauses for the time specified by Twitter. The symptom of that problem is a message that includes the text "A likely cause is that you have made too many Twitter requests in the last 15 minutes." (This might not fix the problem, because the problem's cause is unknown.)

1.0.1.247 (2013-08-02)
  • If you import a Twitter search network and tell NodeXL to calculate Twitter search network top items (NodeXL, Analysis, Graph Metrics), then the following columns now get added to the Vertices worksheet: Top URLs in Tweet by Count, Top URLs in Tweet by Salience, Top Domains in Tweet by Count, Top Domains in Tweet by Salience, Top Hashtags in Tweet by Count, Top Hashtags in Tweet by Salience, Top Words in Tweet by Count, Top Words in Tweet by Salience, Top Word Pairs in Tweet by Count, Top Word Pairs in Tweet by Salience.
  • When importing a Twitter network, if Twitter unexpectedly closes the network connection, then NodeXL will now try to reestablish the connection. (The symptom of this problem is a message that includes the text "[IOException]: Unable to read data from the transport connection: The connection was closed.")

1.0.1.246 (2013-07-19)
  • An importer for a new Graph Server has been added. The Graph Server is currently private.
  • Bug fix: If you used NodeXL, Analysis, Subgraph Images and one of your vertices had a name that was "reserved" by Windows (con, lpt, nul, and several others), you would get an error message that included the text "[ExternalException]: A generic error occurred in GDI+". Note that subgraph image file names now always start with "Img-", as in "Img-con.png".

1.0.1.245 (2013-06-19)
  • This release wraps up a set of enhancements and bug fixes that were previously included in a series of experimental private releases. All changes since the last public release (1.0.1.238) have to do with importing Twitter networks.
  • An experiment involving "shared term" edges in the Twitter search network is still in progress, and those edges are not included in this release. (They were not included in version 1.0.1.244, either.)
  • This release is functionally identical to version 1.0.1.244.

1.0.1.244 (2013-06-17, private release)
  • In the Twitter search network, vertices are now added to the graph for people who were replied to or mentioned by the people who actually tweeted the specified term.
  • Bug fix: In the Twitter networks, if you checked "Expand URLs in tweets" and a malformed URL was provided by Twitter, you would get a "Partial Network" message and then the graph would have no edges. The Partial Network details included the text "[UriFormatException]: Invalid URI: The format of the URI could not be determined". Now, NodeXL doesn't attempt to expand the bad URL.
  • Bug fix: When getting a Twitter search network, you would sometimes get a "Partial Network" message with details that included the text "[KeyNotFoundException]: The given key was not present in the dictionary." (This was caused by Twitter giving NodeXL a tweet that included no information about the tweeter. NodeXL now ignores such tweets.)

1.0.1.243 (2013-05-19, private release)
  • The Twitter Search Network now uses experimental shared term thresholds. This is part of an effort to obtain meaningful edges without running into Twitter's new rate limits.

1.0.1.242 (2013-05-01, private release)
  • The shared word user threshold can now be specified in the network configuration file used by the Network Server program. (For advanced users of private releases only.)
  • Bug fix: If you specified shared hashtag, URL, word, or word pair edge relationships in the Import from Twitter Search Network dialog box, the graph summary (NodeXL, Graph, Summary) did not mention the fact that the graph included those edges. (Private releases only.)

1.0.1.241 (2013-04-25, private release)
  • Bug fix: If you imported a Twitter network that included the empty hyperlink "http://" somewhere in the network's text, Excel would refuse to save the workbook. The error message started with "Errors were detected while saving..." This is an Excel bug that will also arise if you type "http://" directly into a cell. This change does not fix the latter problem.

1.0.1.240 (2013-04-24, private release)
  • If you check "add statistic columns to the Vertices worksheet" in the Import from Twitter Search Network dialog box, no additional time will be required to get the network. This used to require additional Twitter requests, and it was marked as "slower" in the dialog box.

1.0.1.239 (2013-04-08, private release)
  • Same as 1.0.1.238, but with additional edge options.

1.0.1.238 (2013-04-08)
  • Bug fix: In versions 1.0.1.236 and 237, if you entered a space (or a colon, or a few other special characters) into the "Add a vertex for each..." textbox on the Import from Twitter Search Network dialog box, you would get a message that included the text, "The Twitter Web service refused to provide the requested information."

1.0.1.237 (2013-03-25, private release)
  • Same as 1.0.1.236, but with additional edge options.

1.0.1.236 (2013-03-25)
  • There are some major changes in NodeXL's Twitter importers. See Changes in NodeXL's Twitter Importers for more information.
  • When you use dynamic filters (NodeXL, Analysis, Dynamic Filters), filtering an edge will automatically filter its adjacent vertices if the filtering causes those vertices to become isolates.
  • If you set the Visibility of vertex X to "Skip" and vertex X has adjacent vertices that are connected only to vertex X, then those adjacent vertices are now skipped as well. Previously, the adjacent vertices would remain in the graph as isolates.
  • For programmers: The NodeXL source code is now available on the CodePlex "Source Code" tab. The source code will no longer be provided as separate releases on the Downloads tab.
Go to Page 2 >>

↧

Updated Wiki: CompleteReleaseHistory

August 8, 2013, 9:51 am
$
0
0

Complete NodeXL Release History

1.0.1.248 (In progress)
  • If you import a network from the NodeXL Graph Server, the graph summary (NodeXL, Graph, Summary) now includes more information, including the date range of the tweets in the network.
  • The Data Import section of the Graph Summary for all Twitter, YouTube and Flickr network is now broken into paragraphs for clarity.
  • NodeXL will now pause for an extra 15 seconds when Twitter rate limits are reached. This is an attempt to work around a problem where Twitter occasionally refuses to provide more information even after NodeXL pauses for the time specified by Twitter. The symptom of that problem is a message that includes the text "A likely cause is that you have made too many Twitter requests in the last 15 minutes." (This might not fix the problem, the cause of which is unknown.)

1.0.1.247 (2013-08-02)
  • If you import a Twitter search network and tell NodeXL to calculate Twitter search network top items (NodeXL, Analysis, Graph Metrics), then the following columns now get added to the Vertices worksheet: Top URLs in Tweet by Count, Top URLs in Tweet by Salience, Top Domains in Tweet by Count, Top Domains in Tweet by Salience, Top Hashtags in Tweet by Count, Top Hashtags in Tweet by Salience, Top Words in Tweet by Count, Top Words in Tweet by Salience, Top Word Pairs in Tweet by Count, Top Word Pairs in Tweet by Salience.
  • When importing a Twitter network, if Twitter unexpectedly closes the network connection, then NodeXL will now try to reestablish the connection. (The symptom of this problem is a message that includes the text "[IOException]: Unable to read data from the transport connection: The connection was closed.")

1.0.1.246 (2013-07-19)
  • An importer for a new Graph Server has been added. The Graph Server is currently private.
  • Bug fix: If you used NodeXL, Analysis, Subgraph Images and one of your vertices had a name that was "reserved" by Windows (con, lpt, nul, and several others), you would get an error message that included the text "[ExternalException]: A generic error occurred in GDI+". Note that subgraph image file names now always start with "Img-", as in "Img-con.png".

1.0.1.245 (2013-06-19)
  • This release wraps up a set of enhancements and bug fixes that were previously included in a series of experimental private releases. All changes since the last public release (1.0.1.238) have to do with importing Twitter networks.
  • An experiment involving "shared term" edges in the Twitter search network is still in progress, and those edges are not included in this release. (They were not included in version 1.0.1.244, either.)
  • This release is functionally identical to version 1.0.1.244.

1.0.1.244 (2013-06-17, private release)
  • In the Twitter search network, vertices are now added to the graph for people who were replied to or mentioned by the people who actually tweeted the specified term.
  • Bug fix: In the Twitter networks, if you checked "Expand URLs in tweets" and a malformed URL was provided by Twitter, you would get a "Partial Network" message and then the graph would have no edges. The Partial Network details included the text "[UriFormatException]: Invalid URI: The format of the URI could not be determined". Now, NodeXL doesn't attempt to expand the bad URL.
  • Bug fix: When getting a Twitter search network, you would sometimes get a "Partial Network" message with details that included the text "[KeyNotFoundException]: The given key was not present in the dictionary." (This was caused by Twitter giving NodeXL a tweet that included no information about the tweeter. NodeXL now ignores such tweets.)

1.0.1.243 (2013-05-19, private release)
  • The Twitter Search Network now uses experimental shared term thresholds. This is part of an effort to obtain meaningful edges without running into Twitter's new rate limits.

1.0.1.242 (2013-05-01, private release)
  • The shared word user threshold can now be specified in the network configuration file used by the Network Server program. (For advanced users of private releases only.)
  • Bug fix: If you specified shared hashtag, URL, word, or word pair edge relationships in the Import from Twitter Search Network dialog box, the graph summary (NodeXL, Graph, Summary) did not mention the fact that the graph included those edges. (Private releases only.)

1.0.1.241 (2013-04-25, private release)
  • Bug fix: If you imported a Twitter network that included the empty hyperlink "http://" somewhere in the network's text, Excel would refuse to save the workbook. The error message started with "Errors were detected while saving..." This is an Excel bug that will also arise if you type "http://" directly into a cell. This change does not fix the latter problem.

1.0.1.240 (2013-04-24, private release)
  • If you check "add statistic columns to the Vertices worksheet" in the Import from Twitter Search Network dialog box, no additional time will be required to get the network. This used to require additional Twitter requests, and it was marked as "slower" in the dialog box.

1.0.1.239 (2013-04-08, private release)
  • Same as 1.0.1.238, but with additional edge options.

1.0.1.238 (2013-04-08)
  • Bug fix: In versions 1.0.1.236 and 237, if you entered a space (or a colon, or a few other special characters) into the "Add a vertex for each..." textbox on the Import from Twitter Search Network dialog box, you would get a message that included the text, "The Twitter Web service refused to provide the requested information."

1.0.1.237 (2013-03-25, private release)
  • Same as 1.0.1.236, but with additional edge options.

1.0.1.236 (2013-03-25)
  • There are some major changes in NodeXL's Twitter importers. See Changes in NodeXL's Twitter Importers for more information.
  • When you use dynamic filters (NodeXL, Analysis, Dynamic Filters), filtering an edge will automatically filter its adjacent vertices if the filtering causes those vertices to become isolates.
  • If you set the Visibility of vertex X to "Skip" and vertex X has adjacent vertices that are connected only to vertex X, then those adjacent vertices are now skipped as well. Previously, the adjacent vertices would remain in the graph as isolates.
  • For programmers: The NodeXL source code is now available on the CodePlex "Source Code" tab. The source code will no longer be provided as separate releases on the Downloads tab.
Go to Page 2 >>

↧

Updated Wiki: CompleteReleaseHistory

August 9, 2013, 8:46 am
$
0
0

Complete NodeXL Release History

1.0.1.248 (In progress)
  • If you import a network from the NodeXL Graph Server, the graph summary (NodeXL, Graph, Summary) now includes more information, including the date range of the tweets in the network.
  • The Data Import section of the Graph Summary for all Twitter, YouTube and Flickr network is now broken into paragraphs for clarity.
  • When it looks for user names in tweets, NodeXL now ignores most punctuation. For example, the user name "john" the tweet "Hello,@john" wasn't being detected, because it was preceded by a comma instead of a space.
  • NodeXL will now pause for an extra 15 seconds when Twitter rate limits are reached. This is an attempt to work around a problem where Twitter occasionally refuses to provide more information even after NodeXL pauses for the time specified by Twitter. The symptom of that problem is a message that includes the text "A likely cause is that you have made too many Twitter requests in the last 15 minutes." (This might not fix the problem, the cause of which is unknown.)

1.0.1.247 (2013-08-02)
  • If you import a Twitter search network and tell NodeXL to calculate Twitter search network top items (NodeXL, Analysis, Graph Metrics), then the following columns now get added to the Vertices worksheet: Top URLs in Tweet by Count, Top URLs in Tweet by Salience, Top Domains in Tweet by Count, Top Domains in Tweet by Salience, Top Hashtags in Tweet by Count, Top Hashtags in Tweet by Salience, Top Words in Tweet by Count, Top Words in Tweet by Salience, Top Word Pairs in Tweet by Count, Top Word Pairs in Tweet by Salience.
  • When importing a Twitter network, if Twitter unexpectedly closes the network connection, then NodeXL will now try to reestablish the connection. (The symptom of this problem is a message that includes the text "[IOException]: Unable to read data from the transport connection: The connection was closed.")

1.0.1.246 (2013-07-19)
  • An importer for a new Graph Server has been added. The Graph Server is currently private.
  • Bug fix: If you used NodeXL, Analysis, Subgraph Images and one of your vertices had a name that was "reserved" by Windows (con, lpt, nul, and several others), you would get an error message that included the text "[ExternalException]: A generic error occurred in GDI+". Note that subgraph image file names now always start with "Img-", as in "Img-con.png".

1.0.1.245 (2013-06-19)
  • This release wraps up a set of enhancements and bug fixes that were previously included in a series of experimental private releases. All changes since the last public release (1.0.1.238) have to do with importing Twitter networks.
  • An experiment involving "shared term" edges in the Twitter search network is still in progress, and those edges are not included in this release. (They were not included in version 1.0.1.244, either.)
  • This release is functionally identical to version 1.0.1.244.

1.0.1.244 (2013-06-17, private release)
  • In the Twitter search network, vertices are now added to the graph for people who were replied to or mentioned by the people who actually tweeted the specified term.
  • Bug fix: In the Twitter networks, if you checked "Expand URLs in tweets" and a malformed URL was provided by Twitter, you would get a "Partial Network" message and then the graph would have no edges. The Partial Network details included the text "[UriFormatException]: Invalid URI: The format of the URI could not be determined". Now, NodeXL doesn't attempt to expand the bad URL.
  • Bug fix: When getting a Twitter search network, you would sometimes get a "Partial Network" message with details that included the text "[KeyNotFoundException]: The given key was not present in the dictionary." (This was caused by Twitter giving NodeXL a tweet that included no information about the tweeter. NodeXL now ignores such tweets.)

1.0.1.243 (2013-05-19, private release)
  • The Twitter Search Network now uses experimental shared term thresholds. This is part of an effort to obtain meaningful edges without running into Twitter's new rate limits.

1.0.1.242 (2013-05-01, private release)
  • The shared word user threshold can now be specified in the network configuration file used by the Network Server program. (For advanced users of private releases only.)
  • Bug fix: If you specified shared hashtag, URL, word, or word pair edge relationships in the Import from Twitter Search Network dialog box, the graph summary (NodeXL, Graph, Summary) did not mention the fact that the graph included those edges. (Private releases only.)

1.0.1.241 (2013-04-25, private release)
  • Bug fix: If you imported a Twitter network that included the empty hyperlink "http://" somewhere in the network's text, Excel would refuse to save the workbook. The error message started with "Errors were detected while saving..." This is an Excel bug that will also arise if you type "http://" directly into a cell. This change does not fix the latter problem.

1.0.1.240 (2013-04-24, private release)
  • If you check "add statistic columns to the Vertices worksheet" in the Import from Twitter Search Network dialog box, no additional time will be required to get the network. This used to require additional Twitter requests, and it was marked as "slower" in the dialog box.

1.0.1.239 (2013-04-08, private release)
  • Same as 1.0.1.238, but with additional edge options.

1.0.1.238 (2013-04-08)
  • Bug fix: In versions 1.0.1.236 and 237, if you entered a space (or a colon, or a few other special characters) into the "Add a vertex for each..." textbox on the Import from Twitter Search Network dialog box, you would get a message that included the text, "The Twitter Web service refused to provide the requested information."

1.0.1.237 (2013-03-25, private release)
  • Same as 1.0.1.236, but with additional edge options.

1.0.1.236 (2013-03-25)
  • There are some major changes in NodeXL's Twitter importers. See Changes in NodeXL's Twitter Importers for more information.
  • When you use dynamic filters (NodeXL, Analysis, Dynamic Filters), filtering an edge will automatically filter its adjacent vertices if the filtering causes those vertices to become isolates.
  • If you set the Visibility of vertex X to "Skip" and vertex X has adjacent vertices that are connected only to vertex X, then those adjacent vertices are now skipped as well. Previously, the adjacent vertices would remain in the graph as isolates.
  • For programmers: The NodeXL source code is now available on the CodePlex "Source Code" tab. The source code will no longer be provided as separate releases on the Downloads tab.
Go to Page 2 >>

↧
Search

Updated Wiki: CompleteReleaseHistory

August 9, 2013, 8:47 am
$
0
0

Complete NodeXL Release History

1.0.1.248 (In progress)
  • If you import a network from the NodeXL Graph Server, the graph summary (NodeXL, Graph, Summary) now includes more information, including the date range of the tweets in the network.
  • The Data Import section of the Graph Summary for all Twitter, YouTube and Flickr network is now broken into paragraphs for clarity.
  • When it looks for user names in tweets, NodeXL now ignores most punctuation. For example, the user name "john" in the tweet "Hello,@john" wasn't being detected, because it was preceded by a comma instead of a space.
  • NodeXL will now pause for an extra 15 seconds when Twitter rate limits are reached. This is an attempt to work around a problem where Twitter occasionally refuses to provide more information even after NodeXL pauses for the time specified by Twitter. The symptom of that problem is a message that includes the text "A likely cause is that you have made too many Twitter requests in the last 15 minutes." (This might not fix the problem, the cause of which is unknown.)

1.0.1.247 (2013-08-02)
  • If you import a Twitter search network and tell NodeXL to calculate Twitter search network top items (NodeXL, Analysis, Graph Metrics), then the following columns now get added to the Vertices worksheet: Top URLs in Tweet by Count, Top URLs in Tweet by Salience, Top Domains in Tweet by Count, Top Domains in Tweet by Salience, Top Hashtags in Tweet by Count, Top Hashtags in Tweet by Salience, Top Words in Tweet by Count, Top Words in Tweet by Salience, Top Word Pairs in Tweet by Count, Top Word Pairs in Tweet by Salience.
  • When importing a Twitter network, if Twitter unexpectedly closes the network connection, then NodeXL will now try to reestablish the connection. (The symptom of this problem is a message that includes the text "[IOException]: Unable to read data from the transport connection: The connection was closed.")

1.0.1.246 (2013-07-19)
  • An importer for a new Graph Server has been added. The Graph Server is currently private.
  • Bug fix: If you used NodeXL, Analysis, Subgraph Images and one of your vertices had a name that was "reserved" by Windows (con, lpt, nul, and several others), you would get an error message that included the text "[ExternalException]: A generic error occurred in GDI+". Note that subgraph image file names now always start with "Img-", as in "Img-con.png".

1.0.1.245 (2013-06-19)
  • This release wraps up a set of enhancements and bug fixes that were previously included in a series of experimental private releases. All changes since the last public release (1.0.1.238) have to do with importing Twitter networks.
  • An experiment involving "shared term" edges in the Twitter search network is still in progress, and those edges are not included in this release. (They were not included in version 1.0.1.244, either.)
  • This release is functionally identical to version 1.0.1.244.

1.0.1.244 (2013-06-17, private release)
  • In the Twitter search network, vertices are now added to the graph for people who were replied to or mentioned by the people who actually tweeted the specified term.
  • Bug fix: In the Twitter networks, if you checked "Expand URLs in tweets" and a malformed URL was provided by Twitter, you would get a "Partial Network" message and then the graph would have no edges. The Partial Network details included the text "[UriFormatException]: Invalid URI: The format of the URI could not be determined". Now, NodeXL doesn't attempt to expand the bad URL.
  • Bug fix: When getting a Twitter search network, you would sometimes get a "Partial Network" message with details that included the text "[KeyNotFoundException]: The given key was not present in the dictionary." (This was caused by Twitter giving NodeXL a tweet that included no information about the tweeter. NodeXL now ignores such tweets.)

1.0.1.243 (2013-05-19, private release)
  • The Twitter Search Network now uses experimental shared term thresholds. This is part of an effort to obtain meaningful edges without running into Twitter's new rate limits.

1.0.1.242 (2013-05-01, private release)
  • The shared word user threshold can now be specified in the network configuration file used by the Network Server program. (For advanced users of private releases only.)
  • Bug fix: If you specified shared hashtag, URL, word, or word pair edge relationships in the Import from Twitter Search Network dialog box, the graph summary (NodeXL, Graph, Summary) did not mention the fact that the graph included those edges. (Private releases only.)

1.0.1.241 (2013-04-25, private release)
  • Bug fix: If you imported a Twitter network that included the empty hyperlink "http://" somewhere in the network's text, Excel would refuse to save the workbook. The error message started with "Errors were detected while saving..." This is an Excel bug that will also arise if you type "http://" directly into a cell. This change does not fix the latter problem.

1.0.1.240 (2013-04-24, private release)
  • If you check "add statistic columns to the Vertices worksheet" in the Import from Twitter Search Network dialog box, no additional time will be required to get the network. This used to require additional Twitter requests, and it was marked as "slower" in the dialog box.

1.0.1.239 (2013-04-08, private release)
  • Same as 1.0.1.238, but with additional edge options.

1.0.1.238 (2013-04-08)
  • Bug fix: In versions 1.0.1.236 and 237, if you entered a space (or a colon, or a few other special characters) into the "Add a vertex for each..." textbox on the Import from Twitter Search Network dialog box, you would get a message that included the text, "The Twitter Web service refused to provide the requested information."

1.0.1.237 (2013-03-25, private release)
  • Same as 1.0.1.236, but with additional edge options.

1.0.1.236 (2013-03-25)
  • There are some major changes in NodeXL's Twitter importers. See Changes in NodeXL's Twitter Importers for more information.
  • When you use dynamic filters (NodeXL, Analysis, Dynamic Filters), filtering an edge will automatically filter its adjacent vertices if the filtering causes those vertices to become isolates.
  • If you set the Visibility of vertex X to "Skip" and vertex X has adjacent vertices that are connected only to vertex X, then those adjacent vertices are now skipped as well. Previously, the adjacent vertices would remain in the graph as isolates.
  • For programmers: The NodeXL source code is now available on the CodePlex "Source Code" tab. The source code will no longer be provided as separate releases on the Downloads tab.
Go to Page 2 >>

↧
↧

Updated Wiki: CompleteReleaseHistory

August 9, 2013, 9:02 am
$
0
0

Complete NodeXL Release History

1.0.1.248 (2013-08-09)
  • If you import a network from the NodeXL Graph Server, the graph summary (NodeXL, Graph, Summary) now includes more information, including the date range of the tweets in the network.
  • The Data Import section of the Graph Summary for all Twitter, YouTube and Flickr network is now broken into paragraphs for clarity.
  • When it looks for user names in tweets, NodeXL now ignores most punctuation. For example, the user name "john" in the tweet "Hello,@john" wasn't being detected, because it was preceded by a comma instead of a space.
  • NodeXL will now pause for an extra 15 seconds when Twitter rate limits are reached. This is an attempt to work around a problem where Twitter occasionally refuses to provide more information even after NodeXL pauses for the time specified by Twitter. The symptom of that problem is a message that includes the text "A likely cause is that you have made too many Twitter requests in the last 15 minutes." (This might not fix the problem, the cause of which is unknown.)

1.0.1.247 (2013-08-02)
  • If you import a Twitter search network and tell NodeXL to calculate Twitter search network top items (NodeXL, Analysis, Graph Metrics), then the following columns now get added to the Vertices worksheet: Top URLs in Tweet by Count, Top URLs in Tweet by Salience, Top Domains in Tweet by Count, Top Domains in Tweet by Salience, Top Hashtags in Tweet by Count, Top Hashtags in Tweet by Salience, Top Words in Tweet by Count, Top Words in Tweet by Salience, Top Word Pairs in Tweet by Count, Top Word Pairs in Tweet by Salience.
  • When importing a Twitter network, if Twitter unexpectedly closes the network connection, then NodeXL will now try to reestablish the connection. (The symptom of this problem is a message that includes the text "[IOException]: Unable to read data from the transport connection: The connection was closed.")

1.0.1.246 (2013-07-19)
  • An importer for a new Graph Server has been added. The Graph Server is currently private.
  • Bug fix: If you used NodeXL, Analysis, Subgraph Images and one of your vertices had a name that was "reserved" by Windows (con, lpt, nul, and several others), you would get an error message that included the text "[ExternalException]: A generic error occurred in GDI+". Note that subgraph image file names now always start with "Img-", as in "Img-con.png".

1.0.1.245 (2013-06-19)
  • This release wraps up a set of enhancements and bug fixes that were previously included in a series of experimental private releases. All changes since the last public release (1.0.1.238) have to do with importing Twitter networks.
  • An experiment involving "shared term" edges in the Twitter search network is still in progress, and those edges are not included in this release. (They were not included in version 1.0.1.244, either.)
  • This release is functionally identical to version 1.0.1.244.

1.0.1.244 (2013-06-17, private release)
  • In the Twitter search network, vertices are now added to the graph for people who were replied to or mentioned by the people who actually tweeted the specified term.
  • Bug fix: In the Twitter networks, if you checked "Expand URLs in tweets" and a malformed URL was provided by Twitter, you would get a "Partial Network" message and then the graph would have no edges. The Partial Network details included the text "[UriFormatException]: Invalid URI: The format of the URI could not be determined". Now, NodeXL doesn't attempt to expand the bad URL.
  • Bug fix: When getting a Twitter search network, you would sometimes get a "Partial Network" message with details that included the text "[KeyNotFoundException]: The given key was not present in the dictionary." (This was caused by Twitter giving NodeXL a tweet that included no information about the tweeter. NodeXL now ignores such tweets.)

1.0.1.243 (2013-05-19, private release)
  • The Twitter Search Network now uses experimental shared term thresholds. This is part of an effort to obtain meaningful edges without running into Twitter's new rate limits.

1.0.1.242 (2013-05-01, private release)
  • The shared word user threshold can now be specified in the network configuration file used by the Network Server program. (For advanced users of private releases only.)
  • Bug fix: If you specified shared hashtag, URL, word, or word pair edge relationships in the Import from Twitter Search Network dialog box, the graph summary (NodeXL, Graph, Summary) did not mention the fact that the graph included those edges. (Private releases only.)

1.0.1.241 (2013-04-25, private release)
  • Bug fix: If you imported a Twitter network that included the empty hyperlink "http://" somewhere in the network's text, Excel would refuse to save the workbook. The error message started with "Errors were detected while saving..." This is an Excel bug that will also arise if you type "http://" directly into a cell. This change does not fix the latter problem.

1.0.1.240 (2013-04-24, private release)
  • If you check "add statistic columns to the Vertices worksheet" in the Import from Twitter Search Network dialog box, no additional time will be required to get the network. This used to require additional Twitter requests, and it was marked as "slower" in the dialog box.

1.0.1.239 (2013-04-08, private release)
  • Same as 1.0.1.238, but with additional edge options.

1.0.1.238 (2013-04-08)
  • Bug fix: In versions 1.0.1.236 and 237, if you entered a space (or a colon, or a few other special characters) into the "Add a vertex for each..." textbox on the Import from Twitter Search Network dialog box, you would get a message that included the text, "The Twitter Web service refused to provide the requested information."

1.0.1.237 (2013-03-25, private release)
  • Same as 1.0.1.236, but with additional edge options.

1.0.1.236 (2013-03-25)
  • There are some major changes in NodeXL's Twitter importers. See Changes in NodeXL's Twitter Importers for more information.
  • When you use dynamic filters (NodeXL, Analysis, Dynamic Filters), filtering an edge will automatically filter its adjacent vertices if the filtering causes those vertices to become isolates.
  • If you set the Visibility of vertex X to "Skip" and vertex X has adjacent vertices that are connected only to vertex X, then those adjacent vertices are now skipped as well. Previously, the adjacent vertices would remain in the graph as isolates.
  • For programmers: The NodeXL source code is now available on the CodePlex "Source Code" tab. The source code will no longer be provided as separate releases on the Downloads tab.
Go to Page 2 >>

↧

Source code checked in, #72805

August 9, 2013, 9:55 am
↧

Source code checked in, #72806

August 9, 2013, 9:59 am
$
0
0
Updates the NodeXL source code to version 1.0.1.248.
↧

Updated Release: NodeXL Excel Template, version 1.0.1.248 (Aug 09, 2013)

August 9, 2013, 10:00 am
$
0
0
The NodeXL Excel template displays a network graph using edge and vertex lists stored in an Excel 2007 or Excel 2010 workbook.

Please help support the development of NodeXL with your donation.

What's New

This release expands the Twitter search network top items that NodeXL calculates. See the Complete NodeXL Release History for more information.

Installation Steps

Follow these steps to install and use the template:
  1. Download the Zip file.
  2. Unzip it into any folder. Use WinZip or a similar program, or just right-click the Zip file in Windows Explorer and select "Extract All."
  3. Close Excel if it's open.
  4. Run Setup.exe. You need to be an administrator to do this. (You don't need to be an administrator to actually use the NodeXL template once it's installed, however.) The setup program might install some Microsoft prerequisites. These are the Microsoft. .NET Framework 3.5 Service Pack 1, the Microsoft Office 2007 Primary Interop Assemblies, and the Microsoft Visual Studio Tools for the Office System 3.0 Runtime Service Pack 1.
  5. Delete the unzipped files. They're no longer needed.
  6. Register. If you didn't register while running Setup.exe, please do so here. Registration is optional.
  7. Use the template. In the Windows Start menu, click "All Programs" (Windows 7 or Vista) or "Programs" (XP), then "NodeXL," then "Excel Template."

Installing for multiple users: There is an option in the setup program to install for "Just Me" or "Everyone." Most people should accept the default "Just Me" option. If you think you need the "Everyone" option, please see How to install NodeXL for multiple users for more information.

System Requirements

  1. Windows 7, Vista, or XP. (Will also work within Parallels Desktop and VMware Fusion on the Mac.)
  2. Office 2007 or 2010.
  3. NodeXL has not been tested yet with Office 2013 or Windows 8.

Release History

Please see the Complete NodeXL Release History.
↧
↧

Updated Release: NodeXL Excel Template, version 1.0.1.248 (Aug 09, 2013)

August 9, 2013, 10:01 am
$
0
0
The NodeXL Excel template displays a network graph using edge and vertex lists stored in an Excel 2007 or Excel 2010 workbook.

Please help support the development of NodeXL with your donation.

What's New

This release makes some changes in the graph importers. See the Complete NodeXL Release History for more information.

Installation Steps

Follow these steps to install and use the template:
  1. Download the Zip file.
  2. Unzip it into any folder. Use WinZip or a similar program, or just right-click the Zip file in Windows Explorer and select "Extract All."
  3. Close Excel if it's open.
  4. Run Setup.exe. You need to be an administrator to do this. (You don't need to be an administrator to actually use the NodeXL template once it's installed, however.) The setup program might install some Microsoft prerequisites. These are the Microsoft. .NET Framework 3.5 Service Pack 1, the Microsoft Office 2007 Primary Interop Assemblies, and the Microsoft Visual Studio Tools for the Office System 3.0 Runtime Service Pack 1.
  5. Delete the unzipped files. They're no longer needed.
  6. Register. If you didn't register while running Setup.exe, please do so here. Registration is optional.
  7. Use the template. In the Windows Start menu, click "All Programs" (Windows 7 or Vista) or "Programs" (XP), then "NodeXL," then "Excel Template."

Installing for multiple users: There is an option in the setup program to install for "Just Me" or "Everyone." Most people should accept the default "Just Me" option. If you think you need the "Everyone" option, please see How to install NodeXL for multiple users for more information.

System Requirements

  1. Windows 7, Vista, or XP. (Will also work within Parallels Desktop and VMware Fusion on the Mac.)
  2. Office 2007 or 2010.
  3. NodeXL has not been tested yet with Office 2013 or Windows 8.

Release History

Please see the Complete NodeXL Release History.
↧

Released: NodeXL Excel Template, version 1.0.1.248 (Aug 09, 2013)

August 9, 2013, 10:01 am
$
0
0
The NodeXL Excel template displays a network graph using edge and vertex lists stored in an Excel 2007 or Excel 2010 workbook.

Please help support the development of NodeXL with your donation.

What's New

This release makes some changes in NodeXL's graph importers. See the Complete NodeXL Release History for more information.

Installation Steps

Follow these steps to install and use the template:
  1. Download the Zip file.
  2. Unzip it into any folder. Use WinZip or a similar program, or just right-click the Zip file in Windows Explorer and select "Extract All."
  3. Close Excel if it's open.
  4. Run Setup.exe. You need to be an administrator to do this. (You don't need to be an administrator to actually use the NodeXL template once it's installed, however.) The setup program might install some Microsoft prerequisites. These are the Microsoft. .NET Framework 3.5 Service Pack 1, the Microsoft Office 2007 Primary Interop Assemblies, and the Microsoft Visual Studio Tools for the Office System 3.0 Runtime Service Pack 1.
  5. Delete the unzipped files. They're no longer needed.
  6. Register. If you didn't register while running Setup.exe, please do so here. Registration is optional.
  7. Use the template. In the Windows Start menu, click "All Programs" (Windows 7 or Vista) or "Programs" (XP), then "NodeXL," then "Excel Template."

Installing for multiple users: There is an option in the setup program to install for "Just Me" or "Everyone." Most people should accept the default "Just Me" option. If you think you need the "Everyone" option, please see How to install NodeXL for multiple users for more information.

System Requirements

  1. Windows 7, Vista, or XP. (Will also work within Parallels Desktop and VMware Fusion on the Mac.)
  2. Office 2007 or 2010.
  3. NodeXL has not been tested yet with Office 2013 or Windows 8.

Release History

Please see the Complete NodeXL Release History.
↧
Search

Updated Release: NodeXL Excel Template, version 1.0.1.248 (Aug 09, 2013)

August 9, 2013, 10:01 am
$
0
0
The NodeXL Excel template displays a network graph using edge and vertex lists stored in an Excel 2007 or Excel 2010 workbook.

Please help support the development of NodeXL with your donation.

What's New

This release makes some changes in NodeXL's graph importers. See the Complete NodeXL Release History for more information.

Installation Steps

Follow these steps to install and use the template:
  1. Download the Zip file.
  2. Unzip it into any folder. Use WinZip or a similar program, or just right-click the Zip file in Windows Explorer and select "Extract All."
  3. Close Excel if it's open.
  4. Run Setup.exe. You need to be an administrator to do this. (You don't need to be an administrator to actually use the NodeXL template once it's installed, however.) The setup program might install some Microsoft prerequisites. These are the Microsoft. .NET Framework 3.5 Service Pack 1, the Microsoft Office 2007 Primary Interop Assemblies, and the Microsoft Visual Studio Tools for the Office System 3.0 Runtime Service Pack 1.
  5. Delete the unzipped files. They're no longer needed.
  6. Register. If you didn't register while running Setup.exe, please do so here. Registration is optional.
  7. Use the template. In the Windows Start menu, click "All Programs" (Windows 7 or Vista) or "Programs" (XP), then "NodeXL," then "Excel Template."

Installing for multiple users: There is an option in the setup program to install for "Just Me" or "Everyone." Most people should accept the default "Just Me" option. If you think you need the "Everyone" option, please see How to install NodeXL for multiple users for more information.

System Requirements

  1. Windows 7, Vista, or XP. (Will also work within Parallels Desktop and VMware Fusion on the Mac.)
  2. Office 2007 or 2010.
  3. NodeXL has not been tested yet with Office 2013 or Windows 8.

Release History

Please see the Complete NodeXL Release History.
↧

New Post: Partial network problem in Twitter

August 9, 2013, 10:21 am
$
0
0
John:

I've made a change in the latest release (1.0.1.248) that you might want to test on your 64-bit machine. From the release notes:

"NodeXL will now pause for an extra 15 seconds when Twitter rate limits are reached. This is an attempt to work around a problem where Twitter occasionally refuses to provide more information even after NodeXL pauses for the time specified by Twitter. The symptom of that problem is a message that includes the text "A likely cause is that you have made too many Twitter requests in the last 15 minutes." (This might not fix the problem, the cause of which is unknown.)"

-- Tony
↧
↧

New Post: Partial network problem in Twitter

August 9, 2013, 10:25 am
$
0
0
Tony, that's awesome, thanks. I will try it this weekend and see how it goes.

Marc, that's what I have been doing until now, which is OK most of the time, but I run into memory errors on larger networks (which I can work around on the machine that has more memory). But that is often an option. I've been testing the upper limits of what one can reasonably expect to do in NodeXL.
↧

New Post: Clique Size

August 9, 2013, 7:40 pm
$
0
0
I apologize if this was in the documentation I attempted to do a search to find it.

Is there a metric that provides the monochromatic clique size of the graph.

For example if I put in a label of "red" for some of the edges and "blue" for the rest, then will it tell me the biggest K^n red or blue that is present?
↧

New Post: Partial network problem in Twitter

August 10, 2013, 6:52 am
$
0
0
I started a huge import last night, and it's still running today without the error (which had come up pretty quickly in the past). I am optimistic this has resolved the issue, but I will run some more stuff over the weekend and let you know if I run into the problem again.

Thank you!!!!
↧
Viewing all 4386 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>