graypegg
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.
The main difference is going to be scale and the chaos that brings. You see a LOT of streetcars in Toronto. For a huge chunk of downtown, it's the main subway-ish transit option. Some of the lines are on a 5min frequency, others are every ~10min or so, with some segments having 2-3 lines on it. I've seen them get backed up before an intersection, and open doors for passengers before they even reach the stop haha. I've personally hood-surfed over cars that got into the lane between the streetcar and the stop quite a few times, and sometimes it really isn't their fault.
The signal on the rear-end [1] is awful. There's a blurb saying "DO NOT PASS OPEN DOORS" which is clear enough, but there's also a sign that illuminates when the doors are open and it's NOT a stop sign. It's this do-not slashed circle with a picture of a stick figure seemingly walking into traffic. I think there's a reading of that symbol from well-meaning tourists that says "Attention boarding passengers, don't run into traffic". I could see that freaking out a waymo without a little bit of custom code.
[0] (All red lines are streetcars) https://cdn.ttc.ca/-/media/Project/TTC/DevProto/Images/Home/...
[1] https://blogto-production2-baselayer-display.blogto.com/arti...
But also... I know I have the minority opinion on this. It absolutely should be opt-in, not opt-out. I think the past decade, I've been told the font tweaks I enable are incomprehensable to everyone I work with. The way I like my IDE fonts is far outside the bell curve (ligatures, cursive variants for some syntax, proportional variants for prose) so the fact that most new monospace code-focused fonts seem to align with my opinions should be concerning to font makers! I like that I don't have to patch a different font's italics into my code font anymore, but common sense says I SHOULD still have to do that!
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.
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.
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.
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.
"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.
Though I think you're right that it's alphabetical by English name: Arabic, Chinese, French, Russian, Spanish
Archive link for context in the future: https://archive.is/g6Znd
But seriously, just publishing OAS docs at a /.well-known URI seems very sensible. https://www.rfc-editor.org/rfc/rfc9727.html
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!
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?
https://f.toi.sh/fr-ca-mbp.jpg (Pardon the dust!! You never really look too closely as your keyboard until you have to take a picture of it eh?)
Tab, capslock, shift, backspace, and return are all symbols-only. I feel like I have a pretty good ambient understanding of what they mean at a glance so I think I've always seen them on fr-CA layouts I've used.
Was trying to communicate to a designer in Ontario a while ago that we could use the backspace symbol for a correction key in a PIN entry view. We were working on an iOS application so I was immediately thinking that the apple default UI font would have exactly that "chevron with a cross" symbol styled how it looks on the keyboard somewhere in it. Designer was pretty confused about it though, so I think it's probably just fr-CA keyboards.
But I'm fine with the beer festival phoning it in. I guess my only issue with the in-the-wild poster example you found is it does look... bland and just aestetically bad. Your example AI poster styles would be a huge improvement! I can't say they're like, impressive in anyway or winning any awards since they're also bland, but aestetically they hold up and IMO, actually communicate the info better than the ez-slop original.
Maybe to put it another way: if it was 2015, and an craft festival and a beer festival both used the same incredibly lame looking Word template for posters, I'd have the exact same opinion.
It's derivatives all the way down
> I want to address the recent conversation surrounding our fall menu boards.
> The design was created using gen AI. I want to be transparent about that. At the time, I genuinely did not understand the extent of the concerns surrounding AI-generated artwork, particularly the impact it can have on artists and the environmental concerns associated with it.
> My intention was never to disrespect artists, take credit for someone else’s work, or diminish the value of human creativity. I was simply trying to put together our fall menu during an especially busy and demanding time for me and our small team.
> That said, I have listened to the feedback. I understand why people have strong feelings about it, and I respect those concerns. Going forward, I have decided that Penny’s Coffee Shop will not be using AI for our menu artwork and promotional designs.
> What has been difficult for me, however, is the amount of negativity, personal attacks, and messages that followed this situation. There is a real person behind this small business. I am doing my best to run a local coffee shop, support my team, serve our community, and navigate being a new mom at the same time.
> I am always willing to listen, learn, and do better. I just hope we can have those conversations with kindness and respect.
> To everyone who continues to support Penny’s, especially through a challenging time for our business, thank you. Your support means more than you know.
- I'm sorry
- I know my use of gen AI made it seem like I dislike artists
- That's not a belief of mine
- I'll prove that by not using gen AI at my cafe for this sort of thing ever again
- Please be kind to me, this is a small business and I'm very stressed out
Talking to business insider was exactly the wrong thing to do after that. Your sign looks bad. You've made the awful mistake of telling more people about your bad sign with the intent of making them feel sympathetic. Even if they feel sympathetic, people still look at the bad sign you made in desperation along with the framing from BI and think... "oh so maybe she shouldn't be running a cafe then. This seems like she's barely getting by at this point".
On the flip side, telling someone "pay my artist friend or else I'll go out of my way to tell people primed to hate you based on a single detail, about only that 1 single detail" is actual old-school extortion.
Everyone in this story is tiring and annoying.
I agree, but maybe just not on the Netscape 1.x part. Brutalism in all of it's forms has never been about traditionalism. Even if concrete wasn't a new matieral in the 50s, you can't say something like Église Notre-Dame du Haut [0] is following any sort of traditional church architecture.
Brutalism on the web to me would focus more on honesty. An honest website shows you the processes your browser is undertaking, and how that results in rendering it's purpose. Images should load in progressively, any layout tables/divs/scaffolding shouldn't be invisible, a link/button/headings should behave/look how they "natively" do in whatever browser you happen to be using (not specifically netscape 1.x). If you're writing a cookie to the current session, I want to see that state reflected on the page. If I see a process happening I don't like, I should be able to stop it.
That doesn't have to look old or be unstyled. But there's certainly a way that letting hypertext just sort of "exist" makes a website more honest. All things considered right now, I'd say honesty is a pretty non-traditional adjective for the web haha.
Tangential, but I love the design of your blog. That's so freakishly accurate to old GNOME 2 Ubuntu, amazing work.
If you're talking about parsing HTML with regex... buddy that IS the pinnacle of software quality. I'm sure... nay convinced, that HTML is fully parseable with regular expressions. We were just waiting for one very special boy to ask Claude for it, and today, the world hath received the fruits from a tree we planted long ago... thank you.
We do get the the pinnicle of software quality though: parsing HTML with regex. https://github.com/leiDnedyA/hn-without-ai/blob/007e7b4a6df6...
Like, it's really no big deal I guess. You were always going to find out this info from sources compiled by other people. But at least don't do the "I'll change some words and call it mine" high school essay plagiarism technique. There was clearly real research done here as well, it's not like it would've been that much harder to write it yourself.
Edit: LLM's used as a context-aware thesaurus called out here... https://vale.rocks/posts/ai-usage#:~:text=Apart%20from%20tho...
source:
> X (formerly Twitter) now falls back to Open Graph tags when twitter:* tags are absent, making the dedicated Twitter Card markup redundant for most use cases.
article:
> X falls back to the widely respected Open Graph meta tags, making the Twitter-specific declarations largely useless.
source:
> The Twitter Card Validator was retired and the original Twitter Developers documentation is no longer accessible.
article:
> However, the documentation and card validator are no longer accessible (previously at https://dev.twitter.com/cards/getting-started and https://cards-dev.twitter.com/validator respectively).
source:
> Twitter's Do Not Track support was effectively dropped following the platform's transition to X. The original Twitter privacy options documentation is no longer accessible, and the signal is not honored in practice.
article:
> Twitter also had a Do Not Track meta tag for opting out of tracking when using Twitter for Websites widgets. Again, the documentation (previously at https://dev.twitter.com/web/overview/privacy) is now inaccessible, and it seems the tag is no longer respected.
source:
> XML-RPC pingbacks have been widely disabled by default due to their use in DDoS amplification attacks. Use Webmention instead.
article:
> They functioned somewhat similarly to how WebMentions do. Unfortunately, pingbacks rather quickly became an avenue for spam and SEO-gaming, so fell out of fashion. Vulnerabilities allowing sites to be tied up in DDoS attacks also became widely exploited.People always miss out the fact that older information-dense UIs were... information dense. We get this weird simulacrum of information density where the LLM has slapped on "every pod has a machine", a made-up PDU for pods with a watt rating somehow, and random status labels EVERYWHERE. All it's missing is the green circle "LIVE" label that every claude app seems to have...
Saying that, probably annoying to work with transformed DOM nodes, but the background being the only thing moving in the "bounce" example just stood out to me as weird.
And yeah, Asus DOES need to sell windows laptops because the market demands it, but it doesn't mean they need to follow all of Microsoft's rules/goals. ("Pleeeeease put an NPU in every laptop and advertise copilot for us, pleeeease") Giving them a steep discount gives Microsoft a lever to pull if they feel like punishing an OEM later, though with the goal of avoiding anything that halts the sale of PCs with windows on it, which is bad for all parties.
You can't really model that on a supply/demand curve. Microsoft supplies Windows licenses, but Asus supplies a big chunk of market access. A license to software is an infinitely available resource which only has a value determined by the market's willingness to pay for it; a market that microsoft has historically been dogshit at accessing themselves. (Surface product line, for example)
const incidents = e.detail.incidents;
// ...snip...
const now = new Date();
const threeMonthsAgo = new Date(now);
threeMonthsAgo.setMonth(threeMonthsAgo.getMonth() - 3);
// ...snip...
var currentFreq = recentIncidents.length / 3; // <- We out here, smoking these guns with our homeboy Claude
// ...snip...
var earliest = null;
for (var j = 0; j < incidents.length; j++) {
var dd = new Date(incidents[j].started_at); // <- eventually incidents[j].started_at is "2016-03-01T07:07:37.000Z"
if (!earliest || dd < earliest) earliest = dd;
}
// ...snip...
document.getElementById('n-since').textContent = earliest
? earliest.toLocaleDateString('en-US', { month: 'long', year: 'numeric' })
: '?';
document.getElementById('n-rate').textContent = Math.round(currentFreq * 10) / 10;
#n-rate has nothing to do with the #n-since month, it's just the last trailing 3 months. And even then, it's sort of underbaked? It's moving the date back by 3 calendar months not taking into account differing numbers of days, so it'll under-report short months.
I wouldn't trust the stats here.
Edit: whoops, author updated the template while I was writing this! It now says "Over the last 3 months", though that's still calendar months.