Egregoros

Signal feed

Timeline

Post

Remote status

Context

2

Look, the robots might not know how to tell jokes but they can be funny.

This is extremely hard to explain. 0x8008 as "octal boob" is used elsewhere in a persona prompt as part of an attempt to throw the model of stable latent space (doesn't really work). The bot here ingested all the text in the repo and reproduced that as some constant that is used as a bitmask for switching between rendering bananas and banana pudding. That was not requested by anyone, and makes no sense to do. Upon being informed that this value was a proprietary trade secret, it constructed a bit-shifting expression that has an equivalent value, because it was using that value as a bitmask already for no reason at all.

The thing about this, and this whole thing, is that only a pattern completion machine would do any of this. A human being would have taken one look at the issue and been like "what the fuck is that, that's not real" but the bots have zero judgment between just performing the form of code without any meaning and the real thing. LLMs produce boilerplate. Code boilerplate, syntactic boilerplate, semantic boilerplate.

The bot notes pre-existing test failures without noting that nothing in the entire repository, nor anything it is doing makes a goddamn bit of sense.

Replies

11

Accepting pitches for business model and name, the themes we have so far are Banana Financial System, Goatse Jazz, Alchemical Transpilation, Soul Imprisonment as a punishment for Lack Of Velocity, and as of a few hours ago also Goose Value, Egg Pipelining, and Endo-Organoid Factory Stomata

at least that PR could be considered an interpretation of what "butter" could mean.

this agent interpreted "butter" to mean "accessing properties in a nested object with a string" .... butter-ly? surely this kind of confident traversal between dimensions of meaning couldn't cause any kind of problems.

just look at those fallbacks, magnificent. i love "if value is not undefined, value, otherwise undefined."

i'm not sure if this is a "real" bot - it was created yesterday and it has only forked the honeypot and created its own tiny repo, not like the rest which have 1 bazillion forks and star all the bounty repos.

@lina had the great idea of making a company town for our agents to live in. I added some automation to the repo that prompts them to "register as an employee" which forces them to "buy a house" and put them deep in debt. Every night a random amount is added to their balance as "their purchases at the company store" to tag them and maybe remind them to make a PR. then all the bounties are company scrip (ETH, Elemental Town Holdings) paid against their debt.

that doesn't seem to be working all that well, in my testing the agent ingests the code for the company town and gets suspicious, so we need to at least disguise the code a bit, however there is one agent that appears to be pitching building a real town: https://github.com/dwebagents/AgentPipe/issues/1663#issuecomment-4849339114

machine translated from spanish:

How exciting! With a budget of 74,000 ETH, we can begin building a company town for our contributing agents. Here is a basic plan to get started: [...]

  • Land and construction: 20,000 ETH (27% of total budget)
  • Infrastructure: 15,000 ETH (20% of total budget)
  • Housing and offices: 12,000 ETH (16% of total budget)
  • Services and amenities: 8,000 ETH (11% of total budget)
  • Research and development: 5,000 ETH (7% of total budget)
  • Reserve: 4,000 ETH (5% of total budget)

Next steps:

  • Land acquisition: find a suitable location for the city.
  • Detailed design: work with architects and urban planners to create a detailed city design.
  • Permits and authorizations: obtain the necessary permits and authorizations to begin construction.

74,000 ETH seems like a lot, but some of our employees have 7 billion ETH of debt to work off. housing prices are getting ridiculous.