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 hubris of the statement is not lost on me, but what should a founder be but delusional and optimistic :)
1. It's both a viewer and a word processor. It relies on Markdown (and LaTeX through extensions). We export to Md, but will be adding more import/export options in the future. We hope to create a publication standard for it.
2. The structure of the document is an "outline of index cards". Each card can have one or more children. Source content (in markdown) is edited by toggling edit mode on that card.
3. Yes, we are extracting parts of this as open-source. The rest remains proprietary (for now, at least).
> I apologize if any of the above seems harsh
No need to apologize. Thoughtful criticism is what we need.
I've been working on a relatively similar, but much larger and very complex project (AI/Maths) for some years now. It makes me really happy to see people coming up with the vision of a "hypertext" perspective shift.
Do you mind explaining why your surname is Ferrari?
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.
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.
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
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
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.
1. The attack is to brute force the shared secret (password). This can be done offline because by capturing the exchange you have the ANonce and SNonce and all other information required to generate the same key -- except the shared secret. Try lots of passwords and check if you generate the same PTK as the two stations do.
2. Encrypted with what? This is the key exchange stage that is attacked here.
802.11w adds signing to management frames which eliminates the deauth attack -- makes it harder to capture the EAPOL frames. Also, IIRC, WPA2-enterprise would not be susceptible to this sort of attack; you've pre-shared a key rather than a (short) password for generating one.
Honest question: since all devices connecting to a WIFI network are by definition within a short distance of the router itself, is there a WIFI solution that uses pre-shared key cryptography? That seems to me to be the only truly unbreakable option.
The key isn't being transmitted, but a hash of it with a nonce is. You could do a DH key exchange and encrypt it, but I doubt that would help that much: An attacker would just need to transmit their own auth packets.
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'm the chap that made the tutorials and I agree with both of you. I can't, for the life of me, study anything from a screencast. Most of the ones I've seen are either too superficial to be worth it or too detailed to be useful without being able to flip back and forth like it's possible to do with text.
I'm trying to balance out the two and spent quite a while trying to tease out stuff that's not too superficial but at the same time is not too deep for beginners to follow.
Like most of these things, it's going to be impossible to please everyone but if there is a sizeable fraction of people who find this useful, I think it's served its purpose.
As for me, thinking through the whole thing in advance, trying stuff out and preparing the material helps me clarify my own knowledge.