Get your own customer support community

About me

Recent activity

Subscribe to this feed
  • idea

    schwarz replied on January 12, 2009 20:36 to the idea "A public test server and stable server" in Plurk:

    schwarz
    Ok, I was thinking of it more as an extra thing on top of what you already do, not as a replacement of your current testing. Feel free not to do it, but I think the idea is good :-)
    Do you think this is one of the best points? Mark it as a good point
  • idea

    schwarz replied on January 12, 2009 17:09 to the idea "A public test server and stable server" in Plurk:

    schwarz
    I wasn't thinking about the current issues in particular. I think at least some of us would spot at least some errors from time to time, and that would be of quite som value to you.
    I'm thinking about the caching issues, replicating and disappearing plurks, and such things.
    Do you think this is one of the best points? Mark it as a good point
  • idea

    schwarz shared an idea in Plurk on January 12, 2009 10:21:

    schwarz
    Better error messages
    You should improve your error messages. They are close to useless as they are now. The only error message Plurk seems to give your is "an unknown error happened". This can mean anything from a server error when saving the message to a locally broken VPN connection or what have you. I am not really sure any "known errors" exist ;-)

    How about keeping some state on the client to give more appropriate error messages? You could also set up a service that would send some clues back of what the error might be (for example it could tell if the database is known to be unstable right now). That would improve usabilty vastly and lower frustrations.
  • idea

    schwarz shared an idea in Plurk on January 12, 2009 10:04:

    schwarz
    A public test server and stable server
    It would be great if you set up a public testing server on which you would roll out changes and new features before putting it on the production server. People could be moved to this server on an opt in basis, so the stable server would be the standard.

    I am sure many people would volunteer to try out the bleeding edge of Plurk development, but I also believe a lot more would love the stability of a server running only code that has been publicly tested.

    Furthermore this would make is possible for all the hard working translaters to have a relatively complete translation ready when the changes move to the stable server, so the international versions aren't always as lacking as they are now.