20230214 Site Updates

• Happy Valentine's day, everybody!
• The Feb'23 Issue of WasyaCo has been deployed: https://wasya.co/
  • Yes, I know: links don't work, it doesn't look good on mobile, styling is inconsistent, and many pages aren't working.
  • I'm developing this at a pretty consistent pace, and the overall site should be improving very quickly very soon. Cheers!

20230213 Site Updates

The FED has announced a 25 BPS Rate Hike at FOMC meeting.

True Inflation (8.89%) and Minimum Wage ($28.75/hr) in the US

ChatGPT Surpasses Instagram With 10 Million Daily Users In Just 40 Days

2023-01-26 Site Update

• I wrote a script to auto-publish a gallery of images, one image per day. So you can expect 10 new Trees to be published in the Trees category, starting tomorrow. This functionality will be used later to schedule more elaborate collections of posts. Stay tuned!

Toronto scammers successfully sold a house while its owners were out of town

Making History: AI Lawyer to Defend in Upcoming Case

Northwest Biotherapeutics Files Lawsuit Against Major Market Makers for Market Manipulation

Richest 1% bag nearly twice as much wealth as the rest of the world put together over the past two years

SWIFT payments network access cut to crypto exchanges

The reported short interest is a lie and I think can prove it!

Capitain Bootstraps

$GME: A Single Security Exhibiting Idiosyncratic Risk

Crypto used for shorting Gamestop (a colloquial anecdote)

Brazil, Price Waterhouse Coopers as the auditors, and $3.9 billion missing due to "inconsistencies"

Untitled (Evolution of apes)

Norway Is Using Ethereum (Arbitrum) for Shareholder Management

Sketch 1959

Read More >>>

Untitled ("City")

Tree #2

Two minute papers: This AI Learned Some Crazy Fighting Moves!

Inflation data for December: 6.5%

Follow the 741 Brick Road - on Tuesdays

Wall Street climbs; Powell comments avoid rate policy

Swiss National Bank reports a loss of 132B francs ($143B), which is a lot

The Story of Mel, a Real Programmer

         Real Programmers write in FORTRAN.

     Maybe they do now,
     in this decadent era of
     Lite beer, hand calculators, and "user-friendly" software
     but back in the Good Old Days,
     when the term "software" sounded funny
     and Real Computers were made out of drums and vacuum tubes,
     Real Programmers wrote in machine code.
     Not FORTRAN.  Not RATFOR.  Not, even, assembly language.
     Machine Code.
     Raw, unadorned, inscrutable hexadecimal numbers.
     Directly.

     Lest a whole new generation of programmers
     grow up in ignorance of this glorious past,
     I feel duty-bound to describe,
     as best I can through the generation gap,
     how a Real Programmer wrote code.
     I'll call him Mel,
     because that was his name.

     I first met Mel when I went to work for Royal McBee Computer Corp.,
     a now-defunct subsidiary of the typewriter company.
     The firm manufactured the LGP-30,
     a small, cheap (by the standards of the day)
     drum-memory computer,
     and had just started to manufacture
     the RPC-4000, a much-improved,
     bigger, better, faster --- drum-memory computer.
     Cores cost too much,
     and weren't here to stay, anyway.
     (That's why you haven't heard of the company,
     or the computer.)

     I had been hired to write a FORTRAN compiler
     for this new marvel and Mel was my guide to its wonders.
     Mel didn't approve of compilers.

     "If a program can't rewrite its own code",
     he asked, "what good is it?"

     Mel had written,
     in hexadecimal,
     the most popular computer program the company owned.
     It ran on the LGP-30
     and played blackjack with potential customers
     at computer shows.
     Its effect was always dramatic.
     The LGP-30 booth was packed at every show,
     and the IBM salesmen stood around
     talking to each other.
     Whether or not this actually sold computers
     was a question we never discussed.

     Mel's job was to re-write
     the blackjack program for the RPC-4000.
     (Port?  What does that mean?)
     The new computer had a one-plus-one
     addressing scheme,
     in which each machine instruction,
     in addition to the operation code
     and the address of the needed operand,
     had a second address that indicated where, on the revolving drum,
     the next instruction was located.

     In modern parlance,
     every single instruction was followed by a GO TO!
     Put *that* in Pascal's pipe and smoke it.

     Mel loved the RPC-4000
     because he could optimize his code:
     that is, locate instructions on the drum
     so that just as one finished its job,
     the next would be just arriving at the "read head"
     and available for immediate execution.
     There was a program to do that job,
     an "optimizing assembler",
     but Mel refused to use it.

     "You never know where it's going to put things",
     he explained, "so you'd have to use separate constants".

     It was a long time before I understood that remark.
     Since Mel knew the numerical value
     of every operation code,
     and assigned his own drum addresses,
     every instruction he wrote could also be considered
     a numerical constant.
     He could pick up an earlier "add" instruction, say,
     and multiply by it,
     if it had the right numeric value.
     His code was not easy for someone else to modify.

     I compared Mel's hand-optimized programs
     with the same code massaged by the optimizing assembler program,
     and Mel's always ran faster.
     That was because the "top-down" method of program design
     hadn't been invented yet,
     and Mel wouldn't have used it anyway.
     He wrote the innermost parts of his program loops first,
     so they would get first choice
     of the optimum address locations on the drum.
     The optimizing assembler wasn't smart enough to do it that way.

     Mel never wrote time-delay loops, either,
     even when the balky Flexowriter
     required a delay between output characters to work right.
     He just located instructions on the drum
     so each successive one was just *past* the read head
     when it was needed;
     the drum had to execute another complete revolution
     to find the next instruction.
     He coined an unforgettable term for this procedure.
     Although "optimum" is an absolute term,
     like "unique", it became common verbal practice
     to make it relative:
     "not quite optimum" or "less optimum"
     or "not very optimum".
     Mel called the maximum time-delay locations
     the "most pessimum".

     After he finished the blackjack program
     and got it to run
     ("Even the initializer is optimized",
     he said proudly),
     he got a Change Request from the sales department.
     The program used an elegant (optimized)
     random number generator
     to shuffle the "cards" and deal from the "deck",
     and some of the salesmen felt it was too fair,
     since sometimes the customers lost.
     They wanted Mel to modify the program
     so, at the setting of a sense switch on the console,
     they could change the odds and let the customer win.

     Mel balked.
     He felt this was patently dishonest,
     which it was,
     and that it impinged on his personal integrity as a programmer,
     which it did,
     so he refused to do it.
     The Head Salesman talked to Mel,
     as did the Big Boss and, at the boss's urging,
     a few Fellow Programmers.
     Mel finally gave in and wrote the code,
     but he got the test backwards,
     and, when the sense switch was turned on,
     the program would cheat, winning every time.
     Mel was delighted with this,
     claiming his subconscious was uncontrollably ethical,
     and adamantly refused to fix it.

     After Mel had left the company for greener pa$ture$,
     the Big Boss asked me to look at the code
     and see if I could find the test and reverse it.
     Somewhat reluctantly, I agreed to look.
     Tracking Mel's code was a real adventure.

     I have often felt that programming is an art form,
     whose real value can only be appreciated
     by another versed in the same arcane art;
     there are lovely gems and brilliant coups
     hidden from human view and admiration, sometimes forever,
     by the very nature of the process.
     You can learn a lot about an individual
     just by reading through his code,
     even in hexadecimal.
     Mel was, I think, an unsung genius.

     Perhaps my greatest shock came
     when I found an innocent loop that had no test in it.
     No test.  *None*.
     Common sense said it had to be a closed loop,
     where the program would circle, forever, endlessly.
     Program control passed right through it, however,
     and safely out the other side.
     It took me two weeks to figure it out.

     The RPC-4000 computer had a really modern facility
     called an index register.
     It allowed the programmer to write a program loop
     that used an indexed instruction inside;
     each time through,
     the number in the index register
     was added to the address of that instruction,
     so it would refer
     to the next datum in a series.
     He had only to increment the index register
     each time through.
     Mel never used it.

     Instead, he would pull the instruction into a machine register,
     add one to its address,
     and store it back.
     He would then execute the modified instruction
     right from the register.
     The loop was written so this additional execution time
     was taken into account ---
     just as this instruction finished,
     the next one was right under the drum's read head,
     ready to go.
     But the loop had no test in it.

     The vital clue came when I noticed
     the index register bit,
     the bit that lay between the address
     and the operation code in the instruction word,
     was turned on ---
     yet Mel never used the index register,
     leaving it zero all the time.
     When the light went on it nearly blinded me.

     He had located the data he was working on
     near the top of memory ---
     the largest locations the instructions could address ---
     so, after the last datum was handled,
     incrementing the instruction address
     would make it overflow.
     The carry would add one to the
     operation code, changing it to the next one in the instruction set:
     a jump instruction.
     Sure enough, the next program instruction was
     in address location zero,
     and the program went happily on its way.

     I haven't kept in touch with Mel,
     so I don't know if he ever gave in to the flood of
     change that has washed over programming techniques
     since those long-gone days.
     I like to think he didn't.
     In any event,
     I was impressed enough that I quit looking for the
     offending test,
     telling the Big Boss I couldn't find it.
     He didn't seem surprised.

     When I left the company,
     the blackjack program would still cheat
     if you turned on the right sense switch,
     and I think that's how it should be.
     I didn't feel comfortable
     hacking up the code of a Real Programmer.

The Truth About CBDCs: an Analysis

…The Truth About CBDCs… Design Choices by ECB & FED Analysed… Both Are Aiming At Tight Control Over Accounts, Interest and Spending... A Digital Prison Is Being Built in the Shadows… [Due Diligence]

Massive overreach of Central Banks underway.They are designing a new kind of money allowing them to:

• Establish centralized settlement of ALL payments…

• Tie digital identities to all transactions and record them on a central bank ledger forever…

• Force built-in features such as limits on how much CBDC you can have in your account, negative interest rates, account charges in line with regulatory objectives, and caps on conversions and spending…

• Create “money” that is traceable, programmable, taxable, and subject to the monetary whims of central planners…

• Stamp out spending without permission and slowly phase out cash…

The war on money continues. The aim: to replace cash with a system of centralized control over ALL transactions and account balances.

This report explains exactly what to expect from Central Bank Digital Currencies (CBDCs); it looks at the possible design options, what central banks have decided so far, and the likely outcomes.

The ugly conclusion is that CBDCs are a new form of currency that allows a small group of unelected people control over what we can, and cannot do with our own money…

Crypto Empire DCG Faces US Investigation Over Internal Transfers

2023-01-07 Site Updates

Let's All Dance the Melvin Superswap

Howdy Ape-areenos,

I just got around to watching the 2 part GME series on HBO MAX titled Gaming Wall Street, and it was refreshing to see our side of the story told authentically after a year of gaslighting by the media. I know that the issue is complicated and it’s hard to create and sustain a captive audience around complex financial instruments. However, it did not sit well with me that I finished the series with no real idea of any tangible, targeted requests that the general public could make to reform wall street. Sending a letter to your senator saying the market is corrupt and it needs reform is simply too vague to take action. It also did not sit well with me that the story ended with the narrator throwing up their hands and saying that maybe Melvin swapped out the liability somehow, and no one really knows what is going on. I think the research done in this sub paints a pretty compelling picture of what happened, and there are signatures of it all over the data that we do have access to.

I hope that this post sheds more light on these swaps, and allows the broader community to begin to understand what is going on here. This work builds off of some great DD by others in the community, namely u/Zinko83 and u/Mauerastronaut on variance swaps. As with all of my posts, it would not be possible without the efforts of the group of people that u/Gherkinit compiled in the community to investigate the derivatives used on GME. Without the rule documenting, data collecting, and derivative investigating done by this group, I would not be able to write this post.

Let’s start where the documentary left off.

Silvergate Shares Plunge 46% as Crypto Bank Cuts 200 Jobs

• The company also said it is writing off its investment in former Facebook stablecoin project Diem.
• Crypto bank Silvergate Capital (SI) has cut 40% of its staff
• Read more here: https://www.coindesk.com/business/2023/01/05/silvergate-cuts-40-jobs-writes-off-diem-asset-acquisition/

A review of Aswath Damodaran's youtube channel about accounting

Intro

Bed Bath & Beyond Warns It May Go Out of Business

• Company includes going-concern warning in SEC filing
• Retailer weighing options, including potential asset sales
• Full story: https://www.bloomberg.com/news/articles/2023-01-05/bed-bath-beyond-issues-going-concern-warning-reviews-options

Tree #1

U.S. DOJ in process of seizing Robinhood shares tied to Alameda Research loans

Titled, Our Lady Sound Monetary Policy

Unfortunate... Crypto firm Wyre winding down after failed Bolt deal

An Iron Dog

Turns out (1) University of California gets to gamble with - presumably students'? - money, and (2) Blackstone casually "guarantees" an 11.25% annualized return on investment for 6 years

American politicians continue destroying the value of labor

Protagonists :: SURVEY

Inversion of 2yr/10yr Treasury yields has been a historically accurate leading indicator of recessions.

Some Book recommendations

Published on July 24, 2018.

Titled, The Plight of the Homeworker

Every indication that 2023 will be a miserable year

Shorting and FDT'ing on Bonds and T-bills is the most direct way to extract wealth from population, by increasing money supply and inflation

Bilderberg - the Movie (2014)

Here is the graph of Bilderberg Group participants' connections to every major company and institution

Productivity vs real earnings in the US -- what happened ca 1974?

US bitcoin miner Core Scientific files for bankruptcy

• Core Scientific reiterated it could run out of cash before the end of the year as lawsuits are piling up.
• Core Scientific has been affected by the bankruptcy of lender Celsius's mining arm, one of its biggest clients.
• Two other companies sued CORZ in November: Sphere 3D (ANY) and McCarthy Building Companies. A class-action lawsuit was filed in the same month in Texas courts alleging failures to disclose important information to investors.

Japan Securities Clearing Corp (JSCC) issues emergency margin call

Who runs the world? Blackrock, Vanguard and State Street