An afterthought comment in brackets is not enough. You need to clarify more strongly that its the address at the bottom of the page and NOT the actual address that the link brings you to, before someone destroys their Nxt by sending them to the Genesis address. THE ADDRESS AT THE LINK IS NOT HIS DONATION ADDRESS. Nexern's donation address is located at the bottom of the page.

Yikes, yes, it's the "donation" address at the bottom of the page. Not sure why it linked to the genesis address in that URL, I just copied the homepage, sorry.

at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1044) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141) at org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:199) at org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:109) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97) at org.eclipse.jetty.server.Server.handle(Server.java:459) at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:280) at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:229) at org.eclipse.jetty.io.AbstractConnection$1.run(AbstractConnection.java:505) at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:607) at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:536) at java.lang.Thread.run(Thread.java:724)Caused by:java.util.concurrent.TimeoutException: Idle timeout expired: 5000/5000 ms at org.eclipse.jetty.io.IdleTimeout.checkIdleTimeout(IdleTimeout.java:153) at org.eclipse.jetty.io.IdleTimeout$1.run(IdleTimeout.java:50) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:724)2013-12-15 14:08:24.521:WARN:oejh.HttpParser:qtp2016627616-14: badMessage: java.lang.IllegalStateException: too much data after closed for HttpChannelOverHttp@45de65d6{r=4,a=IDLE,uri=-}2013-12-15 18:04:03.200:WARN:oejh.HttpParser:qtp2016627616-33: badMessage: java.lang.IllegalStateException: too much data after closed for HttpChannelOverHttp@65f92557{r=1,a=IDLE,uri=-}2013-12-15 18:10:13.920:WARN:oejh.HttpParser:qtp2016627616-32: badMessage: java.lang.IllegalStateException: too much data after closed for HttpChannelOverHttp@3090db2e{r=7,a=IDLE,uri=-}

Also i think 512MB of ram is not enough to run a node as after 2 days of continuous operation i seem to be getting heap space errors. I will continue to this monitor over the next coming days and decided if i should scale up.

In noone reports critical bugs in 0.3.19e within next 8 hours, I'll use its code for 0.3.20.

Well, except for that 0.3.19e has run for ~30-40 hours (not sure exactly) and then got stuck using 100% CPU, don't see other bugs. But it's a public node with a few hundred peers, so probably a memory leak or something of the sort. Runs on 1 GB RAM, openvz vps. Granted 0.3.18 didn't want to run at all on an openvz vps, I see a considerable improvement

Hello Everyone,I am the guy that originally developed the Mac client (username: newname) on nextcoin.org.

Graviton, I don't condone or agree with my suspension, but I do understand, as I have been in your position before. I hope one day we can move on and work together on a NXT project...

I read about the funding issue on this thread...

I am willing to pledge 5-10k in cold hard cash to a developer fund as soon as my Chase sends me a check as they have closed my accounts (they aren't crypto-currency friendly.) This check should arrive in under 15 days.

wesleyh, that looks like an awesome client! I would love to clean it up a bit and package it into a tidy application bundle for Macs under 10.9. Would you mind if I proceeded?

Good god if you could get the client to work quickly on a mac 10.6.8 I would be the happiest person on the planet.

It now checks for correct java version and is also built for 10.7+ - please check if that works.

What exactly do you mean by tidying it up? It does need an icon if you have one available. Any other features you'd like to add message me to discuss.

But anyway, I think it may prove futile. I'm using the experimental version of nxt and it seems to lag the software after a short while (even after that first time opening). Perhaps it has to do with the ton of requests the nxt client makes?

An afterthought comment in brackets is not enough. You need to clarify more strongly that its the address at the bottom of the page and NOT the actual address that the link brings you to, before someone destroys their Nxt by sending them to the Genesis address. THE ADDRESS AT THE LINK IS NOT HIS DONATION ADDRESS. Nexern's donation address is located at the bottom of the page.

Yikes, yes, it's the "donation" address at the bottom of the page. Not sure why it linked to the genesis address in that URL, I just copied the homepage, sorry.