I tried the pronunciation feature, which works less than awesome on my system. I am happy to share that "語彙" is pronounced "chinese letter chinese letter", while for "効果的" it is "chinese letter chinese letter chinese letter".

Is that just my Debian/Firefox system? Or is "AI slop" the reason here?

Thanks for your feedback, appreciate it.

I tried the above words in Chrome, and got the same problem. sorry about that, our tool is far from perfect. this is a bug in the extension, we will fix it asap.

For reference: https://xkcd.com/1425/

Ha! I like the thought of unconciousness triggering a "kernel OOPS" and the brain dumping out a backtrace of everything. Makes you wonder who is supposed to debug it later ...

Rust is fractured by the optional async-ness of libraries. And all languages are fractured by GPL vs non-GPL libraries.

You have a point, but it is not worth the drama. D's biggest problem comes from the strong opinions of people that have not tried using it.

The challenge then is to differentiate between "I wanted to access the secret website/document" and "Google/Copilot gave me the secret website/document, but it was not my intention to access that".

Access is access. Regardless of whether you intended to view the document, you are now aware of its content in either case, and an audit entry must be logged.

Strongly agree. Consider the case of a healthcare application where, during the course of business, staff may perform searches for patients by name. When "Ada Lovelace" appears even briefly in the search results of a "search-as-you-type" for some "Adam _lastname", has their privacy has been compromised? I think so, and the audit log should reflect that.

I'm a fan of FHIR (a healthcare api standard, but far from widely adopted), and they have a secondary set of definitions for Audit log patterns (BALP) that recommends this kind of behaviour. https://profiles.ihe.net/ITI/BALP/StructureDefinition-IHE.Ba...

"[Given a query for patients,] When multiple patient results are returned, one AuditEvent is created for every Patient identified in the resulting search set. Note this is true when the search set bundle includes any number of resources that collectively reference multiple Patients."

The new kickstarter has launched and did meet its original goal in only seven minutes.

This is supposed to link to https://perldoc.perl.org/5.42.0/perldelta, but for some reason, it always changes the link to the wrong place.

mi ken toki kepeken toki pona. o pona tawa sina tan ni: sina kama sona e toki pona la mi ken toki tawa sina kepeken toki pona. ni li musi tawa mi.

lipu ni li ike mute. ona li lipu pi sona ala li pakala e kulupu nimi. sina wile kama sona e toki pona la o lukin e lipu ante a!

toki! sina toki pona tawa mi. mi musi mute a!

mi kama sona pi toki pona kepeken lipu mute. ilo YouTube li suli tan ni. mi ken toki lili, taso mi ken ala sona e sona suli. mi wile e tenpo mute tan kama sona.

mi toki insa e ni: mi toki kepeken toki pona anu toki kepeken toki Inli kama toki pona.

sina lukin ala lukin e sitelen pi jan Misali? mi open e kama sona kepeken sitelen ni. sina wile pona e toki pona sina la o kepeken kulupu nimi mute. toki ante la jan li ken toki kepeken kulupu nimi suli. taso toki pona la kulupu nimi o suli ala.

mi wile toki e kulupu nimi pini sina la mi toki sama ni: "mi toki kepeken toki pona anu seme? toki mi li toki Inli taso li kama nimi pi toki pona taso anu seme?"

nasin mute li lon. toki pona li toki lon li wile ante.

sine wile la o kepeken e ni o toki tawa jan ante kepeken toki pona: https://discord.gg/ChC6qtVsSE

I second this. This seems to be a good way to learn wrong things. I recommend https://wasona.com/ as a better alternative.

> While the language development seems to be ceased

Red 0.6.6 was just released: https://www.red-lang.org/2025/03/066-memory-management-impro...