pull down to refresh
They're not wrong, but is Zitron in turn really wrong when he says that they lie all the time, that there's circular moneys going on in ways that are unsustainable, and that the products until now have not lived up to the hype the creators made? Much of this is verified fact, the difference is that he is offended by it, where everyone else seems to really need the break after their multi-whole-coin jpegs went to nil.
The only thing that really made me wow were some of the seedance 2.0 clips, which I don't recall to have seen matched after launch day and I was unable to create good video with it myself. But that's not the kind of disruptive thing that puts us straight into the age of abundance; it's a narrow field.
So, I don't know if it's all going to collapse; I think it's possible, but it's also possible that they manage to avoid it. The lying and printing has to stop at some point tho, I tire of it.
And then people, even stackers that should know better, ask me why I am so autistically retarded that I dislike the system and don't wanna borrow money. Because it's a fucking atrocity, that's why. I don't want to be part of that. Not even when it hurts.
The thing is that most people (caveat: who know how an LLM works) agree they are lying. It's just that only few people seem to care they are lying.
EDIT:
Ah, you're actually saying that:
he is offended by it, where everyone else seems to really need the break after their multi-whole-coin jpegs went to nil.
Seems like footnotes don't render when editing a comment. Or maybe I'm fuzzy on the syntax.
Ah that's it probably. I was in write, and wanted to check whether it renders well by clicking compose. When going back to write, it has this weird habit to add backslashes.
I'm really sorry, it's because compose mode lacks support for footnotes and (also) tables. Compared to other rich text nodes, these require more UI/UX attention and, as such, have been delayed to the next editor enhancement packs. These nodes, at the moment, can only be edited in write (markdown) mode and displayed in compose mode.
The \ backslashes are a way to avoid what-can-be literal Markdown syntax from being recognized by our parser (escaping), the editor adds them automatically when posting in compose mode or switching back to write mode. *This for example should be italic text **and this bold***, but I’m writing this in compose mode.
If you type/edit a [something] in compose, it will add slashes, yes.
(undisclosed colleague)
[^1]: https://en.wikipedia.org/wiki/Muckraker