Slope initially began as a blog, so this is where most of the website’s content resides. Here we have tens of thousands of posts dating back over a decade. These are listed in reverse chronological order. Click on any category icon below to see posts tagged with that particular subject, or click on a word in the category cloud on the right side of the screen for more specific choices.
Having spent most of the night awake and working on Slope, I am nearly ecstatic to report that, well more than an hour before the opening bell, we appeared to have the necessary breakthrough. Not to jinx it, but I believe we are good-to-go!! I shall now turn my attention to my portfolio, which appears to be off to a simple fantastic start to the day. Good luck out there, and I hope Slope goes smoothly for you all.
Good morning (more or less) to everyone. I’ve been up much of the night trying to deal with a fairly severe network issue which has hobbled many of the tools (particularly SlopeCharts) on my beloved site (Substack readers are NOT affected).
Those of you on mobile are doing just fine, but otherwise, please read this quick post from Sunday to see what’s going on. It could be a number of hours (not days, hopefully, but you never know) before things are good again, and I promise to do a post to let you know when things are solid.
In between tech support calls, I’ve been checking the overnight action. Bitcoin has undone a big chunk of the exciting plunge it had earlier, although it is still down quadruple digits.
First off, if Slope is acting odd for you, please read the prior post.
More substantively, as I stand here Sunday night, the markets are roiling. I’m not sure if it was Trump’s 50% boost to the tariffs he established only on Friday, or the Iran situation, or just a crazy-overvalued market ,but equities are down nearly 1% across the board (as of now, at least; you know how these things can turn).
Through no fault of our own – – NOT THAT IT MATTERS! – – Slope started acting funny on Sunday. Not “ha ha” funny but “what the hell is wrong with this site?” funny.
The very, very good news is that we know precisely what happened, which is that the brainiacs who control Apache code thought it would be a great idea to update their code base and render a bunch of legacy rules completely unreliable. The not-at-all good news is that I can’t make any promise at all when things will be rock solid again. Suffice it to say this has the most urgent priority with our host provider and I, having 43 positions open and with the market in total turmoil, could not be MORE incentivized to get things rocking again. It’s going to get fixed ASAP, and I’ll let you know when it’s done.
Onward, Mishka!
