Oh yes, the routers and gateways that most people have that are isp provided that may not actually have open VPN or wireguard support.

Those ones?

Also putting a VPN in someone else’s house so that all their Network traffic goes through your gateway is pretty damn extreme.

Nor will the VPN work on things like their TV or Roku or game console. You know the things that people typically sit down and watch media on…

Which doesn’t work for The grand majority of devices that would be used to watch said media.

Tvs game consoles rokus so on so forth typically don’t support VPN clients.

The Jonathan clients for these devices also typically don’t support alternative authentication methods which would allow you to put jellyfin behind a proxy and have the proxy exposed to the internet. Gating all access to jellyfin apis behind a primary authentication layer thus mitigating effectively all security vulnerabilities that are currently open.

It never made sense why you shouldn’t expose jellyfin to the internet?

I mean I think your link tells the story right?

I’m guessing I must have missed something here when I made that comment. I visited the link in the body of the OP not once, or twice, but three times to verify I wasn’t losing my mind. Even went into reading the readme, some issues…etc to verify.

I’m now realizing that in my Lemmy client the link in the body is more obvious to click on than the actual article itself.

Did you go to the repo before running your mouth? It’s awesome-selfhosted data.

What AI slop?

Edit:

I’m guessing I must have missed something here when I made that comment. I visited the link in the body of the OP not once, or twice, but three times to verify I wasn’t losing my mind. Even went into reading the readme, some issues…etc to verify.

I’m now realizing that in my Lemmy client the link in the body is more obvious to click on than the actual article itself.

Makes sense. I appreciate your replies

The commit history is 1 day.

Which is incredibly suspicious.

It is, but WSL is also pretty much shit.

I’ve been maining Windows with WSL at work, and it works great, till it doesn’t. And then it just sucks, and sucks, and sucks.

Almost always has to do with processes on WSL.not being killed by connectors to their windows counterparts. And docker desktop, holy hell, docker desktop and WSL just love to turn WSL into sludge.

I’ve been fighting with it for years, WSL is an awesome idea, it works great when it works. But as soon as you out real development loads onto it it just folds.

The maintainer you and said that they tirelessly tested, reviewed and verified changes over the course of 3 weeks to make sure that things were running and operating correctly.

This is how it should be done. It’s not like they’re vibe coding this.

Pretty much.

I’ve started using AI on a project last week and the first thing I do is write tests. Lots of tests.

With enough guardrails, you could actually get pretty decent quality output out of it and with enough regression tests, you can ensure that nothing’s actually breaking.

Similarly, reviewing its changes and actually reading the code that’s being generated to ensure correctness is necessary. However, I am finding ways to automate that and reduce the incident rate of problems to even lower than my co-workers.

Sure they can. Because what are you going to do financially ruin yourself in a lawsuit you’re going to lose against Microsoft or some other mega Corp who doesn’t give a shit about GPL licencing?

If it’s not enforced with teeth then it doesn’t matter anymore.

Dude, my team members put out code that’s like this or worse on a regular basis that gets caught in PR review without using AI tooling…

I’ve supported legacy projects that of course were built without tooling that didn’t exist. That are structured and written in ways that are far far worse than this.

Nothing here screams vibe coated.

Completely agree. If this is a skilled Dev who’s built products like this before and you can build something like this in your afternoons and weekends in like 6 months without LLM tool assistance.

With basic assistance you can definitely cut that time down to 4 months or less easily.

And if this is a full-time project, you can probably get it out the door in 1 to 2 months with llm assistance. (Not vibe coding, two very different things)

I’ve built projects of the size in 5-7 months before we had LLM or ML coding tools.

With tabbed completion (Which most devs enjoy), and before full LLM code gen, 4-6 months.

With llm assistance, not vibe coding, it’s possible to build projects like this in 1 to 2 months without sacrificing quality or safety. If you are an experienced engineer and have built projects like this before. A lot of these are boring, boilerplate, stuff.

So the time spent doesn’t necessarily say that it’s vibe coded but if this is an inexperienced engineer then it very well might be and may be full of holes and issues.

It’s a fucking black hole for information. I hate that they don’t direct people to at least GitHub issues or GitHub discussions.

Even worse are the people that have an open GitHub repo for their project and then tell you to go seek help on discord when you open a GitHub issue.

Ultimately, the solution to many problems caused by corporations abusing their positions is through taxation

It’s prism. A multi-launcher for Minecraft Java edition.

Even worse is when they strip the plus sign out after the fact and then you can’t log in anymore because you didn’t realize that’s what has happened.

Yeah, it should inflate to 15TB or more I think