Hello, Getting data on gnu.hurd.org is not cumbersome because of the cvs commit (that's not more difficult than a git commit), but because publishing on gnu.hurd.org means endorsing the content, which I haven't taken the time to do in the past few years.
Also, it seems that ./render_locally has some rendering troubles, for instance faq.html reads: Note: the most up-to-date version version of this FAQ is available on [darnassus](http://darnassus.sceen.net/~hurd-web/faq/>) This page <a href="./faq_inlined.html">with all items inlined</a>. # General-discussion FAQs The darnassus URL hasn't been turned into html, and the title hasn't been turned into html either, while the faq_inlined line did get turn into html. Help welcome on this, I'm running ikiwiki 3.20260201-3 Earlier today I took the time to update at least the main pages, notably the faq. Don't hesitate to tell me if some page should really be updated. The really good point about darnassus is getting the hurd wiki hosted by a hurd system. It has been successful for more than a decade, but nowadays with all the bots it's more difficult :/ Ideally things like iocaine could be used, but as usual with all the recent tools, they depend on dozens of libraries which have the tendency of depending on only very standard setups (x86_64 linux). Iocaine does build after some fixups, but it fails to start on i386-hurd: thread 'main' (1) panicked at /home/buildd/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/roto-0.9.0/src/codegen/mod.rs:298:44: called `Result::unwrap()` on an `Err` value: "unsupported architecture" apparently because cranelift, used by roto, doesn't support i386, only x86_64. Perhaps there is some way to tell roto or cranelift to use a more generic backend rather than an arch-specific backend, their readmes don't say. Samuel [email protected], le lun. 09 mars 2026 01:01:25 +0000, a ecrit: > Hey Hurd friends! > > I'd like to get some consensus for how we might fix https://gnu.hurd.org > being fairly out of date. First let me describe the status quo. > gnu.hurd.org is hosted by the FSF. It is out of date, because to update > hurd.gnu.org one must follow the cumbersome directions that I believe are > found on this page (1). Samuel has been the main person that has done this > for years. Thanks Samuel! He mainly focuses on updating the qoths now. > > The more up to date wiki is located at https://darnassus.sceen.net/~hurd-web/ > . > It is a Hurd powered website, and when the AI bots do not attack it, it can > be quite fast. One can easily edit the wiki on both hurd.gnu.org or at > darnassus via pressing the "Edit" button, or one can email git patches to > [email protected]. > > Now that I've described the status quo, let me describe some possible > solutions. > We could have someone volunteer to update hurd.gnu.org via the CVS method, but > this will always be a manual process. We could have many wiki mirror websites > like: https://hurdos.com/wiki (it's my site, but searching does not work) or > https://hurd.ion.nu/index.html (searching does work, but not the edit button). > > The person behind hurd.ion.nu, (Alicia on irc) has offered that site to be the > main Hurd wiki. Do this person want us to re-direct hurd.gnu.org to > hurd.ion.nu > ? The cost of hosting hurd.gnu.org could be quite expensive. I swore that I > once > saw a video, where the leader of the OpenBSD project mentioned that it costs > him > $500 a month to host OpenBSD.org ... The AI bots really do hammer websites a > ton. Here's my favorite blog post that explains how hard it is to fight the AI > bots (3). > > > Thoughts, > > Joshua Branson > gnucode.org > 143 > > > 1. https://savannah.gnu.org/maintenance/HomepageUpload/ > 2. > https://drewdevault.com/2025/03/17/2025-03-17-Stop-externalizing-your-costs-on-me.html > 3. > https://drewdevault.com/2025/03/17/2025-03-17-Stop-externalizing-your-costs-on-me.html
