when you accidentally view the federated timeline
stonks, GameStop, bird site
twitter thread on how a bunch of machine learning + automated trading systems "noticed" all the hype about GameStop because of the reddit troll, and then bought up shares in it, further increasing the mayhem
"Blockbuster stock up 774% this morning" is not a blurb I thought I'd read in 2021, but 🤷
(those are sarcasm squigglies)
~~~greatest nation in the history of the world~~~
uspol, covid, cdc guidelines, violence
the US needs to bathe in the blood of its children regularly. if kids are not in school being shot, then they must be in school contracting and dying from COVID.
iirc a PDA with two stacks is also Turing Complete. reasoning about such a thing would be easier than reasoning about an automaton with a queue and you could probably make a Turing Complete superset out of an existing RPN system straightforwardly. I'm certain this has been done to death a thousand times before but I find it fun to daydream about
i *think*, without having bothered to research or prove it, that probably means you could have minimal statefulness and mostly compute stuff with the queue operations and clever choice of symbols you put into/remove from the queue.
i'm assuming if I dug enough or asked around enough someone would tell me a common language I already know about was built on that principle, but i'm just spitballing
one fun computer science fact I stumbled on recently is that the class of pushdown automata (PDAs) where the stack is replaced by a queue is Turing complete. this means in principle you can compute any computable function with a finite-state machine that also has push and pop queue operations and that's it.
calling XMPP a messaging protocol in 2021 is like calling HTTP a document-serving protocol.
one thing that really hobbles XMPP is that it's usually presented as a messaging protocol. that's not what it is, though. really, it's a protocol for handling stateful interactions. it originated as a messaging protocol and is tuned for that purpose, but it can do so much more than that. any webapp you can think of could be served over XMPP instead of HTTP (obviously with lots of client code changes) and work the same way.
i have this half-baked idea that part of the reason HTTP raced forward while XMPP lagged behind is that proper stateful protocols (XMPP) are difficult to do well so people either punted or hacked a solution.
it's really puzzling to me though why XMPP isn't used more. things like fill-in-the-blanks forms and wizards are so much easier and more natural in XMPP versus HTTP (especially RESTful APIs). obviously messenging and presence is more natural too.
all of this *waves hands vaguely* needs to be stopped yesterday https://gizmodo.com/microsoft-landed-a-patent-to-turn-you-into-a-chatbot-1846113786
welp, +200 MHz on the graphics clock and +1300 MHz on the VRAM did it lol. never waste a reboot i always say
manic pixie dream walrus
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!