graypegg

I’ll never understand this desire from certain OSRS folk.

You can put hundreds of hours into these accounts, and people will roll the dice on a vibecoded plugin they (or a stranger on the runelite plugin repo) make with very little understanding that Jagex (the company that maintains OSRS) just sees client commands. If you look like a bot and smell like a bot, you get treated like a bot.

I now know two friends that got bans (one permanent!) for rolling their own unpublished plugins, not realizing that they asked Mod Claude for a macro set for some bossing content… oof.

I have an original homepod, and man, I wish I could lobotomize it easily.

It's a really nice speaker if I set it on something sturdy that won't rattle, and airplay is still pretty good even on ancient devices.

I can't keep it plugged in because it will just randomly say "You can enable personalized responses in the settings app!" at 3am about once a week if I do. It's horrifying when it happens because it always seems to be 10x louder than I remember it being set to.

You already know why that’s a confusing argument because you included the time scale yourself, but to say the obvious: I think we probably need to go a bit faster than “millions of years”.

    What if [positive noun] instead of [negative noun]? Have you ever thought about that? [Nefarious proper noun] tries to feed us [negative noun] but using [url] we're going to change the [collective noun]! [Collective noun in which the reader self-includes] has always been at the forefront of [positive adjective] innovation, and that has inspired me [artisanal synonym for "to make"] with love for you all.

I'm there, I feel it, it's 2011 and I'm being pitched facebook for dog walkers or twitter for the uzbec equestrian community unironically except this is taking the bold step of making the niche "all of humanity".

You really need more than "new time bad... remember old time?" to pitch a general-purpose social media product that avoids the obvious, well-documented foibles of social media.

Nahhhh you don't need a new term. It's just like... on the fringes of what the term means.

I'd call it an "ASCII-Art inspired shader", but some % of people would look at it and immediately call it "ASCII Art" with no confusion. Some other % of people are also going to scoff at me saying it's "ASCII-Art inspired" at all.

Should mention, I have no issue with this little project! I'm just agreeing with the parent comment that this is just hinting at the limitations of ASCII art without actually working with them, in our opinion. Thinking about art being an important step in appreciating art, and all of that.

Ayyy that's a much more articulate way to put what I was also thinking.

"Being constructed of text characters" is a very loose definition of ASCII art. Not to say it's not visually interesting, but just that it's on the far ends of the histogram of what people think of when they hear "ASCII art".

Personally, I think the fact this is relying on colour for contrast makes this feel more like a shader that quantizes the input into little dots that just happen to be 1 of 3 characters, than ASCII Art. It's a vague border between that and an ASCII shader, and then ASCII art, but there's definitely some measureable distance between those peaks.

It’s a cool name! Don’t let Stripe make you doubt that haha

People keep trying to systematize things for the tools they keep saying don't need systemization. No idea why you can't just put the documentation programming language context in the URL. "/docs/typescript/...", "/docs/python/..." etc.

I don't think the agents are struggling with the idea that different URLs have different responses, and that checking the sitemap is a good idea.

Tangential: A rare en–dash user out in the wild!

> Recently, a Vercel engineer called on harnesses to send the programming language the client prefers, so documentation sites can serve more specific examples. For example, adding Python could prioritize docs for the Python SDK instead of sending something generic.

I know this is pedantic, but IMO that should just be in the URL if the resource is going to be totally different. Accept-Language is already a bit weird for the same reason in my mind, but I think the intention behind it is the resource itself is attempting to communicate the exact same resource. Obviously, two different languages from two different cultures are going to have different interpretations of the same direct translation, but the intention is the service has at least tried to avoid that as much as possible.

Adding programming language into that same concept just makes it seems like you're serving both /docs/typescript/vx/... and /docs/python/vx/... from /docs/vx/... despite them (in theory) having many more differences in between implementations/context than that would imply.

Agents should read sitemaps. Does anyone's harness do specifically that when looking up documentation?