I haven't dug into Guix yet, so is the config more of a markup and less of Turing complete language? That sounds like it'd be easier to grock or optimize an LSP for.

I have heard that Guix takes a stronger stance with respect to unfree software. I don't think any of the official nix Hydra infrastructures build for unfree packages, but they are packaged and indexed into nixpkgs. Has Guix been difficult at all in that regard, i.e. using proprietary drivers or closed libraries for work or personal hardware?

I've been using TTS systems for decades with accessibility use cases, so other than quality audio books that necessitate a skilled performing narrator, I no longer mind.

In fact, I prefer legacy Bayesian phonetic models over the newer convolutional and recurrent neural networks, as their hard consonants and robotic consistency in pronunciations and intonation are much easier to listen and discern at higher words per minute, like at 3x or 4x natural speech rates for everyday blind reading, as compared to modern mumbling/slurring of syllables or artificial stridor and other breathy sounds.

From the video notes, this alternative to nix-serve looks promising:

• https://github.com/nix-community/harmonia

Perhaps one could use something like this using Android's Virtualization Framework in the meantime:

• Run Full Linux with GUI on Android 16 – Native Support!
  • https://youtube.com/watch?v=4hqsKyfwG6U

https://github.com/moq/moq/pull/1381

Yea, luckily Android can use the back navigation gesture in the PWA to traverse the site much like a browser tab's history. Android even has the lesser know forward navigation as well: handy when you accidentally pressed the back navigation gesture, but don't want to have to find the link you clicked before to get back to the same page you backed out of.

I wish the website or PWA had more of a short term memory about the state of pages you visit. As when I go back and forth posts and feeds, I have to return the content sort option back to what I was using before I left the comment section, as well as re-minimize the same comment threads, even if those comment subtrees never changed sence I folded them previously.

1. move topic collection into a new community

I think it would be hard to concretely categorise what should go into a new hypothetical !main(?) vs !programming given such a !main should still fall under the scope of the theme of the instance's name, programming. It could worsen the indecision for first time posters, or those trying to understand the applicable nuance between the two. Perhaps the community could keep with the classic montra "I know it when I see it" to keep posts on brand.

Also, IMO, trying to change the general default community from !programming to something else would be like trying to close the barn door after the horse has bolted, or like trying to change horses in midstream, given !programming is already our largest community.

Yeah, it was real nice once the kernel modules for PS DS3/4 finally shipped with Android's mainline. Although, it's still a pain that one needs to recompile the module to disable the rumble or LED when games using the device do not expose user level override settings.

I think circles are better. While circles don't pop out as much as cropped polygons, I think they still fit better with the general web ecosystem of avatars and profile icons. Not to mention they allow for a slightly larger canvas size for artwork already circle cropped by Lemmy-UI's CSS .

It would be cool if Communities could be rounded squares, and reserve circles for users, just like github orgs vs github users. That could help with readability between the two when skimming icons in lemmy's page feeds. But perhaps that should be a user customization. As long as most artworks abide by best practices for maskable icons, then different lemmy clients, web UIs, mobile app launchers, etc, could crop however they like:

• Adaptive icon support in PWAs with maskable icons
  • https://web.dev/maskable-icon/

The new brighter colors do help. BTW, I do love rainbows. One thing you might want to try is once you've settled on a good saturation and value for readability, you could diversify the hue across different icons (with perhaps the hues for the gradients derived from the original/official logos/icon's color palette, if not too difficult to maintain), allowing local communities to be more readily distinguishable from each other at a glance, while still unified stylistically for our instance, sort of like a colorful android launcher icon pack?

Perhaps we could code up scripts to do this theming, so we could automate this procedurally? Similar to this art pipeline:

• Favicon Generator. For real.
  • https://realfavicongenerator.net/

I really like the aesthetic of the local communities for general topic categories; great iconography!

For the lang communities, or communities for projects with widely recognizable or official logos, I'm not so sure about unifying those as well, as it could hamper the visual brand recognition and association of the community with its target focus. For example, with so many communities, it's kind of convenient to be able to quickly glance the list and pick out recognizable interests without even reading the multiple pages of search results or labeled lists.

That said, perhaps there is merit in going fully unified, as then remote subscribers could easily identify communities hosted from the programing.dev instance, a pattern that other instances like beehaw.org or lemmy.world have already set a UX precedent for.

However, beehaw does benefit from having a recognizable shape (a hexagon), along with a high contrast color pallet (black on yellow), making it easier to recognise silhouetted logos, given the high contrast, even at smaller resolutions no bigger than the subtitle font size in Lemmy's post feed. Admittedly, some of the black on purple gradients here look a little dark to read at font height scale.

Checking the issues tracker for RES, there's not yet any mention of lemmy or kbin:

• https://github.com/honestbleeps/Reddit-Enhancement-Suite/issues?q=is%3Aissue+is%3Aopen+lemmy

Perhaps you could ask there. I'd also recommend checking out the Lemmy Plugins & Userscripts community:

• https://sh.itjust.works/c/plugins

Indeed, video mediums can take longer to consume lesson material on mass, compared to written form tutorials and documentation, but some folks will always prefer learning from lecture style recordings. Still great for outreach and exposure for the Rust programming language itself though.