"#RoedeanSchool, a top #Johannesburg private girls’ school, is facing allegations of #antisemitism after its first-team #tennis side refused to play scheduled tennis matches against players from #KingDavidLinksfield (#KDL) because they were #Jewish.

The incident has sparked outrage, forced high-level inter-#school engagements, and raised alarming questions about alleged #discrimination taking place at the school. It has also ignited antisemitism online.

The SA Jewish Report has in its possession a verified recording of a conversation that took place between King David Principal #LorraineSrage and a member of #Roedean’s staff, in which the latter explains that the school is under pressure from its parent body not to play KDL.

She told #Srage, “We are facing a bit of pressure from our community and our constituents regarding not playing against #KingDavid. So It’s almost like what’s happening out in society is now affecting us at school level.”.

https://www.sajr.co.za/sinister-game-roedean-ducks-antisemitism-allegation-in-tennis-row/

Ведь достаточно задействовать стандартизированный формат сериализации/конфигурации с МАССИВАМИ, больше ничего менять не нужно. Та же схема: если строка равна `%` — подставить вместо неё строку с путём к файлу, для внезапно необходимых строк из одних лишь `%` предусмотреть возможность экранирования «каждые `%%` превращаются в `%`». Но при этом за счёт продуманного стандартизированного формата у нас есть возможность явно разделять аргументы, передавая их в виде массива строк (тот же niri с его #kdl).

Ну и ладно, я могу и сам пошерстить. Только я не буду держать всё в голове либо в неструктурированных заметках, как делал это раньше, я буду собирать структурированные данные! В таблички я не умею и учиться не хочу (много кнопок, фу), поэтому буду использовать #kdl и тыкать #nushell.

maybe I'll do some KDL stuff today. As a treat.

#KDL

🌘 設定檔的本質：抽象化而非語法
➤ 告別語法之爭，擁抱抽象化來解決設定檔的根本問題
✤ https://ruudvanasseldonk.com/2025/abstraction-not-syntax
文章探討目前對 YAML 等設定檔格式感到厭倦的現象，並指出許多新興格式僅在語法層面進行優化，而忽略了更根本的問題。作者認為，真正的關鍵在於抽象化能力，而非僅僅簡化語法。透過使用像 RCL 這樣的工具，可以利用迴圈和變數等程式碼概念來消除重複，減少錯誤，並提高可維護性，儘管這也會帶來額外的處理步驟和可搜尋性下降的挑戰。最終，對於複雜的設定，引入程式碼般的抽象化是必要的，以平衡程式碼與資料之間的關係。
+ 說得太對了！一直覺得 YAML 雖然看起來不錯，但重複性太高，很容易出錯。RCL 的例子確實展示了抽象化的威力。
+ 雖然我明白抽象化的好處，但導入新的工具鏈和處理步驟還是讓人有點猶豫。如何在可讀性和功能性之間找到平衡點，是個值得思考的問題。
#軟體開發 #設定檔 #抽象化 #YAML #TOML #KDL #RCL

Initial custom themes support has landed in @conjured.ink's stall software and it's very fast, and very easy to write custom themes for (assuming you know a little bit of HTML/CSS!)

Highlights:

• VERY fast jinja-style templates w/ layouts & partials
• KDL-based metadata ;)
• No framework needed!
• Easy packaging

Our shops are more than just ecommerce: they're going to be able to do newsletters/blogging, POSSE, and general custom websites, all with an EXTREMELY small footprint that will be cheap or free!

Like this whole thing? Please support us if can comfortably do so: https://mastodon.social/@conjured_ink/115347161647458655

#KDL #POSSE #IndieWeb #Rust #RustLang #StopPayPros #BoostsWelcome

Big Brain, btw, is designed to be data-oriented, so I might provide an API that lets you define game AI in .kdl files that look like this. It could also, for example, eventually use a hypothetical node editor (thing Blender Geometry Nodes), to define the same data.

#KDL #Bevy #BigBrain #GameAI

Hold up can we talk about how cute this little file tree icon for KDL files in Zed is?!

#KDL #ZedEditor #Zed

Wrote a tokenizer for #kdl in #zig, going to make it a full parser soon™

@samir obligatory #KDL spam: https://kdl.dev

Excited for the @bevy scene format. I poked at it a bit and it's definitely something that would look really darn good in #KDL. This is using the proposed number type suffix syntax.

Once the format lands, I might write an adapter that lets you write scenes in KDL and hot reload w/o recompile!

ok hear me out

what if

#KDL args/prop vals could be nodes, too? This seems... tremendously silly, but I can imagine use cases even if I can't imagine how to make it look reasonable.

language design challenge: If you were to support unquoted paths in a language like #KDL, how would you do it in a way that didn't have massive footguns?

See https://github.com/kdl-org/kdl/discussions/494 and send us your answer there! Maybe there's still a way :)

#KDL v2 is such a delight to use omfg

I just really really really wish we had found a good way to allow / in bare idents. One of those sins of the past thing where we would’ve had to completely change the comment syntax to support it :(

Probably my only regret about the language right now tbh.

L'association Le Klan du Loup vous souhaite une très belle fête de Lugnasad 🌾🌾🌻🌻🐾

#KDL

so this is happening.

All my #Rust #RustLang repos are moved over. Now I just need to figure out CI, republish to crates.io, and archive the github side (and document a tombstone in their readmes).

I have a bunch of other repos I'll either archive or delete as well.

#KDL and #orogene will remain github-side for now because they're a bit more dependent on github services, but I would like to at least move orogene over eventually. KDL might be stuck, though, unfortunately, but I might move only kdl-rs.

#bevy #miette

semi-cursed idea: a #KDL representation of _every #XMPP stanza_, mostly for denser raw storage.

Most clients decide very-lossy data storage is good enough, but that doesn't satisfy me. The current storage mechanism for Spades is based on the XML stanzas (in MAM form) and the size of the XML in bytes represented as an ASCII number, wrapped in ASCII record/field separator characters. (Actually, the XML might be gzipped, I can't remember.) To condense it further, I could try to write a dense KDL representation and convert at store and read time. I could also try Brotli instead of gzip or xz.

I'm also thinking I'll want to split the history into multiple files (possibly by file size), and figure out how I'm going to page through that. Also it's all stored unencrypted at rest right now. (I think when I tried to do E2EE last, I had to have it save the unencrypted version because I had no direct access to the original encryption module to re-decrypt it; it's more or less embedded in the SDK and decrypted before I get it.)

#kdl file formatter! Check it out:

https://github.com/hougesen/kdlfmt

secretly genius #xmpp idea: #KDL representation of Data Forms.

So this beast:

      Bot Configuration
      Fill out this form to configure your new bot!
      
        jabber:bot
      
      Section 1: Bot Info
      
      
      
        
      
      
      Section 2: Features
      
        contests
        news
        polls
        reminders
        search
        news
        search
      
      Section 3: Subscriber List
      
        20
        10
        20
        30
        50
        100
        none
      
      Section 4: Invitations
      
        Tell all your friends about your new bot!
      
    

(form)meta {
  title "Bot Configuration"
  instructions "Fill out this form to configure your new bot."
}
(hidden)FORM_TYPE jabber:bot

(fixed)"" "Section 1: Bot Info"
(text-single)botname label="The name of your bot"
(text-multi)description label="Helpful description of your bot"
(boolean)public label="Public bot?" required=#true
(text-private)password label="Password for special access"

(fixed)"" "Section 2: Features"
(list-multi)features label="What features will the bot support?" {
  (option)contests label="Contests"
  (option)news label="News"
  (option)polls label="Polls"
  (option)reminders label="Reminders"
  (option)search label="Search"
  news
  search
}

(fixed)"" "Section 3: Subscriber List"
(list-single)maxsubs label="Maximum number of subscribers" {
  20
  (option)10
  (option)20
  (option)30
  (option)50
  (option)100
  (option)none label=None
}

(fixed)"" "Section 4: Invitations"
(jid-multi)invitelist label="People to invite" desc="Tell all your friends about your new bot!"

Still looking for some help from an extra set of eyeballs or such for some #KDL consistency checking

From: @zkat
https://toot.cat/@zkat/114359709628259341