Is there a handwritten (stylus) notes software which can be used for this type of linking? I'm not talking about OCR, but handwritten/drawn as default format.
I'm certainly drawn to the idea and am inclined positively towards it. I'm even willing to overlook the ridiculous hubris of "This new medium will be the way most text is read and written in the future."
However, there are many confusing things to me as a person who arrived at the site through HN. Since one of the developers is promoting the "app" here, it might be useful to hear from him on these points:
1. Is this an input format or is it a publication format, or is it a viewer? Does it rely on a time-tested plaintext markup format like LaTeX or markdown? Perhaps it is a HTML viewer for a LaTeX markup document with special structure, rather than an actual typset web publication format.
2. What is the conceptual structure of the document system? Giving me a screenshot does not show me anything about the way you are conceptualizing your document. Is there a separation of content and output, output and viewer?
3. Is any part of this open source? Are you incorporating any other major technologies which have already been developed?
I apologize if any of the above seems harsh, but this is an important topic and I have become slightly tired of seeing flashy presentations about poorly-thought out "revolutionary" new document formats/tools/whatnot.
The 2011 video I referenced in my other comment was taken along Coorow-Latham road, in WA, with the same camera motions... Perhaps this one was also taken there?
Interesting utility, and kudos for making it OSS!
Something I couldn't help but notice is that it is very similar to a short film which played at TIFF 2011 called "Coorow-Latham Road" by Blake Williams, a 20 minute video work which played in the Wavelengths experimental section of the festival.
Amusingly, the artist has created another version of the video, now that hyperlapse is available:
https://vimeo.com/63778677
The original film, Coorow-Latham Road, is edited and manipulated from screenshots of a Google street view road trip along the length of a road in rural Australia. The camera rotates 180 degrees from forward to backward along the 20 minute trip.
This may be a case where art inspires software, which is an interesting phenomenon in itself, or maybe it's a freak coincidence!
This seems to work well -- I imagine I would use it if I were using a temporary computer, an ipad, or some such thing. What would be nice is if I could integrate it with dropbox or similar services, essentially use it to edit and compile files in my dropbox library. Also it would be good to use a standard editor with config files that could be saved to customize the environment.
From my point of view, that's not really tex to html. That's tex markup to html. I am talking about using the latex software, whose purpose is to do typesetting. The amazing thing about this converter is that it takes the latex OUTPUT and produces html.
Amazing - I am attempting to install this on mac osx lion -- it is taking a lot of time because of the dependencies. With so many dependencies the probability of failure is very high. Let's hope it works.
I urge you to find a way to allow people to install your software more easily.
I managed to get it to install (after about an hour and a half of tinkering. However I get "Segmentation fault" when I try running it:
pdf2htmlEX --debug=1 test.pdf
temporary dir: /tmp/pdf2htmlEX-LY9cOv
Preprocessing: ....
Working: Add new temporary file: /tmp/pdf2htmlEX-LY9cOv/__css
Add new temporary file: /tmp/pdf2htmlEX-LY9cOv/__pages
Add new temporary file: /tmp/pdf2htmlEX-LY9cOv/p1.png
Install font: (29 0) -> f1
Add new temporary file: /tmp/pdf2htmlEX-LY9cOv/f1.pfa
A couple of naive questions about the design of the security system:
1. Why is it possible to do the password tests remotely? Why would the key on the router be allowed to be transmitted? Even a 6 character password should be safe if you don't allow multiple tries.
In creating tutorials, the key is exercising restraint.
This is especially important when dealing with Emacs, which is a classic case of an almost complete lack of restraint
concerning the hierarchical organization of features. EmacsWiki is another great example of a huge tangled ball of knots.
Most experts forget exactly how impenetrable a new subject can seem to a beginner. I commend the tutor for not forgetting this!
I find your post interesting, and it goes some way to answering my own questions. However, your post is based on the premise
"There are four issues with decentralized, large-scale sharing of content between non-technical people..."
and you claim those four issues are
1. Identity Persistence
2. Data Persistence
3. Publishing
4. Access Restrictions
I do not see why this is so. But even if it is, it is not even clear if the main point, at this stage, is to identify the atomic components of the "social web" -- perhaps what is
sought after now is a slightly higher-level conceptual framework which puts these together.
For example, "publishing" may be missing the point - perhaps we need a finer grained concept: different kinds of collaboration, delegation of authority, distribution of tasks, self-communication, electronic cloud prayer...