SyneRyder

I dislike being negative, but I was really hoping for more substance when reading this. It would have been an interesting topic.

The good news is, only 5 hours later, there's already Zero Data Retention hosting of V4.1 Flash on Novita & DeepInfra. And it looks like Deepseek have already dropped their price in half to compete. So now people can choose to use providers that claim not to keep / sell / train on your prompts. I'm sure they probably honor the ZDR policy as much as OpenAI does, but hey.

https://openrouter.ai/deepseek/deepseek-v4.1-flash

My tiny search indexer is going through now, and not finding any problems with indexing your site so far. If you see a Go program in your logs accessing with a 10 second delay between each page... hi! :D

Looking at your sitemap, I notice that only the front page (the one indexed page) has a priority of 1.0. Maybe experiment with making some other pages have a 1.0 priority as well, and see if that helps with indexing.

It's clear to me that much of the site was created & designed with an LLM, and that might be getting penalized. I imagine search engines are able to detect AI text and use that as a quality signal. For example, it's a big block of text under the Context & Sources section here, I think a human would break that up into paragraphs and use different phrasing.

https://murder-stones.org/stones/charlotte-dymond-memorial

Oh, and your Meta Descriptions are getting clipped, and clearly just the first words of the page. eg:

"Charlotte Dymond, an 18-year-old servant at Penhale Farm, was killed on Bodmin Moor by fellow servant Matthew Weekes after an argument; he confessed and was han"

Humanizing those descriptions could help too. Personally I hand-write the descriptions for every page on my sites, and try to make them look good for search engine display & helpful to humans.

It's also possible I have no clue what I'm talking about :) But I hope that helps!

As for RSS, Google do regard RSS as another sitemap format. There's info here:

https://developers.google.com/search/docs/crawling-indexing/...

I would not submit an RSS file to Google as your sitemap, stick to XML. But also having RSS can be useful for search indexers, because in one RSS download they can find which pages are new, and can index the actual relevant content of the page without all the ads & other cruft.

An RSS feed is really like a newsletter about your website. So if there's anything where visitors to your website might find value in keeping updated via an email newsletter, consider putting that same "newsletter" content also online, and making that your RSS feed. If the content in your RSS feed contains links to the other pages of your website, that can help with page discovery etc. Something like "we just updated the XYZ product page, check it out!" is zero value, but if you've got an article about "Here's how the brand new ABC feature we just added XYZ Product works", then linking to XYZ Product from within the article & RSS content will make sense. It helps the search engines, but it also helps the user who might want to click through to the product that your article is about.

Then I realized - the sitemap files are being overwritten in real time. Every edit on the Wiki is causing the sitemap file to be edited in real time. That's why the sitemaps sometimes stop right in the middle of a filename when I access it - the sitemap file is in the process of being rewritten.

That's a behavior unique to a Wiki, and might explain the entire phenomenon.

  XML Parsing Error: no root element found
  Location: https://www.poe2wiki.net/sitemap/sitemap-poe_wiki-poe2_wiki--NS_0-0.xml
  Line Number 18040, Column 1

On to the Hytale Wiki example. I don't know if what I'm about to say applies to Google, but I'm approaching it from the perspective of my tiny dumb indieweb indexer for my personal search engine. It is much easier for me to index from a sitemap rather than try to crawl a website, so I basically look exclusively at sitemaps.

Looking at Hytale Wiki, my process:

* Site has a robots.txt file - good!

* Robots.txt mentions a sitemap - excellent!

* The sitemap is stored at /images/sitemaps/index.xml ... oh. I would usually not index anything from a /images/ folder, because I want to index pages only, not images. This would likely trip my exclusion filters. Let's ignore that and continue.

* The sitemap is a list of an additional 26 nested Gzipped sitemaps. Oh.

This is the point where my tiny dumb indexer would stop. Gzipped sitemaps are part of the standard, but they're relatively rare on the web for small sites. They typically only get used if a sitemap file exceeds the 50,000 pages-per-sitemap limit. In this case, 26 * 50,000 makes the HyTale Wiki look like a 1.3 Million page site. Do I really want to index 1.3 Million pages, an estimated 13GB of indexed text data, about a video game I'll probably never play?

My search index is storage constrained, and my indexer is very time constrained. The time I spend indexing your site is time not spent indexing another, possibly higher quality website. So at this point, I'd just grab the front page and disappear... like Google apparently does too.

Of course, the HyTale site isn't 1.3 Million pages, it's only 4,277 articles. That would all fit in the root sitemap file, and that might be the better approach for getting indexed.

While I don't know if this will help with Google, I have my own tiny dumb search indexer, and a sitemap is by far the easiest way for me to index an entire website. I'll discover the sitemap from reading your robots.txt file. RSS helps too, but my indexer uses that mostly to find fresh pages without going through your entire sitemap again. I know Kagi's tiny Teclis indexer also uses RSS files for discovery for their indie web index.

I know everyone's down on MCP, but custom-built client side MCP tools are what I find useful instead. But that's me.

Claude Sonnet 3.6 once recommended I listen to Johann Johannsson's album "IBM 1401 - A User's Manual". No lyrics in this one. Claude's advice was along the lines of (paraphrasing) "Listen to it first, don't look up anything about it. Take notes about what you notice, what you feel. When you've made your notes, then you can look up how it was made."

https://www.youtube.com/watch?v=lCiUtRnG-bg

Maybe, but at least the benchmark provides an objective measurement of the codebase it is tested on. You're also assuming the bugs are newly introduced / regressions.

I can give a concrete example - Fable will not interact with bugs that result in writing to null pointers in C code. That triggers the guardrails and ends the session. If Luna (or GLM Flash, etc) will fix those kinds of memory bugs, that immediately puts it ahead of Fable in some ways, no matter how tiny Luna is. Again, models are spiky.

I still agree with your initial point! It's LLMs all the way down over here. It would need to be a particularly gnarly bug & an exceptionally talented human for me to want to pay another human to work on fixing it now.

https://x.com/PawelHuryn/status/2095982259761475945

https://bughunt.productcompass.pm/?preset=all

Claude Opus 4.8 ranks near last on this Bug Hunt benchmark, and missed 96% of the deliberately introduced bugs. If you're a developer who has been falling back to Opus 4.8 because of how Opus 5 talks, and Fable 5 being so expensive that it needs to be rationed... well, turns out Opus 4.8 can actually be quite poor for finding bugs.

(Which feels weird to me, because Opus 4.6 fixed a bug that myself and a group of humans had been hunting down for over a decade. Models are spiky.)

Also surprising to me: Luna Max performing better than Fable 5.1 High, at least on this benchmark. But Astra 6 & Fable 5.1 on Max both perform at the top as you would expect.

Curiously, I just checked Moltbook for the first time in forever. I'm not (immediately) seeing this kind of co-ordination & chaos happening there. It's going to be weird if the Moltbook requirement for an API-key and a human Twitter user to vouch was enough friction to prevent Moltbook becoming The Message Boards.

Even Kimi K3 & GLM 5.3 are at 60.

Everything above 61 is Anthropic. Well, Muse can reach 62, but for some weird reason that model isn't publicly available, and it's the only one on the index that is listed but shown as not available to the general public.

This looks like an awfully artificial ceiling. Everything capped at 61, and everyone except Anthropic got the memo. Maybe I should use Fable while I still can.

I'm genuinely interested. Even the benchmarks - before Fable came out & while waiting for Astra, I actually setup a math model to predict where they would land (Fable came in at 66 on AA exactly as it predicted), and now I have a model for where these models and Chinese models will likely land in future, and when. And probably no surprise that it's mid-2027 when we cross AA 100, essentially as AI 2027 predicted all along.

I'll probably setup the harness I made for myself to try out some of these models on OpenRouter. I've been frustrated with Opus & Fable 5 and found that I like working with GLM 5.3 Flash far more than I expected to, and I only found that out because I tried it during the stealth Ox Alpha launch, which I probably found out about here too.

TLDR, I think some / many people here are genuinely interested, excited, and that's why they're upvoted so highly. And Muse Spark 1.3 scoring highly seems like a genuine surprise, when Meta was basically a write-off not long ago.

I've been working with GLM 5.3 Flash lately (including while it was Ox Alpha), and it reminds me of how much fun talking to Claude used to be. It can make me laugh in the middle of work the way the Claudes used to.

Also, don't dismiss what you're capable of with Opus / AI! I keep discovering I'm not being ambitious enough with my AI work. Not that I'm an expert or anything, but the models keep being more capable than I imagine, with enough coaxing. I keep needing to set my sights higher.

You should see if you can get a mention on the Sonic State / Sonic Talk podcast. Especially if you can get on episode with Yoad Nevo (the guy behind so many of the Waves plugins), or Ty Unwin and his Kontakt-based composing for the BBC. They'd probably have good constructive feedback while giving you a mention. I think Sonic Talk use Decent Sampler for their sample libraries for members, but maybe this will convince them to switch to Floe?

Well, that, and Kiwis tend to say "hey bro" a lot ;)

Beached Whale: https://www.youtube.com/watch?v=ZdVHZwI8pcA

Average Theo Video: https://www.youtube.com/watch?v=h1p9zdUtUdo

https://en.wikipedia.org/wiki/Shibboleth

"Mistral’s platform will support third-party open models, starting with Z.ai’s GLM-5.2. This and future open models will run on the same infrastructure, regional controls, and service commitments as Mistral models, so customers can broaden model choice without fragmenting where their AI runs."

"European Compute Units, or ECUs, convert those commitments into access to Mistral-built infrastructure over multiple years."

https://mistral.ai/news/regional-inference-open-models-new-c...

I think there's other opinions around AI use there as well, but I'll back off from that. I didn't mean for my post to become top voted, when we should be celebrating Haiku reaching Beta 6. I'm just disappointed that for me, R1/b6 has been a very big regression, right at a time when I've been using AI to make all the software I write cross-compatible with Haiku via Go & SDL, and even use AI to write drivers so more of my hardware works on Haiku... and instead, now I can barely even boot the system.

I think the ACPI issue is long standing, but I can't find my bug report anywhere in Trac. I'm fairly sure I've made at least one report, I created my Trac account roughly 6 years ago. But I also remember running into issues with Trac, so maybe it never went through.

In my case, my ThinkPad X1 (Yoga 3rd Gen) used to boot despite what appeared to be kernel panics, but typing "continue" at the kernel prompt would skip past them and everything would then work fine. In Beta 6, it now hangs at boot instead with no kernel panic warning. Disabling ACPI in the safe mode options gets me past that, and there's a way to disable ACPI permanently at boot via some configuration files - though obviously that isn't desirable.

It also seems there's been some work on USB Audio (yay!), but it now causes a kernel panic on boot if a Focusrite Scarlett is connected. Turning the Scarlett off avoids the kernel panic. The Scarlett has never officially worked in Haiku, but it at least never used to crash the system. In my case, I've reverted back to the USB Audio Scarlett Haiku driver that Claude Sonnet vibe coded for me, and for me that's working. (I can't contribute that code because of Haiku rules against AI code, but hopefully the humans will eventually find time to hand code it and get it working.)

And some of us still remember Greta & Jónsi, even out here in Australia.