If you want a bunch of random noise and chaos in your life, there's a silly thing I put together, called FX Radio.

It's a box running Liquidsoap that mixes several audio players going through a huge library of sound effects, production libraries, and other odd things.

Don't expect anything to make sense. If it does, it's purely coincidental.

stream.borris.me:8888/fx

This is running on the same machine that hosts @NoiseBox, which throws a random sound at the fediverse once an hour, at a random minute each hour.

Fun fact:
This is running on a shelf under my mom's desk. While she knows the box is there, she doesn't know what it does. So, it's fun just for that reason.

Onj šŸŽ¶ reshared this.

@Bri New silly bug! Send a new post. In the invisible interface, navigate to that new post. Before anything else comes in, delete that post. Now you're apparently still on that post in the buffer even though it doesn't exist! What's more, you can keep hitting next post, next post, next post, in the invisible interface, and it's entirely silent. Your position in the buffer keeps going up and up and up, E.G. Home. 171 of 162. To recover, hit previous post enough to get back to the real last post, then if you hit next post, it correctly recognizes that you're at the end and prevents you from going off into never-never land again.

> Elasticsearch was never a database. It was built as a search engine API over Apache Lucene (an incredibly powerful full-text search library), but not as a system of record. Even Elastic’s own guidance has long suggested that your source of truth should live somewhere else, with Elasticsearch serving as a secondary index. Yet, over the last decade, many teams have tried to stretch the search engine into being their primary database, usually with unexpected results.

We demanded to keep our normal logs but you know how corporate IT is ...

Long post on the durability of US racism

Sensitive content

in reply to Tim Bray

What would happen if ICE wanted to join the Fediverse? Most instances probably wouldn’t host that account, but some would. The account would be broadly blocked at both individual and instance levels, and some instances would probably defederate the hosting instance. Some folks would migrate between instances based on these choices. All this, I think, would be a good outcome?
This entry was edited (4 hours ago)

Yo, Bulgarian is not an easy language, yet here we are coding it in. Whoever can help tune it, well, it may need some. Good news with it is that it's largely a "what you hear is what you get" kind of language, and with 30 letters, well, seen worse. Bad news? Cyrillic support is hard to code out for the IPA normalizer. Good news? We need Cyrillic support anyway before turning the normalizer into a frontend DLL, which is the next milestone of this project.
Why not keep the frontend normalizer in Python you ask? This good for now, but to ship recompilable and buildable DLLs, it's clear that we'll have to do this, not to mention when NVDA goes 64-bit, although for the latter the issue is more embedding Espeak than the frontend need itself
This entry was edited (53 minutes ago)

NV Speech Player (github.com/tgeczy/NVSpeechPlay…): Updated readme with section that describes how phoneme data is added or changed, as asked by some. Feel free to pull the repo, modify data.py and open a PR, or drop me an updated set of lines if you'd like, and they will get tuned accordingly.
⇧