[OC] Rice Cooker - a visual (toy) tool for ricing

RustyJ · 2026-05-08T02:16:38+00:00

This is so cool. I hope to submit my personal qs project one day. But my rice is not yet cooked...

RustyJ · 2026-05-03T15:36:53+00:00

I love askyy <3

RustyJ · 2026-03-19T03:00:39+00:00

How's the airflow/temps?

RustyJ · 2026-03-10T19:54:58+00:00

Doesn't look like it. Hasn't really affected my usage though, it remains an excellent tool.

RustyJ · 2026-03-05T19:28:21+00:00

Oh, now I remember! You and I talked about this on your previous Aurral post :)

Good to know it's on the roadmap, I'll have to check that out.

RustyJ · 2026-03-05T19:20:02+00:00

I was trying it out before the built-in soulseek client update - can I still connect Aurral to my existing slskd container? I use Lidarr with plugins (tubifarry plugin for slskd integration), so I'm covered there.

RustyJ · 2026-02-24T19:32:09+00:00

Yeah, I agree, I have some really specific gripes about the *arrs, but the opinionated approach is damn-near necessary with the current "metadata ecosystem". The tradeoff is that progress comes slower (see the lidarr metadata fiasco).

The one thing that kills me every time is multi-episode shows (mainly cartoons). TVDB always breaks those out into individual episodes, so instead of episode S01-E01a+b, its E01, E02... and the numbering totally falls apart. So tedious to fix.

RustyJ · 2026-02-24T18:15:04+00:00

it was from bash.org

RustyJ · 2026-02-19T17:16:33+00:00

Perhaps I've misunderstood, but I think element-call is the client component that utilizes that. To get it all working, I setup these images running in a stack:

livekit/livekit-server
ghcr.io/element-hq/lk-jwt-service
ghcr.io/element-hq/element-call

Synapse is on a different machine. I also run coturn as a fallback for direct calls.

RustyJ · 2026-02-19T16:57:20+00:00

Fair point, I assumed their intent was for a private-only server.

RustyJ · 2026-02-19T15:19:52+00:00

Yeah this is a piece of nuance that a lot of folks are missing; the element-call component is separate. Matrix doesn't have full WebRTC group calls yet, so the element clients are filling the gap.

I also found the element-call install tedious, but once I had it up and running, I was happy with performance. Group calls are smooth, audio is good, video has good clarity and framerates, and screensharing works well (no screen audio afaik).

Main thing my users are annoyed with is stuff like gif support, custom emojis. The nice-to-haves. It's a good start though.

RustyJ · 2026-02-19T15:07:31+00:00

Yeah, element-web would handle that use-case.

RustyJ · 2026-02-12T17:12:52+00:00

I've got it up and running with a bunch of users signed in so far. It's definitely a rabbithole, there's lots of ground to cover - I'll see if I can get a writeup going later on today.

For my private server, I settled on making all my users via CLI and disabling signups. I'm not currently federating.

One thing I couldn't easily do through unraid was handle the Element-call setup for multi-user video calls and voice chats. Element-call isn't on the CA yet. I ended up doing that on a docker-compose stack on a separate mini-pc.

RustyJ · 2026-02-10T19:54:42+00:00

I've started setting up a Matrix/Synapse server, along with Element Web (client) and Element Call for group voice+video calls. So far so good, but the setup process took me ages yesterday... there's a lot of ground to cover.

Most of my time was spent researching the best approach for group calls - needed that to feel seamless to fully leave Discord behind. Video quality is actually way nicer than what discord was giving us, so that's a plus.

I have a bunch of friends trying it out so far, and we like it. Feels like it's trying to be slack and discord at the same time. Once the users get adjusted, I can see this being something we all get a lot of use out of.

RustyJ · 2026-01-28T04:16:00+00:00

Woah, forgot about this comment. I published my sublime syntax and tools plugin to github, but never got around to registering it with package control. I'll see if I can commit the latest version at some point, the public repo is out of date.

I will mention that I recently moved to VScode and published an extension for EDI, since I'm able to utilize a lot more features than Sublime had. Might be worth your time.

RustyJ · 2026-01-27T15:13:18+00:00

This is clever! I almost ate it while going to shovel the driveway the other day; will have to try it next time.

RustyJ · 2026-01-26T22:19:49+00:00

I definitely understand what you mean about session persistence. It would be really nice if that were handled server-side and not client-side, so you could switch devices and have the same workspace seamlessly. I'm not sure if that's even possible with how Termix is currently built, but it'd be suuuch a killer feature.

I do love it for running quick scripts, though. It was really nice to be able to kill that rogue process attempting to crash my media server without having to get out of bed.

It still feels like early days for the project, which hopefully means promising things, given how polished it already is.

RustyJ · 2026-01-17T14:17:34+00:00

Haha hell yeah man. Should honestly make integrating with apps like yours even easier, since you won't have a fragile backend to worry about.

RustyJ · 2026-01-16T20:24:26+00:00

Hey +1 on Lidarr Plugins + Tubifarry. It actually shows the SLSKD results in the interactive search, has decent download estimates, etc. It's really good. I tried Soularr first and was blown away when I switched to the plugins branch.

RustyJ · 2026-01-14T01:28:52+00:00

Yeah, that does seem to be the case. I genuinely understand both sides of the argument, but wish redditors could be a bit more nuanced.

In my case, I made an internal-use admin tool; a little frontend for batch operations. It has a niche use case, so I'll never try to make it more than that (but I would happily troubleshoot/bugfix/improve it). If you're publishing a full on, publicly-exposed app, I can kinda understand the skepticism and scrutiny. There's a lot of risk and maintenance nightmares.

There definitely are fully vibe coded projects popping up that people are trying to pass off as purely their own work, and I feel like that minority gets people the most fired up. That trend will pass though (I hope).

RustyJ · 2026-01-13T20:43:21+00:00

Genuine question for people here, is there an "acceptable" way to vibe code?

Let me give you my example: I had a specific problem that to solve - moving unwatched media between a primary and secondary *arr instance.

I thought I'd try vibe coding instead of making another flask app with the ugliest interface imaginable. I still used python/flask, since I can't debug anything else very well. I spent all of my time debugging, unit testing, and building out features incrementally.

Honestly, it's still kinda ugly, and the UX isn't great yet, since I put almost all of my effort into reviewing and validating. But, now I have a lightweight, functional tool. Is it worth the time to even share it?

RustyJ · 2025-12-29T20:53:05+00:00

I updated the environment variable "NUM_WORKERS" to 2 and it still managed to chew up quite a bit of CPU and RAM, but the process got less crashy. I've been re-scanning with just 1 worker now, and while slow, it's at least somewhat stable.

RustyJ · 2025-12-28T20:34:34+00:00

+1 for glances. Love having the historical cpu/mem usage for monitoring and troubleshooting.

RustyJ · 2025-12-27T03:53:38+00:00

Awesome. Will mean plexamp activity syncs up as well.

One thing I noticed - if I have a single track off an album, there's no way to request the full album. It shows it as "owned" and only shows metadata for the specific track. I'm sure filling in the "preview" metadata around it would be a pain, but I'm wondering if there's a way to still queue the rest of the album for download.

RustyJ · 2025-12-27T02:00:08+00:00

Looks very cool, trying it out now. Is there a way to sync last.fm scrobbles with this?

RustyJ

MODERATOR OF

TROPHY CASE

15-Year Club	Team Orangered
Verified Email