Yeah, it's really sad, isn't it?
Especially since I had quite a good time here, and met nice people. Goodbye, CLOAK. One last time with capital letters again, just like at the beginning.

To be honest, I think it's over now and rebuilding trust is not an option anymore. When all the fudders came in, there were still some people trusting the coin and others who just were in to ride the waves (maybe to compensate their losses). But now, there isn't even any volume anymore.

Closing the eyelids of the cold cloak and giving it one last hug.

I guess the coin will now slowly fade away. But not because of YourMother's "heroic act"; it's more the devs' work.

To this I-told-ya-YourMother-was-right-guy: I didn't lose on cloak, either. Instead of "cutting my losses", I flipped the coin and made it back. All of it. Now that this goal is achieved, I'm out, too. Moving on, learning more and leaving potential investors in this thread the message to be very, very careful.

Of course he was right. But saying "thank you" to a low life who feels the compulsive need to call others all kind of primitive names? I don't know in what kind of society you live, but where I live, we don't do that. Before I say "thank you" to it, it should apologize first. But we all know that's not gonna happen (not sure if he is still able to post, though ^^).

.edit:
Shall the attendance of this thread drop, I don't care. It's not only since yesterday that I'm out.

gimme a c
gimme an l
gimme an x
gimme an r
gimme a 29
gimme a wooden plank!
C-K-A-L-O-K!

^^

CAOLKC!!! HDOL!!1

lab rat hoax: only hard to imagine if you don't consider that the project might have brought big gains to some individuals.

Short answer: no / we don't know, sadly / we don't know, sadly.
Although I'm not sure if that was an unexpected answer. ^^

If your time allows for it, you're welcome to join the thread: https://bitcointalk.org/index.php?topic=783089

Version updates / development progress will be documented here.

2015-10-20
Updates:

• Lots of charts added for coins on Bittrex
• Implemented charts for cryptoId.info's rich list feature, which will enable you to selectively monitor coins/wallets at a later stage

2014-09-18
Updates:

• Trading view: implemented search feature for all markets on Cryptsy (uses live data from the API)

Next steps:

• Improvements for handling API data (got some issues with script timeouts due to the amount of data being loaded and processed)
• Storage of historical data in the database (on a hourly basis) for all coins (Cryptsy)
• Setup of the application on my server, so interested users can have a look

Dear community,

I'm currently using my spare time to develop a charts/trading suite. The reason is that I'm not at all satisfied with the trading experience and the amount of information the charts on the exchanges present. There are way more possibilities and I have no idea why they aren't used. So I started developing (at the beginning only for myself) and from time to time, I was talking about my project on several threads and in IRC chats, and I got quite some resonance. So I considered to continue developing with the ability to let users also use this project in mind, and to not miss the point and waste time into coding something noone wants to use, I wanted to share my idea and ask for some feedback. The project is in a quite early stage of development, so there is room for ideas and improvements.


Some things about me

I live in Germany and I'm a web developer by profession. For the most part, I'm making TYPO3 websites for our customers (for the Americans and other people who maybe don't know TYPO3: it's an open source enterprise CMS - content management system - like Drupal, Wordpress and so on, very extensible and with a very, very active community) and I have quite a lot of experience in

• PHP development (mostly developing TYPO3 extensions, also TYPO3.Flow, which is a framework... to explain what TYPO3.Flow is, i often say "TYPO3.Flow is to PHP what Rails is to Ruby"), OOP/MVC
• JavaScript magic (plain JavaScript as well as jQuery, jQueryUI, mootools, ExtJS, Sencha Touch, ...)
• GNU/Linux server administration, shell magic, ...
• some other fields of web development which do not really matter here

I'm working for a small web agency in Karlsruhe since several years now, being in home office due to me and my wife moving places at the end of last year (about the same time as the last - up to now biggest - Bitcoin price run, heh). My spare time goes to a big extend to the development of private projects like this one.


Planned features of the application

Newsletter (see an image of the current version here):

• different subscribable versions of a newsletter will be available
• newsletters will cover various exchanges, beginning with Bittrex (implementation almost complete) and others following
• newsletter contains an overview about how which coins perform
• historical data is displayed for the last ~25 days
• more detailed information and charts can be found on the website

Technical analysis:

• storage of historical data (not sure about how much data there will be stored... Cryptsy e.g. has way more than 100 coins listed)
• implementation of different subscribable trading strategies with different levels of complexity - suggestions are welcome
• notifications (e.g. email) if a trading signal (e.g. moving averages crossing each other) occured
• configurable JavaScript based charts displaying excessive information which we don't see on the exchanges (no idea why they don't implement more features... they have the charts, they have the data - it's easy!)

Market analysis: displaying information (with nice charts, graphs and diagrams) we don't see on the exchanges, such as

• relations between time, volume and price movements to detect - if that's possible at all, I'll have to investigate this - recurring events
• major price movements of certain coins: which coins have gained/lost unproportionally much value in a certain amount of time?

Trading (Live/Auto): Update 2015/01/20: Focus of trading features has ceased a bit and shifted towards charting and TA. For that reason, the trading features are planned for a later version, if any.

• trading on the exchanges with improved user interface (although there is still one problem to solve: I do not want to handle users' trading API keys; although I'm quite experienced in handling GNU/Linux servers, I'm convinced that there is always someone with better skills to hijack the server, and I don't ever want to be in the need to tell people why their accounts got wiped... maybe I find a solution to outsource the API connection into the client, we'll see)
• adding buy/sell orders: single order or by setting an amount of orders to place as well as a range, so the intermediate orders between min and max value are calculated automatically
• in the table of own buy/sell orders, there are buttons to cancel and edit (remove and re-add) single orders as well as to remove all own orders
• "Auto Pump/Dump" feature (sorry, didn't come up with a better name yet): either set a slider for the target value (needed amount of cryptocurrency is being calculated and displayed prior to execution) or enter an amount to invest into buying/selling (the target price is being displayed)
• fill gaps on buy/sell side when pumping/dumping the market
• option to remove all buy/sell orders before pumping/dumping the market
• overview of current buy/sell orders on the market
• nice chart of current price development, optionally with trend indicators
• automated trading using a bot with different trading strategies

Account settings
Of course, there will be account settings with options on which trading strategies to subscribe to, the type of notification used when certain events (buy/sell signals etc) occur.


General information about the project - the backend

The backend is a TYPO3.Flow application which is totally separate from the frontend. This brings some benefits: as TYPO3.Flow can be easily instructed to deliver JSON data output, it's easy to create APIs which can be used by totally independent frontends (although it sounds funny: creating an API for an application which uses APIs of exchanges).
All the logic is handled by the backend:

• reading data from database
• writing new data to the database
• querying APIs of the different exchanges

General information about the project - the frontend

The frontend is provided by a separate TYPO3.Flow application which connects to the backend. Its main purpose is to display data (plus some JavaScript calculations which are more performant to be executed client-side instead of server-side). For doing so, I purchased a license for a really powerful template called "SmartAdmin". It's normally used for implementation in backends, but depending on the view - when development has progressed so far that users can log in to the service - it actually is a backend.
It provides (amongst others) the following features:

• UI components based on twitter bootstrap and jQueryUI
• a charting/plotting library (for our beloved candlestick charts, I had to implement another library called "AmCharts", as the included library "flot" had a separate plugin for candlesticks, but I was not satisfied with that one... AmCharts is free for personal use; however, when the application goes online, I have to purchase a license for some 140 or 280 $ (depending on what features are used), but as AmCharts is really great, I'm more than willing to pay the price
• the whole frontend layout

SmartAdmin is a great template. However, it took a lot of time to actually wrap my head around it, as it provides a ton of sample files with ui elements of all kinds, each with up to more than a thousand lines of code.


Goals achieved so far: backend

• setup of new TYPO3.Flow application "BitShit.Backend" with models required to store historical data (atm for only one coin, as I'm still in development phase and I have no need of other coins, yet)
• implementation of the complete cryptsy API (I just saw recently that someone already coded a library for that, heh)
• basic implementation of some simple/complex trading strategies based on historical data (calculated in the backend because historical data is completely handled by the backend/fetched from database... trading strategies used on short term/live data will probably be calculated in the frontend, as the data comes from the exchanges' APIs directly)
• usage of PHP PECL package "trader" for trend indicators etc

Goals achieved so far: frontend

• setup of new TYPO3.Flow application "BitShit.Frontend"
• integration of "SmartAdmin" template for UI elements
• found and implemented nice candlestick-capable JavaScript charting/plotting library "AmCharts"
• calculation of several trend indicators (for the moment it's just SMAs, more to follow)
• basic version of the "Technical Analysis" menu point (mainly just a chart for the moment with trend indicators for use with a certain trading strategy I implemented for use with historical data)
• built view "Trading (Auto/Live) -> Cryptsy" with a chart representing current market data (also for a single coin for now), adding of new buy/sell orders (amount of orders as well as range (for multiple orders) customizable), output of lists of current own open buy/sell orders with buttons to edit/cancel, option to "pump/dump" the market with options to fill gaps created in orderbook as well as to remove all own buy/sell orders before unloading coins on the market, and an overview of current open buy/sell orders on the market (all those points are pure frontend work (besides the chart displaying real data), the features have yet to be connected to the backend/exchanges APIs)
• built a basic version of the user settings screen
• built a basic version of the newsletter
• implemented cryptoId.info's API to monitor coins/wallets for large movements

Screenshots

Newsletter (2015-01-10):


Technical Analysis:


Trading (Live/Auto):


Settings / Notifications:


Top Coins / Bittrex (added 2014-10-13, will contain more exchanges for direct comparison as well as historical data)


That's it for now. Main reason for posting a project which is in development was because I mentioned it in another thread and I got so much positive resonance that I thought that I take the opportunity and open a separate thread, so the development of current features can be discussed. Also, if some good ideas about features people wish to see/use arise, I'd consider to implement them.

I'll keep this posting updated with current development progress, and if you have questions, critics (constructive, please) or wish to discuss anything, please feel free to post your reply.


.edit:
At the moment, I'm developing locally, but soon I'll take the time to remove all private data from the source and put the application on my server.

.edit2:
Fixed some grammar and typos.


Next steps:

2014-09-15:

• Implemented on 2014-09-18: Selection of trading pair in the "Trading (Live/Auto)" view, as currently, there is only one coin being used

2014-09-19:

• Improvements for handling API data (got some issues with script timeouts due to the amount of data being loaded and processed)
• Storage of historical data in the database (on a hourly basis) for all coins (Cryptsy)
• Setup of the application on my server, so interested users can have a look (2014-10-13: suspended for now, as I have a lot of features to develop before putting it live… so, when it goes live, it'll hopefully be more usable than a half-ready product)

What do you mean, "I'm back in"? Back invested in cloak or back in the discussion?

"Did you tickle my feet? You know that always wakes me up!" - This is so awesome. I liked it when Bob tipped you 50 bucks for that, well deserved.

I don't know what happened, but until now, there was exactly ONE time i saw someone "advertising" another coin and it was totally okay. That was the guy comparing cloak to DRK some pages ago, with a totally friendly tone, in no way annoying and he just pointed out that development, pr/announcements and so on can be handled way better than it is being done here. So he showed up how this is done over at DRK. And all he wrote seemed just like friendly, honest advice.

As a rule of thumb, it would be good if people treat other coins' threads like they want "their" thread to be treated. If everyone followed that simple rule, we would have way less problems with spam.

I tried something new. I used the "report to moderator" link.

Please, go check your blood pressure :*

.edit: time for this to end, YourMother.

Yeah, that sounds good. In fact, I already "started starting a topic" (I guess, with me, all things just take a bit longer ^^), meaning I started writing the text. Every time something important to be mentioned there comes into my mind, I add it. I think that's the first public posting of an application/service and it has to be good, providing all the information about current state/planned features users might be interested in.

I'd be happy to talk about some coding stuff there, as I have some points (e.g. calculating OHLC data from the single trades... not sure if there's a library yet, and I don't want to reinvent the wheel, but if there isn't, I'll code a library myself, although I'm not sure if I want to put this on the client side, as the 1000 sets of data cause the script to hang) which are worth discussing.

To the user interface: I think in the world we live in, it would be insane to build all those UI elements by hand.
I bought a license for SmartAdmin (uses bootstrap and jquery-ui along with some other libs) which provides the UI elements. But while developing, I already thought that it might have been easier to build those elements myself instead of implementing SmartAdmin
Reason is: SmartAdmin is a template for use in backends. You have a ton of sample pages, each up to multiple thousands of lines of code long, using different features with different libraries to be included. Took some effort to wrap my head around it, but it was worth the time.

Also, SmartAdmin used the JavaScript library "flot" for plotting charts. I was not satisfied with it, mostly because another plugin was needed to display our most needed chart type: candlesticks. So I had a look around and found AmCharts, which I implemented. Currently, it's free, but when my service goes online, I'll have to pay some 1-200 bucks. But as it's really a great, powerful library, I'm more than happy to pay it.

Nope, I didn't. I learned here (edit: I mean the forum in general, not this particular thread) that it's really hard to know whose advice you can trust and whose you cannot. So I decided not to take any advice at all. Sad for those who really try and give helpful advice, but there are so many shady characters in this forum that it's more safe to consider everyone shady until they proved you wrong and use the time to learn making own decisions.

.edit:
Looks like no help is needed. It was worth a try.

... he did not really get a message, he was just being cynical.

Hey,

thank you for your kind words. One potential problem I see is the sheer amount of data which might add up after time. I cannot estimate how much that will be in the database. But for the moment, I'm coding locally with an Apache/MySQL webserver/database on my notebook, and I store data from one coin (development phase... no need to add more, yet) and only the open/close/high/low of every full hour to prevent me running out of disk space.

However, Cryptsy has way more than 100 coins in their exchange, so I'm awaiting the data collection testing phase with agony and fear. ^^

Today, I did some frontend work and I partially implemented a user settings view and a view for trading with different options which are not provided by the exchanges. It already displays real data, but next time I get into JavaScript Wizard Mode, I'll have to provide the functionality which does all the magic.

Here is another screenshot; it'll be the last one here. I'll open up a thread soon (this weekend, maybe), but I have to spend some time with my wife first. She's a bit mad because she thinks I'm spending too much time on the computer. Well, actually, she's right. Kind of.

Click here for the image; I can't get this forum software to display the thumbnail of the screenshot
I see, I have to open a separate thread, as I don't want to hijack this one or people getting annoyed.

Hey buddy, how's the weather?