I had it running on Windows (no container) a while back. Wasn’t particularly difficult at that time, at least.

Can’t give any advice here though, since all we’ve been given to work with is an OS.

You absolutely aren’t wrong there.

Always in favour of healthy competition.

Haha well that’s uhh…

Ngl that’s a interesting idea. Would definitely want it running locally, though.

Right? Like, by this definition, the training algorithm is already “corrupting” the images by vectorizing them. This is just an overly roundabout way of saying “See? The image is cropped, so we good now!”

Haha no way! At this point I can’t think of a reason to switch from VLC, but I’d love to see a Winamp renaissance.

Yeah, before 2000 would make sense. Before 2038 would make sense. But specifically May 2020? That feels like an intentional choice to me… but why?

Regarding the TTS specifically, I remember looking into TorToiSeTTS back when this stuff was first coming out. You can generate ElevenLabs quality audio with it, but it’s insanely slow. In fact, when I was looking into it, it seemed like ElevenLabs may have been using a (much faster at the time) version of TorToiSe TTS, given the output is so similar.

According to the linked Github page, they seem to have solved the speed issues now, so it might be worth looking into. Of course, the other commenters have provided solutions that are pre-integrated into the LLM, but if you’re just looking for TTS this could be worth checking out. Also worth noting that this requires an NVIDIA GPU.

Of course, not to say the data isn’t also important though. It’s very possible that we’re missing something crucial regarding how the brain functions, despite everything we know so far. The more data we have, the better we can build/test these more streamlined models.

Ahh okay, interesting. I’ll have to give this a try, then.

True, these do sound like the best solutions honestly. I wanted to avoid something like Tailscale, since it just becomes another point for me to support/troubleshoot on the user end, but maybe I should reconsider. It’s a tradeoff, but it would also simplify a lot on my end.

Sorry, yeah, “broadcasting” was a bad word choice. What I meant was that if I port-forward, it exposes that socket to potential bad actors searching for exposed services.

Thanks, I’m only very vaguely familiar with NGINX, so I appreciate the clarification.

Thank you for such an in-depth reply!

There’s a lot to take in here, but it sounds like I’ve got some work to do - not necessarily a bad thing. It’s honestly about time I took my network more seriously and set up some proper routing / firewalls.

Yeah, thats definitely something I need to look into setting up.

Wouldn’t this require any user to connect to the VPN though? I’m looking for something more publicly accessible - say like a website.

Ahh okay, thanks for the clarification. Honestly I should use NGINX just for the sake of learning it, if nothing else.

I messed with pfsense a bit at my old job, but never really thought to use it in my home network - might just give that a shot, thanks!

Just in terms of broadcasting my home IP directly vs having a middleman, essentially.