Be sure to report him to abuse@telegram.org, the more reports the more he'll be flagged.

Thanks, and although I've taken a short hiatus, it was mostly to throttle new purchases so I can mitigate any possible problems when I will force everyone to upgrade to the new keycode system. (*gasp* *red flag* dracoix doesn't care about sales, I call bs!) It really is true, about 10% of every keycode purchase has a problem in some way already, either via user error or it derped and I have to manually create a new one. I don't want to create a hundred of them by hand. So, I've been spending the majority of time fixing that issue with a new method and I've been upgrading my homelab equipment quite a bit thanks to previous purchases. I want to thank you all from the bottom of my heart for putting my hobby upgrade on the fast track. Development will return shortly either before or right after the Bitcoin fork. I'm trying to get my homelab finished before the fork. Moonshot has reached to the point where I need to have SonarQube running, have an actual internal git/svn, and a new workstation to profile/optimize it live... so I got a Threadripper 1950X, should do the trick. The end result should have Moonshot be able to run on an i3 potato, a macbook, or even an AMD APU.

tl:dr: I'm committed, not dead, just went out to get equipment and weaponry to bash some problematic walls down.

Not sure, past 2 weeks I've been doing other things, but I have been getting an influx of users trying it out.

Weekly bump.

As Moon Alert's bigger and fatter brother Moonshot progresses, Moon Alert gets extremely outdated. Moon Alert only sees 5mins at a time and uses at most 20 days of data for that 5mins report.

There is a small explanation when the app first loads what each field means.

LATE is basically an arbitrary 'too late' to get in on the ride.
Conf% (I think) is attached to the 30min base-volume percentile compared to 20 days of data -OR- the 5min base-volume percentile.
PCA is a fudge number meant to be the realistic 5min price change% weighted to the average price changes of all 20 days.

The rest are better explained in the info when the app first loads.

Make sure the latest Java 8 (not 9) is installed and is 64-bit. Also make sure Java has permission to run on the machine.

New base-build b2166 available.

Success has been awesome for myself when I'm not being stupid (currently in the hole). It only looks at the here and now and it'll do its best to find anomalous volume activity, but it's not perfect. Usually you have about 30 seconds to react to an obvious pump & moon ride. It will get into bull traps because it doesn't care about price as much as volume.

Daily bump. (Just to make people aware of the scammers.)

Quiet you :p. It'll be will be out soon^tm. Probably the same time I figure out how to deal with Kraken and Bitfinex, because all the api calls will have to be universalized and not spaghetti.

It already does that intelligently, and there's a settings file (because I haven't made a UI for it) that can disable an exchange and specific pairings for Bittrex. Poloniex is a little difficult since it's all asynchronous and I have it loading data dynamically for that api, but the bandwidth for it is tiny compared to Bittrex. Bittrex has an order of update (Bulk first and every 30 mins) -> Market Summaries (every second) -> Tick (if market changed) -> Orders (if market actually is anomalously active). Also Bittrex is always 5 minutes away from completely desyncing and falling on itself if it keeps sending bad/empty data via HTTP. I've been looking into it's SignalR websocket, but the actual library for it is massive and cumbersome for java. Poloniex's websocket is simple and uses the open standards, only needed a few lines of code to hook up to it, and another couple hundred to filter it.

1) When I fix up the chart, sure.
2) That's your problem lol

And as for a data sprew service, that's getting planned for Moon Alert Classic. Eventually that part will be all open source to tear apart.

Thank you. I guess it's time to change up my keycode auths on next few builds and wreck his day.

The signals are not as reliable. There is a buy signal, it's just really really rare and before I started developing Moonshot I stopped using those in favor of looking at the raw statistics such VA and VM and the Conf. Classic currently uses continuous bulk and tick data, it takes a while.

Make sure you have a fresh install of Java 64-bit JRE, download link is on the main post.

Wow, this thread actually needs a manual self-serving bump for once. Altcoin bloodbath trial keycode is still good until tomorrow. I plan on releasing the new build sometime this weekend. Classic 1.1 is thrown up in the air as I'm having difficulty in making asynchronous stuff...... synchronous for a text-based console window. It was easier when I just kept on bulk scanning and fake-delayed, but the new candle system and network code just can't do that.

Classic 1.1 comes with Poloniex support too, it might be a while but I'm making it top priority. :p

ANN: Due to today's (9/4) altcoin sell spree, I'm ramping up development for Poloniex and Classic 1.1 coding. Meanwhile I'm giving everyone a 3-day Moonshot trial keycode that will last until 9/7, crypto coins should not have to all pay for one country's decision making. Go make your coins back.

e40aba303f12d7b4-38a61aa3ce8d69ef-4e21e48a2b1bb046-41e4e0ed26128503-3350de639db0a2c8-f9b62d6e6b0d96b6

I'll get a Mac OS VM to test out classic. And I wouldn't trust signaling, especially with today's china ico bloodbath.

Unexpected bear market day, perfect for debugging, more coding, and also for people to take advantage of what Moonshot is really meant for... rare moonshots.