HN user

harrywye

27 karma

Windows app developer.

Twitter: @harrywye Blog: http://www.harrysmemo.com/

Posts14
Comments21
View on HN

Yes, I'm aware that. That's why I tried to think of scenarios where I was possibly using my other browsers/devices with the same gmail account. But, this is different. I just saw the same thing happening again with another gdocs document. The message comes up "hxxxxx has opened the document" and then some seconds later, "hxxxxx has left", while I wasn't doing anything. (If it wasn't due to some kind of anomoly in google docs, e.g., possibly as suggested spaghetti, then the only explanation seems somebody cracked my password, unfortunately.)

Not much of a build script, really. I used to (and, still do, for a limited purposes) use ant script to copy GAE jar files to war dir. (Now, Eclipse plugin seems to do that for me.) In any case, the relevant part is as follows (which used to have hard-coded SDK dir). I changed it last night to use "environment" var, GAESDK_HOME.

    ...
    <property environment="myenv" />
    <property name="gae.sdk.dir" value="${myenv.GAESDK_HOME}"/>
    ...
    <target name="copyGAEJars">
        <copy todir="${warLibDir}" overwrite="true" flatten="true">
		    <fileset dir ="${gae.sdk.dir}/lib/user">
			    <include name="**/*.jar" />
			</fileset>
		</copy>
    </target>
    ....
Exploiting reality 14 years ago

It's somewhat amusing that the user "unnamed" posted this link. :) Regardless, this is an interesting article. I can recall a few movies where a made-up character becomes "real".

On a related note, I'm getting all these new kind of spam emails these days in which the messages are specifically tailored to me. Real creepy. They know my name. They know the city I live in. Etc. (The message says, for example, I met the president of his company in a conference in [CITY NAME], and this is a follow-up. Etc.) Real creepy.

If you send @ messages to a large number of people, that's spam, by definition. They don't have to visit your profile to see that. Some of them will just "flag" you if you send them unsolicited @ messages, and you can, and will eventually, be banned from Twitter.

There is no other (legit) way, in my view. If you want to send messages to a large number of people, then you'll have to build your audience/followers over time.

PS: Here's an article I wrote a few weeks ago, if you are interested: http://blog.tweetdelegate.com/post/21164614504/how-do-you-ge...

Oh, man. Seems like they are releasing a new version every other week. I should come up with a better way to "automatically" upgrade my build scripts (and, I have many of them) in some way.... Good new and bad news for me. :)

It should depend on the type of app you're building. If the monetization is important (e.g., it's a paid app), then I hear that iOS is still the way to go. (As kavalec points out, the trend is slowly changing though.) If it's important for you to have wide distribution of the app, then Android has a larger reach and this will only increase over time.

I'm no expert in this area, but I just stumbled upon your post. Depending on the stage of the startup (and, importance of your role), you might get 1/4% or 1/8%, which is sort of standard, in my understanding, for early employees. But, these numbers do not really mean much, since your share will be diluted and diluted, and diluted, as the startup gets more funding. The cash equivalent of your option is close to zero at this point, so I wouldn't optimize for the option. (As for the valuation of the startup, if it has been funded, then there should generally be valuation based on the previous round. You can always ask the founder(s) and, I presume, most of them will be candid about it.)

OK, I figured it out. :) The problem was, we only support HTML pages at this point. The targetUrl you specified did not return a valid HTML page (it's JSON), and the application just returned 404 HTTP status code (since it couldn't find any HTML content), which was by design. (Note that this API is supposed to be used by a program not from a Web browser.) Anyways, it had been a while I actually looked at the code, and it was "fun" to look at the code again. :) I have yet to find a "bug". grin

D*ng, LiquidSummer. I've been using this service for almost a year with no problem, and you broke it. :)

It appears that, because it recursively calls it, the call eventually times out. (Google App Engine has this time limit of 10~30 seconds.) I'm not sure if I'll have a solution for this, but I can at least catch the exception. I'll need to look into it further.

Thanks for finding this bug!

True_religion, Great point. As a matter of fact, PageSynopsis is just part of my larger effort.

There are many different ways we can use, benefit from, others' (other developers') work. Traditionally, using a library and linking it into your own code was the primary way to use other people's work. (There are pros and cons.) There have been many different efforts for the last decade or so to make "reusing" others' software "easier". You may recall things like component-based software development, etc., or more recently, certain architectural designs/paradigms such as SOA, and so forth. Open source software is another way in which you can "reuse" others' work.

I have no problem with one or another of these approaches. I use a lot of open source software and I open sourced a lot of my software before (even before open source was considered an important part of the development community). I was a big believer of component-based software development (which never realized).

This is just a different effort. Do you really want to run hundreds of "small" services yourself? Just hypothetically, if you can find (virtually) every functionality you need as a Web Service, do you still need to code it into your own program or run it as your own service? This is a rhetorical question, but I see this as a future. I believer that having a uniform interface (e.g., REST based WS) can make this dream a reality. REST-based Web services have been getting popular for the last several years with wide "install bases". I think we are on a good track (so far).

More to the point, the program part of the PageSynopsis is not that much. Any competent developer can probably implement this in a day (or, for even less) including all extra functionalities. But, why spend a day? And, spend more hours maintaining it, when/if the service were already available? (Also, that's hundred days for hundred developers.) I believe that the real benefit of PageSynopsis (and, other services I'm currently developing) is that, if you choose so, you do not have to worry about anything other than just the "interface". I developed this service almost a year ago, and amazingly it just works for me to this date. (Google does heavy lifting for me.) No more extra jar files I have to worry about. No maven, ant scripts to maintain.

I hope you see that this can be useful.

Givan, yes and no. Clearly, you're right in that it's one more thing to learn (a particular variant of REST API). But, there can be many benefits of using a Web service like this (or, another app/service/abstraction layer, etc.) in some situations. For example, suppose that you want to get the meta description of a certain Web page using a Javascript (from your own HTML page). The Web page may happen to be large and there can substantial network latency, etc. In many cases, you do not want to do it on the fly every time your page is loaded. You may want to implement a storage or caching layer on the server side, etc. PageSynopsis provides such service "out of the box". It also supports "asynchronous" fetching, periodic refreshing, and so forth. This is a very simple service, but I use it from different apps of mine (and, I don't have to replicate this functionality across different apps). Thanks for checking it out.

Thanks for checking the page, bpfh. I'm not sure what's happening. I haven't tried viewing the Web site on Mac, but I can view it both on Windows and Linux (Ubuntu) with Chrome, FF, and IE8. Can you please try again, and let me know if you still have problem? The Web site (which is running on the same JVM of the Web Service) uses Twitter Bootstrap, and it works from my Android devices as well. Thanks!

UI looks clean and functional. Good work. If I can suggest one feature, how about adding "browse" or list functionality. With a limited "inventory" at this point, search interface does not seem to be the most efficient way to use the site.

Although this has been partly helped by MS's resistance to innovation (e.g., with regards to HTML5), Chrome's rise for the last few years has been truly amazing nonetheless. Chrome is not just for developers any more. I see more and more IE9 commercials these days, but would it really help to reverse or slow down Chrome's momentum at this point?