NiftyHacks
1.7K subscribers
129 photos
32 files
331 links
No paid calls at all! Just sharing of whatever little tricks and hacks of Market I know! @stockManager01 and @Stock_Expert01 are running one fake channel using my name. Be aware of them and report their profiles to @notoscam of Telegram.
Download Telegram
NiftyHacks pinned ยซAs many have requested the link to all the stgs along with shared codes, refer attached link. Save for future updates also. https://docs.google.com/spreadsheets/d/13gB_jyN7UF67KtczZy1rCJ1fgMhvy2YY/edit?usp=sharing&ouid=112513580888985653812&rtpof=true&sd=trueยป
These below stgs need to be removed as Volunteer need 2 slots back. Below are Stats and excel data of deployment till yesterday, for anyone interested. I thank him (want to remain anonymous) on behalf of our group for providing slots for so long ๐Ÿซก๐Ÿซก๐Ÿ™๐Ÿป Also I will try to deploy these 2 strategies on other slots and update shared codes on Sheet again within couple of days.
Seems like margin requirements hav gone up in last few days, so keep an eye for any margin related error executions. Better to keep extra 20% margins for selling stgs than capital requirements shown in every stg.
It seems like TT's rule of marking stg as "inactive-blocked" if user is inactive for 7 days is affecting working stgs' conditions' checks negatively. Experienced this few times now, latest example is Sea Treasure stg, where a simple Universal Exit didn't work on last monthly expiry day, the stg got marked as "inactive-blocked" few days earlier.

Why I think this rule is not required! Bcoz many times we as users put stg deployment for testing quarterly results on paper trade or live offline on some volunteer account or another TT account, so we might not login to TT for long time. Now what this rule says is u need to login to TT account within every 7 days, which we might forget sometimes. This will mark stg as inactive-blocked, which will get removed as soon as we login to TT, but then stg, even though is active or live entered, don't works afterwards.

If u also thinks this rule is not required, I've tweeted TT to remove this, u can also tell them by retweeting this below tweet.
NiftyHacks
https://x.com/NiftyHacks1/status/1961619827346608186?t=8aO-HXkiqBfL9wFDQMsS-A&s=35
What will happen if this "inactive-blocked" thing Either not removed Or not modified by TT to work properly in a robust way (once login done)?! In other words how will it affect our group?

So most of our stg Shared codes that are uploaded on sheet for u guys convenience to track performance, are deployed on volunteers' accounts, accounts that they no longer use or extra slots. Now many will not even bother to login to their respective TT account for long, for same reason that they no longer use that account. For last few weeks, they are doing this login every week thing out of gratitude towards the group, but I can't remind them every week again and again if stg goes to inactive-blocked status, if they fail to login.

So if we fail to retweet this above tweet in massive number by tomorrow, I will be forced to remove the shared codes from sheet for members who will tell me that they won't be able to login every now and then, which I'm already told by few now.

So if u guys thinks shared codes are helpful to Track stg performance on Long Term and needed on sheet, EITHER retweet and force TT to take some action in robust functioning of stg after inactive-blocked status get removed once login done OR else TT should just remove this stupid rule of login every week compulsory. Otherwise I will be forced to remove shared codes from sheet.

Now the decision is on u guys.
Added 2 more versions of Nebun Keturi and Harom Idiota on sheet, on request of few members, which will start from 916. (*For those who are following these)

Members can request any modifications they want in any stg, I will try to do that if possible easily from my side and add link on sheet for that.
I'm getting few queries in last few days, that's why need to put this message. I will not be able to reply or respond until late February or may be March due to some busy schedule ๐Ÿ™๐Ÿป