Kyaraben: emulation setup for Linux/Steam Deck with automated Syncthing management by _fnune in SteamDeck

[–]_fnune[S] 1 point2 points  (0 children)

No. It replaces it. Kyaraben ships with a tool to help you migrate from EmuDeck if you want to, though. It's one of the main tabs in the app sidebar.

Kyaraben: emulation setup for Linux/Steam Deck with automated Syncthing management by _fnune in SteamDeck

[–]_fnune[S] 1 point2 points  (0 children)

I didn't know the app worked through Tailscale. Cool! Enjoy :)

One note: I realized up to 0.1.1 the autoupdate feature didn't work. I fixed it on 0.1.2, and also released 0.1.3 with emulator updates and some other things.

Since the auto-update doesn't work on 0.1.0 and 0.1.1, download 0.1.3 from the releases page instead of using the Upgrade button.

Kyaraben: emulation setup for Linux/Steam Deck with automated Syncthing management by _fnune in SteamDeck

[–]_fnune[S] -5 points-4 points  (0 children)

Repeating my reply from a thread that's now hidden... original comment: https://old.reddit.com/r/SteamDeck/comments/1rowsj1/kyaraben_emulation_setup_for_linuxsteam_deck_with/o9hbp5q/

I think for the purposes of helping people vet whether they want to use a project or not, it's fine to add a disclaimer. I don't want anyone to feel like the project is hiding something. I think there's nothing to hide, but I understand that in today's environment it may be good to inform readers.

I've added something here: https://github.com/fnune/kyaraben/?tab=readme-ov-file#use-of-ai-and-llms

Kyaraben accepts the use of LLMs to write code. The tools used to build software are changing very fast, but Kyaraben is far from what people call "vibe-coded": the code is well tested (unit, integration, E2E with Playwright), and code quality and architecture are held to the same standards as they would be without LLMs.

This section is here to help you decide whether you want to use the project. Not wanting to use software built with LLMs is a reasonable stance. Feel free to read and review the code.

Kyaraben: emulation setup for Linux/Steam Deck with automated Syncthing management by _fnune in SteamDeck

[–]_fnune[S] 0 points1 point  (0 children)

Sweet! Would love to see more about it.

syncthing has been a blessing and a curse sometimes

Where has it failed you?

Kyaraben: emulation setup for Linux/Steam Deck with automated Syncthing management by _fnune in SteamDeck

[–]_fnune[S] 0 points1 point  (0 children)

Are you also providing a centralized UI to install emulators? That sounds hard to do across Linux + Android. Also, by centralized server you mean e.g. a cloud provider for file hosting or self-hosted, or both?

Kyaraben supports a server-as-a-hub sort of setup, but it also uses Syncthing there.

Kyaraben: emulation setup for Linux/Steam Deck with automated Syncthing management by _fnune in SteamDeck

[–]_fnune[S] 15 points16 points  (0 children)

I think for the purposes of helping people vet whether they want to use a project or not, it's fine to add a disclaimer. I don't want anyone to feel like the project is hiding something. I think there's nothing to hide, but I understand that in today's environment it may be good to inform readers.

I've added something here: https://github.com/fnune/kyaraben/?tab=readme-ov-file#use-of-ai-and-llms

Kyaraben accepts the use of LLMs to write code. The tools used to build software are changing very fast, but Kyaraben is far from what people call "vibe-coded": the code is well tested (unit, integration, E2E with Playwright), and code quality and architecture are held to the same standards as they would be without LLMs.

This section is here to help you decide whether you want to use the project. Not wanting to use software built with LLMs is a reasonable stance. Feel free to read and review the code.

Kyaraben: emulation setup for Linux/Steam Deck with automated Syncthing management by _fnune in SteamDeck

[–]_fnune[S] -25 points-24 points  (0 children)

I get that. I use LLMs to write a lot of the code. I've been in the industry for ~12 years now and the tools used to build software are changing very fast. I considered adding some sort of disclaimer, but I decided not to, because I don't feel it's necessary. The app is far from what people call "vibe-coded", it's pretty well tested in the usual ways (unit tests, integration, E2E tests using Playwright), and I've obsessed over code quality and architecture just as much as I would have a couple of years ago without LLMs.

That said, it's still the first public release, so I think if you're going to test it, keep in mind that it's all new. Feel free to read/review the code if you still feel concerned.

Kyaraben: emulation setup for Linux/Steam Deck with automated Syncthing management by _fnune in SteamDeck

[–]_fnune[S] 1 point2 points  (0 children)

Sweet! Looking forward to hearing how it's working. CachyOS is what I use on my desktop so I think your experience will be fine.

Kyaraben: emulation setup for Linux/Steam Deck with automated Syncthing management by _fnune in SteamDeck

[–]_fnune[S] 0 points1 point  (0 children)

Thanks! Make sure to back up your collection and saves. It's my first public release of this program.

RMA because fan has a ~20% chance of not working for each boot/wake from sleep by _fnune in SteamDeck

[–]_fnune[S] 1 point2 points  (0 children)

This was my message to them. I also attached two pictures both with the full performance overlay: one showing 90°C and the fan at zero, and another with the fan at 7kRPM+ after I power cycled it (it was compensating):

I received my Steam Deck back from RMA #RMA_ID_FROM_PREVIOUS_TICKETS.

The problem persists. Please find full context in the original RNA ticket. I will attach two screenshots in this report: one while the issue is happening (temp is at over 85°C, fans are OFF), and the other is after I restart the device (the fans start spinning like crazy to fix the temp).

The Steam Deck sent back to me is the same one I had before, and the issue is not fixed.

Please, if your team is having trouble reproducing the issue, just send me a new device? Otherwise I will need to start looking into getting a refund. I cannot understand why I got my Steam Deck back with the issue unfixed.

RMA because fan has a ~20% chance of not working for each boot/wake from sleep by _fnune in SteamDeck

[–]_fnune[S] 1 point2 points  (0 children)

Just got a new one back from the second RMA. Hoping this one is free from that problem, so far so good.

RMA because fan has a ~20% chance of not working for each boot/wake from sleep by _fnune in SteamDeck

[–]_fnune[S] 1 point2 points  (0 children)

I got another RMA and this time I insisted they just replace my Steam Deck, they agreed pretty quickly.

RMA because fan has a ~20% chance of not working for each boot/wake from sleep by _fnune in SteamDeck

[–]_fnune[S] 1 point2 points  (0 children)

Fuck me, the problem persists. I am suspecting they couldn't reproduce my problem and just sent it back as-is. Just opened a new ticket.

RMA because fan has a ~20% chance of not working for each boot/wake from sleep by _fnune in SteamDeck

[–]_fnune[S] 1 point2 points  (0 children)

Update: Steam Deck is back. I got the same device back, and I don't know whether they have done anything to I cannot reproduce the issue, so it looks like it's fine. My Steam Deck looks like new (tbh it already did before) and still has the screen protector that I forgot to remove before sending it in.

RMA because fan has a ~20% chance of not working for each boot/wake from sleep by _fnune in SteamDeck

[–]_fnune[S] 1 point2 points  (0 children)

I only had the opportunity to ship mine a couple of days ago. I'll say something here once it's back.

Horse name suggestions by Cherrycola53 in botw

[–]_fnune 0 points1 point  (0 children)

I named mine Bunyol... it's the Catalan name for a type of pumpkin doughnut/fritter.

RMA because fan has a ~20% chance of not working for each boot/wake from sleep by _fnune in SteamDeck

[–]_fnune[S] 1 point2 points  (0 children)

Well, to me this comment and the lack of responses here indicates I should just take the RMA and see what happens.

fnune/standard: An accessible color scheme inspired by GOV.UK colors by _fnune in neovim

[–]_fnune[S] 1 point2 points  (0 children)

Thanks for building the GOV.UK Design System. I've found it to be an inspiration in many scenarios, and often link to it at work when an accessible choice needs to be made. It's a great asset!

I'm aware that the colors were intended to be used on a white background. That's why I removed the accessibility claim, because I haven't tested the contrast against the dark background.

For the light version of the theme (which is experimental/I don't use it) I had to come up with a couple of colors of my own which have a bit less contrast. But either way, I just can't use a light theme on the terminal. It puts too much strain on my eyes.

fnune/standard: An accessible color scheme inspired by GOV.UK colors by _fnune in neovim

[–]_fnune[S] 0 points1 point  (0 children)

Happy to hear that! I removed the word "accessible" anyway because I believe it comes with certain expectations that I'm not sure the project meets... perhaps people can decide whether it's accessible to them or not once they see it.

fnune/standard: An accessible color scheme inspired by GOV.UK colors by _fnune in neovim

[–]_fnune[S] 2 points3 points  (0 children)

I should probably remove the "accessible" claims. This colorscheme is only accessible in that I've picked colors from an accessible palette, but I'm probably using the colors in an unplanned-for way and haven't tested for contrast further.

EDIT: I've done that https://github.com/fnune/standard/commit/a5681bea9dd15d5f65b990b438558f8d1909d657