>>13796114 pb
>q v2021.03-03.js
Hey, I have been updating the baker tools for a while now, any reason to pref this one, other than a lighter experience? Let me know if there are features that you want in the next release of the 0.7.5 version of baker tools. Thanks.
Yep cannot argue with that. I got very comfy with the version I "maintain" and add features that I personally want from lurking or baking. Don't think I have had a single legit feature req.
Thanks, forgot to go back in there and check for any useful response, not surprised at what I got back.
Sure I will bite, I copied the q functions to begin with since it was closest to the structure I needed, replacing tripcodes with that I learnt was capcodes. I got it working all but updating the numbers when there was a new BV post, so I was asking for a reply to test both the per post triggers that was meant to update the numbers, as well as testing the bv (you) logic. In the end of the same bread I clarified that the BV (you) was not required. I wanted the BV functions because since they are now more active, it would be handy to know if they are making exec decisions while baking. I use the tools more and more to make what I am interested in stand out above the sea of bullshit that I usually don't filter but let go to one of the fade handlers. I outed myself when I said that I was a perma lurker and occasional baker and updater of baker tools. What else is it that I am hiding? I give heads up that it takes a while on first load cause it iterates over every post in a bread at first load for marking features, so first load will be slower, not recommended for phone fagging or potatoes.
So let's see your specific complaint, what class do you have a problem with? Show me your superior coding and I will make it a part of it. Tell me specifically what your beef is without asking another question or making another vague assertion that requires more follow up questions. I fucking double dog dare ya to succinctly detail your complaint and preferred solution.
*Baker Tools v0.7.5: https://controlc.com/a0409084UPDATED!, >>>/qresearch/13764032
A feature I briefly considered putting in this release, to allow you to mark bv (yous) (posts that reply to you and are made with the bv capcode, which is the red text that starts with ## Board) with a custom colour and be able to navigate them using top board controls as well as marking them in the sidebar. Decided it was not required.
Thanks for reviving this thought, things have escalated since then, in the absence of principles I request numerous BVs perform their anti-spam work hard so we can hopefully go back to tribal rule. Probs not going to happen since they are very verbose and there is no longer a line between bv work and bv shitposting. I've accepted this is just a new flavour of noise to put up with here.
> to allow a Baker to moar easily see a BV post, correct?
correct
> Sounds like it would really come in Handy
That's what I thought and why gave my time to give it back to you all.
>>13716716 pb
>>13717003 pb
For reals? These are questions I asked, I aint no shill, even more confused on the "rules" now.
My pleasure, but I do not do the lite version, I just add features to the bulkyboi.
I think I get it now, a "shill" repeated my question and verbose bv verbose bv'ed, righto.
Feel free to point out the malicious function or code, because you obviously made that comment based on known facts right, rabbi? Is that how we play this game?