Does anyone know of an Android app to install an additional 3rd party TTS engine that can then be configured to point to a custom Open-AI/Fast-API endpoint for self hosting higher quality voices that are not easily run/fit on mobile hardware?

Ah, that's a shame. Thanks for the context though.

I did feel a little bit of that slight dismissal or elitism from the thread I linked above about the graphical installer ISO. Although I think the relative surge of new users after graphical ISO's implementation did end up changing some minds on the merit of its continual development.

It seems like some tools just never fully realize their potential market demand until they're finally implemented and consequently adopted. Quite the catch 22.

I also wonder if it's a bit of a motivational aspect for individual contributors, as in demand with mostly originate from novice users who've yet to master the Nix language, yet by the time one's gained enough experience to contribute to Snowflake OS, you've kind of grown out of outgrow the need for it. That kind of reflects my personal interests around graphical programming, as I became more familiar with various languages, my inkling for a graphical representation of control flow gradually waned.

Still, I think lowering the barrier to adoption is in the long run best serves the community and in sustaining new contributors. Sort of like the conventional Greek proverb:

A society grows great when old men plant trees whose shade they know they shall never sit in.

Nix can create attribute sets from JSON, so there isn't a need to generate nix code.

Is there a good way of mixing and mashing JSON attribute sets with conventional nix config files? Perhaps relegating some config to machine-generated JSON, and some hand crafted configs?

Indeed, I was unaware of this project. Project commit history looks inactive, but I'm guessing its feature-complete? Looks like someone has rewriten it with an added TUI:

• https://github.com/Lassulus/nix-autobahn/issues/7
• https://github.com/wucke13/nix-autobahn

How does distrobox implement display forwarding? Does it support Wayland, or is it using bind mounts for xauth and X11 unix sockets?

With approach does it use for hardware acceleration? Does it abstract over Open Container Initiative's plugin system, e.g. Nvidia container tool kit or AMD's equivalent?

Is it inconvenient if any of your applications use shared memory, like many middleware transports used for robotics or machine learning software development?

I'm more familiar with plain docker and dev containers, but am interested in learning more about distrobox (and toolbox?) as another escape hatch while working with NixOS.

Tagging an image is simply associating a string value to an image pushed to a container registry, as a human readable identifier. Unlike an image ID or image digest sha, an image tag is only loosely associated, and can be remapped later to another image in the same registry repo, e.g latest. Untagging is simply removing the tag from the registry, but not necessarily the associated image itself.

I'm using a recent 42" LG OLED TV as a large affordable PC monitor in order to support 4K@120Hz+HDR@10bit, which is great for gaming or content creation that can appreciate the screen real estate. Anything in the proper PC Monitor market similarly sized or even slightly smaller costs way more per screen area and feature parity.

Unfortunately such TVs rarely include anything other than HDMI for digital video input, regardless of the growing trend connecting gaming PCs in the living room, like with fiber optic HDMI cables. I actually went with a GPU with more than one HDMI output so I could display to both TVs in the house simultaneously.

Also, having an API as well as a remote to control my monitor is kind of nice. Enough folks are using LG TVs as monitors for this midsize range that there even open source projects to entirely mimic conventional display behaviors:

• https://github.com/JPersson77/LGTVCompanion
• https://github.com/cali-95/LGTVLinuxCompanion

I also kind of like using the TV as simple KVMs with less cables. For example with audio, I can independently control volume and mux output to either speakers or multiple Bluetooth devices from the TV, without having fiddle around with repairing Bluetooth peripherals to each PC or gaming console. That's particularly nice when swapping from playing games on the PC to watching movies on a Chromecast with a friend over two pairs of headphones, while still keeping the house quite for the family. That kind of KVM functionality and connectivity is still kind of a premium feature for modest priced PC monitors. Of course others find their own use cases for hacking the TV remote APIs:

• https://youtu.be/io_AFseYleE
• https://youtu.be/76wAEJOdBq8

Didn't know about this case history with Nintendo, nor the name for the common exploit used:

• Game Genie
  • https://en.wikipedia.org/wiki/Game_Genie
• Fusée Gelée exploit
  • https://switch.homebrew.guide/gettingstarted/choosinganexploit.html#fusee-gelee
  • https://medium.com/@SoyLatteChen/inside-fus%C3%A9e-gel%C3%A9e-the-unpatchable-entrypoint-for-nintendo-switch-hacking-26f42026ada0

How did you delimit the leaf pattern so evenly around the circumference of the brim of the bowl? Did you use a rotary indexer and a wood burning jig?

Thanks so much for your hard work and the terrific beta release!
Here's to the success of Lemmy, Sync for Lemmy, and the rest of the Fediverse,
Cheers! 🍻

Personally, I think that a sufficiently large instance does represent a major risk. But now I think it’s a risk we have to take.

If we had to white board a decision matrix on Facebook federation, what would be the number of risk's and rewards for either approach? How would you weight or quantify them? Just trying to approach this from a little more of an analytical angle, given most of us are developers anyway.

Looks like the author of the last article above posted a follow up yesterday:

• https://ploum.net/2023-07-06-stop-trying-to-make-social-networks-succeed.html
  • argument for local communities and against universal social networks

It goes by: the Book. It must be capitalized. /s