diegolo

15 ms·

121.
Oculus Pr0n (vimeo.com)
1 points by diegolo 13y ago|0 comments
122.
Noteslate is back(noteslate.com)
1 points by diegolo 13y ago|1 comments
123.
Sindicetech(independent.ie)
1 points by diegolo 13y ago|0 comments
124.
Conditional probability(setosa.io)
1 points by diegolo 13y ago|0 comments
125.
by diegolo 13y ago
I guess the correct link was http://romuluscrisan.com/blog/2014/02/24/why-i-choose-github...
126.
The network nonsense of Albert-László Barabási(liorpachter.wordpress.com)
1 points by diegolo 13y ago|0 comments
127.
#SixWordPeerReview(twitter.com)
1 points by diegolo 13y ago|0 comments
128.
by diegolo 13y ago
It would be nice to have a view also on the raw html code, e.g., to create a field containing the url of an image in the page.
129.
by diegolo 13y ago
static html websites
130.
by diegolo 13y ago
A little sample of the dump: https://dl.dropboxusercontent.com/u/4663256/tmp/json-wikiped...
131.
by diegolo 13y ago
yes, and also it makes easy to manipulate the dump using Hadoop, and retrieving some values for all the article using jq http://stedolan.github.io/jq/ , could you do the same with XML? Btw You can find a little sample o
132.
by diegolo 13y ago
It does that indeed! It will process a field paragraph, containing a list of parsed paragraphs in the article, as simple UTF8 text. Lists and Tables are collected in separated fields, have a look to the Article object. For the wikicode pars
133.
by diegolo 13y ago
Hi, I'm the author of Json-Wikipedia. It's different from DB-Pedia. DBPedia converts the semistructured data containined in the infoboxes in rdf triples, while Json-Wikipedia converts ALL the content of the page (text, infoboxes,