• 0 Posts
  • 102 Comments
Joined 1 year ago
cake
Cake day: July 29th, 2023

help-circle





  • If it were merely a search engine, it risks not being ai enough. We already have search engines, and no one is gonna invest in that old garbage. So instead, it finds something that you might want that’s been predigested for ease of ai consumption (Retrieval), dumps it into the context window alongside your original question (Augmentation) and then bullshits about it (Generation).

    Think of it as exactly the same stuff that the LLM folk have already tried to sell you, trying to work around limitations of training and data availability by providing “cut and paste as a service” to generate ever more complex prompts for you, in the hopes that this time you’ll pay more for it than it costs to run.



  • Interesting article about netflix. I hadn’t really thought about the scale of their shitty forgettable movie generation, but there are apparently hundreds and hundreds of these things with big names attached and no-one watches them and no-one has heard of them and apparently Netflix doesn’t care about this because they can pitch magic numbers to their shareholders and everyone is happy.

    “What are these movies?” the Hollywood producer asked me. “Are they successful movies? Are they not? They have famous people in them. They get put out by major studios. And yet because we don’t have any reliable numbers from the streamers, we actually don’t know how many people have watched them. So what are they? If no one knows about them, if no one saw them, are they just something that people who are in them can talk about in meetings to get other jobs? Are we all just trying to keep the ball rolling so we’re just getting paid and having jobs, but no one’s really watching any of this stuff? When does the bubble burst? No one has any fucking clue.”

    What a colossal waste of money, brains, time and talent. I can see who the market for stuff like sora is, now.

    https://www.nplusonemag.com/issue-49/essays/casual-viewing/






  • I will find someone who I consider better than me in relevant ways,

    Lemme guess, rich, white, asshole? (now I write this, I realise it could be about the author of the blog post too, and not just the bull he’s seeking).

    These people continue to be so utterly delusional about the nature of success. The desperate need to believe that genetics is destiny, and that the ultra-wealthy got that way because they are also ultra-competent instead of merely being ultra-lucky and/or ultra-rapacious.

    I guess the future is a race to see what comes first… the ultra-wealthy habsburging themselves into oblivion, the oceans boiling, or a resurgence in the construction of hand-built artisanal tumbrels.





  • I’m aware he isn’t there now, but it bears remembering that he was there at the beginning when these goals were being shaped, and as we have seen with twitter there’s nothing to stop him coming back, even if nostr is his new best friend for now.

    I read that posts on BlueSky are permanently stored in a blockchain,

    So, this is complex and hard to find concrete information on, but:

    1. Bluesky use a merkle tree based things. Don’t call em blockchain… that’s the sort of thing cryptocurrency boosters want so as to present their technologies are useful.
    2. Posts are stored in a merkle search tree, but attachments are stored separately. Attached blobs (like images) can be (and are) deleted independently of the tree nodes which reference them.
    3. The merkle trees are independent and can be modified without having to rewrite the whole history of every post on bluesky, because there isn’t one central official ledger of all posts.

    From bluesky’s own (non technical) blurb on the subject,

    it takes a bit longer for the text content of a post to be fully deleted in storage. The text content is stored in a non-readable form, but it is possible to query the data via the API. We will periodically perform back-end deletes to entirely wipe this data.

    The merkle trees are per-user, which makes history-modifying operations like rebasing practical… this facility apparently landed last summer, eg. Intention to remove repository history. Flagging tree nodes as deleted, and then actually destroying them in a series of later operations (rebase, then garbage collection) would explain the front end respecting deletions but lower-level protocols showing older state for a little while.




  • It’s a long read, but a good one (though not a nice one).

    • learn about how all the people who actually make decisions in c++ world are complete assholes!
    • liking go (the programming language) correlated with brain damage!
    • in c++ world, it is ok to throw an arbitrary number of highly competent non-bros out of the window in order to keep a bro on board, even if said bro drugged and raped a minor!
    • the c++ module system is like a gunshot wound to the ass!
    • c++ leadership is delusional about memory safety!
    • even more assholes!

    Someone on mastodon (can’t remember who right now) joked that they were expecting the c++ committee to publicly support trump, in the hopes he would retract the usg memory safety requirements. I can now believe that they might have considered that, and are probably hoping he’ll come down in their favour now that he’s coming in.