Topic: [ANN][AERO] Aero | 100% PoS | AeroME | Anonymous Sending - page 59. (Read 420739 times)
I hope the dev works quickly. The price will hold, but not for another month. If he could just release a beta...I think that would really help the morale around here. Even if testing went on for a while.
The new accounts who sign up from today will get 100 right away, did not have this when you signed up. But ill grant your Aerotalk account 100 AeroX anyways mate 
The aerox reward system has replaced the earlier reward for 50 posts. But dont worry, its easier to get your hands on Aero now
The aerox reward system has replaced the earlier reward for 50 posts. But dont worry, its easier to get your hands on Aero now
Awesome news! =D I'll provide my Aero address tonight when I get home from work. Stupid manager disabled my teamviewer access by adding admin/pass =/
The new accounts who sign up from today will get 100 right away, did not have this when you signed up. But ill grant your Aerotalk account 100 AeroX anyways mate
The aerox reward system has replaced the earlier reward for 50 posts. But dont worry, its easier to get your hands on Aero now
The aerox reward system has replaced the earlier reward for 50 posts. But dont worry, its easier to get your hands on Aero now
Ill have to verify at home, but I don't think I got coins for sign up. I remember there being a reward for at least 50 posts. Is this changed/updated? What can I do to rectify this is it happens to be the case (when I return home to verify)? *great idea by the way*
Great work Krypto as always, supporting this like i support aero from the beginning.
AeroTalk is proud to announce its completely own reward system, AeroX!
What is AeroX?
It's the currency of AeroTalk. You get AeroX for things you do on the forum, like posting, creating poll's/threads, giving or receiving reputation.
100 AeroX is rewarded at signup also!
An AeroX is worh exactly the same as an ordinary Aero. At the AeroX marketplace you can exchange your AeroX for ordninary Aero.
AeroTalk New Member | 100 Aero
Get 100 Aero just for signing up!
Aero for Reputation
50 Aero for each positive rep you get!
5 Aero for each positive rep you give!
New member & Rep currently doesnt work (working on a fix).
But new members will be credited 100 Aero manually within 24 hours.
Aero for Poll
100 Aero for new poll
25 Aero for each vote.
Aero for posting in the forum section!
Development
- Releases - Post 5
- Updates from Devteam - Post 5
- Suggestions & Ideas - Topic 100 | Post 10
- Support - Topic 50 | Post 20
- Introduce Yourself - Topic 50 | Post 5
- Community Projects - Topic 50 | Post 10
- Gold Campaign - Topic 50 | Post 10
- Support Us - Post 50
- Community Staff - Post 10
- Marketplace - Topic 50 | Post 10
- Trading Discussion - Topic 50 | Post 10
- Suggestion & Ideas for AeroTalk - Topic 100 | Post 10
- Whales Club - Topic 50 | Post 10
- Bitcoin Discussion - Topic 50 | Post 10
- Pump Watch - Topic 50 | Post 10
- Altcoin News - Topic 50 | Post 10
Hope you've all checked out http://www.aerotalk.netvery clean looking forum, great little community and above all the goto place to get ALL the information you need about aero!
Come join in, (and you'll get rewarded too) AeroX coming to effect soon!
Come join in, (and you'll get rewarded too) AeroX coming to effect soon!
indeed, the update was really useful for me (dev also). So the application will be a desktop app built with nodejs using node-webkit, it sounds like. Great idea, instant cross-platform and node has a really large ecosystem (npm, javascript in general)
thanks Majika
thanks Majika
As I'm a software engineer myself, your work summary sounds like Mozart to me.
Keep up the good work, mate !
Keep up the good work, mate !
Top work dev! 
Aero Community,
I have been quiet for a few days now but have no fear I have not stopped working..
It's been a frantic few weeks especially during the recent "troubles"
It turns out this was a blessing in disguise by this i mean if it was not for the fact there was a issue which required immediate attention I would not have had the chance to take a fresh look at how some of the underlying code is structured and furthermore how this will apply to our implementation of AeroME features.
I have been quietly working away on updating several components of AERO which will allow for much greater array of expand ability in the near future as AeroME is released.
The principles which drives much of my work is Keep it simple stupid (KISS). So applying this methodology to my work maintains simplicity as its core, aids in manageability of an unruly codebase and helps curb project creep.
Referring back for a moment to the recent Aero troubles It really made me focus on some of the embellishments which are not necessary in creating a superb user experience, this is not to say we do not want some of the fantastic features but what i am saying is that simplicity is key in creating best of breed Hybrid technology's both in terms of front-end UI design and also server-side business logic.
So what have i been doing?
=================
I have re-factored the majority of code to remove the "bumf"
developed various hooks on which to hang my hat. This is simply entry points for future work to integrate more tightly with when the time comes.
Streamlined the build process
Customized the automated the build process.
I have Decided to "open-up" AeroME on release to allow any developer with an interest in AeroME the ability to use AeroME components, modules, designs etc or even to build additional services on top of AeroME infrastructure.
Created new npm repository to make things more modular
Tidied up the internal documentation for both Aero and AeroME also external docs.
made heavey changes to some of node-webkit interop processes commits to follow soon.
changed the way error handling is managed
Optimized the memory heap requirements
Tweaked GC (garbage collection) stuff
Lots of DOM stuff
Continuous integration (CI) build process has been configured and moved onto separate remote servers as opposed to sitting on locally hosted machines (Atlassian Bamboo)
I'm making a start on "AIP" a set of AERO standard which are kind of like Bitcoin improvement protocol (BIP's)
plus lots more to mention.
I have Decided to "open-up" AeroME on release to allow any developer with an interest in AeroME the ability to use AeroME components, modules, designs etc or even to build additional services on top of AeroME infrastructure.I have been quiet for a few days now but have no fear I have not stopped working..
It's been a frantic few weeks especially during the recent "troubles"
It turns out this was a blessing in disguise by this i mean if it was not for the fact there was a issue which required immediate attention I would not have had the chance to take a fresh look at how some of the underlying code is structured and furthermore how this will apply to our implementation of AeroME features.
I have been quietly working away on updating several components of AERO which will allow for much greater array of expand ability in the near future as AeroME is released.
The principles which drives much of my work is Keep it simple stupid (KISS). So applying this methodology to my work maintains simplicity as its core, aids in manageability of an unruly codebase and helps curb project creep.
Referring back for a moment to the recent Aero troubles It really made me focus on some of the embellishments which are not necessary in creating a superb user experience, this is not to say we do not want some of the fantastic features but what i am saying is that simplicity is key in creating best of breed Hybrid technology's both in terms of front-end UI design and also server-side business logic.
So what have i been doing?
=================
I have re-factored the majority of code to remove the "bumf"
developed various hooks on which to hang my hat. This is simply entry points for future work to integrate more tightly with when the time comes.
Streamlined the build process
Customized the automated the build process.
I have Decided to "open-up" AeroME on release to allow any developer with an interest in AeroME the ability to use AeroME components, modules, designs etc or even to build additional services on top of AeroME infrastructure.
Created new npm repository to make things more modular
Tidied up the internal documentation for both Aero and AeroME also external docs.
made heavey changes to some of node-webkit interop processes commits to follow soon.
changed the way error handling is managed
Optimized the memory heap requirements
Tweaked GC (garbage collection) stuff
Lots of DOM stuff
Continuous integration (CI) build process has been configured and moved onto separate remote servers as opposed to sitting on locally hosted machines (Atlassian Bamboo)
I'm making a start on "AIP" a set of AERO standard which are kind of like Bitcoin improvement protocol (BIP's)
plus lots more to mention.
Wow-this is huge.Unlimited potential for Aero to become unique.Thanks Dev for update.
Aero Community,
I have been quiet for a few days now but have no fear I have not stopped working..
It's been a frantic few weeks especially during the recent "troubles"
It turns out this was a blessing in disguise by this i mean if it was not for the fact there was a issue which required immediate attention I would not have had the chance to take a fresh look at how some of the underlying code is structured and furthermore how this will apply to our implementation of AeroME features.
I have been quietly working away on updating several components of AERO which will allow for much greater array of expand ability in the near future as AeroME is released.
The principles which drives much of my work is Keep it simple stupid (KISS). So applying this methodology to my work maintains simplicity as its core, aids in manageability of an unruly codebase and helps curb project creep.
Referring back for a moment to the recent Aero troubles It really made me focus on some of the embellishments which are not necessary in creating a superb user experience, this is not to say we do not want some of the fantastic features but what i am saying is that simplicity is key in creating best of breed Hybrid technology's both in terms of front-end UI design and also server-side business logic.
So what have i been doing?
=================
I have re-factored the majority of code to remove the "bumf"
developed various hooks on which to hang my hat. This is simply entry points for future work to integrate more tightly with when the time comes.
Streamlined the build process
Customized the automated the build process.
I have Decided to "open-up" AeroME on release to allow any developer with an interest in AeroME the ability to use AeroME components, modules, designs etc or even to build additional services on top of AeroME infrastructure.
Created new npm repository to make things more modular
Tidied up the internal documentation for both Aero and AeroME also external docs.
made heavey changes to some of node-webkit interop processes commits to follow soon.
changed the way error handling is managed
Optimized the memory heap requirements
Tweaked GC (garbage collection) stuff
Lots of DOM stuff
Continuous integration (CI) build process has been configured and moved onto separate remote servers as opposed to sitting on locally hosted machines (Atlassian Bamboo)
I'm making a start on "AIP" a set of AERO standard which are kind of like Bitcoin improvement protocol (BIP's)
plus lots more to mention.
I have been quiet for a few days now but have no fear I have not stopped working..
It's been a frantic few weeks especially during the recent "troubles"
It turns out this was a blessing in disguise by this i mean if it was not for the fact there was a issue which required immediate attention I would not have had the chance to take a fresh look at how some of the underlying code is structured and furthermore how this will apply to our implementation of AeroME features.
I have been quietly working away on updating several components of AERO which will allow for much greater array of expand ability in the near future as AeroME is released.
The principles which drives much of my work is Keep it simple stupid (KISS). So applying this methodology to my work maintains simplicity as its core, aids in manageability of an unruly codebase and helps curb project creep.
Referring back for a moment to the recent Aero troubles It really made me focus on some of the embellishments which are not necessary in creating a superb user experience, this is not to say we do not want some of the fantastic features but what i am saying is that simplicity is key in creating best of breed Hybrid technology's both in terms of front-end UI design and also server-side business logic.
So what have i been doing?
=================
I have re-factored the majority of code to remove the "bumf"
developed various hooks on which to hang my hat. This is simply entry points for future work to integrate more tightly with when the time comes.
Streamlined the build process
Customized the automated the build process.
I have Decided to "open-up" AeroME on release to allow any developer with an interest in AeroME the ability to use AeroME components, modules, designs etc or even to build additional services on top of AeroME infrastructure.
Created new npm repository to make things more modular
Tidied up the internal documentation for both Aero and AeroME also external docs.
made heavey changes to some of node-webkit interop processes commits to follow soon.
changed the way error handling is managed
Optimized the memory heap requirements
Tweaked GC (garbage collection) stuff
Lots of DOM stuff
Continuous integration (CI) build process has been configured and moved onto separate remote servers as opposed to sitting on locally hosted machines (Atlassian Bamboo)
I'm making a start on "AIP" a set of AERO standard which are kind of like Bitcoin improvement protocol (BIP's)
plus lots more to mention.
Thank you for the update dev. Going open source is great news . Not to rush you but is there any timeline in which we can expect to see previews or the actual release?
Aero Community,
I have been quiet for a few days now but have no fear I have not stopped working..
It's been a frantic few weeks especially during the recent "troubles"
It turns out this was a blessing in disguise by this i mean if it was not for the fact there was a issue which required immediate attention I would not have had the chance to take a fresh look at how some of the underlying code is structured and furthermore how this will apply to our implementation of AeroME features.
I have been quietly working away on updating several components of AERO which will allow for much greater array of expand ability in the near future as AeroME is released.
The principles which drives much of my work is Keep it simple stupid (KISS). So applying this methodology to my work maintains simplicity as its core, aids in manageability of an unruly codebase and helps curb project creep.
Referring back for a moment to the recent Aero troubles It really made me focus on some of the embellishments which are not necessary in creating a superb user experience, this is not to say we do not want some of the fantastic features but what i am saying is that simplicity is key in creating best of breed Hybrid technology's both in terms of front-end UI design and also server-side business logic.
So what have i been doing?
=================
I have re-factored the majority of code to remove the "bumf"
developed various hooks on which to hang my hat. This is simply entry points for future work to integrate more tightly with when the time comes.
Streamlined the build process
Customized the automated the build process.
I have Decided to "open-up" AeroME on release to allow any developer with an interest in AeroME the ability to use AeroME components, modules, designs etc or even to build additional services on top of AeroME infrastructure.
Created new npm repository to make things more modular
Tidied up the internal documentation for both Aero and AeroME also external docs.
made heavey changes to some of node-webkit interop processes commits to follow soon.
changed the way error handling is managed
Optimized the memory heap requirements
Tweaked GC (garbage collection) stuff
Lots of DOM stuff
Continuous integration (CI) build process has been configured and moved onto separate remote servers as opposed to sitting on locally hosted machines (Atlassian Bamboo)
I'm making a start on "AIP" a set of AERO standard which are kind of like Bitcoin improvement protocol (BIP's)
plus lots more to mention.
I have been quiet for a few days now but have no fear I have not stopped working..
It's been a frantic few weeks especially during the recent "troubles"
It turns out this was a blessing in disguise by this i mean if it was not for the fact there was a issue which required immediate attention I would not have had the chance to take a fresh look at how some of the underlying code is structured and furthermore how this will apply to our implementation of AeroME features.
I have been quietly working away on updating several components of AERO which will allow for much greater array of expand ability in the near future as AeroME is released.
The principles which drives much of my work is Keep it simple stupid (KISS). So applying this methodology to my work maintains simplicity as its core, aids in manageability of an unruly codebase and helps curb project creep.
Referring back for a moment to the recent Aero troubles It really made me focus on some of the embellishments which are not necessary in creating a superb user experience, this is not to say we do not want some of the fantastic features but what i am saying is that simplicity is key in creating best of breed Hybrid technology's both in terms of front-end UI design and also server-side business logic.
So what have i been doing?
=================
I have re-factored the majority of code to remove the "bumf"
developed various hooks on which to hang my hat. This is simply entry points for future work to integrate more tightly with when the time comes.
Streamlined the build process
Customized the automated the build process.
I have Decided to "open-up" AeroME on release to allow any developer with an interest in AeroME the ability to use AeroME components, modules, designs etc or even to build additional services on top of AeroME infrastructure.
Created new npm repository to make things more modular
Tidied up the internal documentation for both Aero and AeroME also external docs.
made heavey changes to some of node-webkit interop processes commits to follow soon.
changed the way error handling is managed
Optimized the memory heap requirements
Tweaked GC (garbage collection) stuff
Lots of DOM stuff
Continuous integration (CI) build process has been configured and moved onto separate remote servers as opposed to sitting on locally hosted machines (Atlassian Bamboo)
I'm making a start on "AIP" a set of AERO standard which are kind of like Bitcoin improvement protocol (BIP's)
plus lots more to mention.
Yeah we are up to around 125 posts and 35 members in like, a week?
Pretty awesome
And about to release the crown jewel of AeroTalk.
Or, its already out there, but will write a piece and explain when its 100%. Hint, AeroX
Pretty awesome
And about to release the crown jewel of AeroTalk.
Or, its already out there, but will write a piece and explain when its 100%. Hint, AeroX
well i suppose we deserve the price crash…Its been dead quite on here.
That's because everyone is hanging out on AeroTalk
That place is gaining traction & getting fun haha.
New section up too! Check out "Aero in the News"!
If you have time go to aerotalk and vote for best new logo.
Wasn't going to but just bought up another 18000 aeros, rude not to at this price
Yeah it has. But come to the forum and chat, we can try to get some intersting topics started
well i suppose we deserve the price crash…Its been dead quite on here.
tough to get through these newsless weeks...Im curious to what the dev has planned for after AeroME. Its a tough act to follow, and it means a lot for the success of Aero. What would you guys like to see?
Jump to: