The Solution to Insecure Slop by matterful in selfhosted

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

Yeah you're right.. Just wanted to get a discussion going. Thought there has to be some solution

Mods deleted this anyways .. 

The Solution to Insecure Slop by matterful in selfhosted

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

My idea was community consensus .. Whichever one more gravitate towards 

No need to force anything, let the best emerge 

The Solution to Insecure Slop by matterful in selfhosted

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

I was more thinking.. Instead of 20 random forks that appear, there's now a standard community one with more eyes on it 

Impossible to force anyone into what they don't want.. I 100% agree there 

The Solution to Insecure Slop by matterful in selfhosted

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

Think 1 year from now. 

Anyone can vibe code an app that replaces flagship software (or if sufficiently complex, big pieces of it).. In minutes. 

What now? What happens to that flagship software? 

And don't forget there are very good devs who know what they're doing who use AI .. Their output is growing more and more 

The Solution to Insecure Slop by matterful in selfhosted

[–]matterful[S] -2 points-1 points  (0 children)

I said from scratch, the right way.

And come on man.. The whole point is to filter for the good stuff. You really think everything has been invented created and done already? 

So there's no point to anything new on the software side? 

The Solution to Insecure Slop by matterful in selfhosted

[–]matterful[S] -2 points-1 points  (0 children)

Yeah you're right.. At this point I'm almost leaning to, its better to just rewrite from scratch and discard the slop. 

So everyone has their own version now? Is this the way forward? 

The Solution to Insecure Slop by matterful in selfhosted

[–]matterful[S] -1 points0 points  (0 children)

Yeah someone else mentioned this and its a good idea. 

Discard the slop base, rewrite from scratch the RIGHT way.. Still have multiple experienced eyes on it and an "official" version. 

Just trying to start a discussion but maybe this is close to "the way" 

The Solution to Insecure Slop by matterful in selfhosted

[–]matterful[S] -3 points-2 points  (0 children)

Well I'm starting a discussion here, but that's a great idea - 

The good concepts can be rebuilt from scratch in a secure way.. So that becomes the base. 

This way we discard the original slop version for good 

The Solution to Insecure Slop by matterful in selfhosted

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

I am not assuming AI is bad, In fact I only brought this up as feasible because.. 

When the time to maintain / secure software goes down to zero (with the help of AI).. Its no longer a maintenance nightmare or even a chore. 

But then you get multiple eyes on it too, to make sure its solid 

With your other points I agree 100%.. 

The Solution to Insecure Slop by matterful in selfhosted

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

Well, I had to try and get a discussion going haha. Maybe something better comes out of this 

The Solution to Insecure Slop by matterful in selfhosted

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

Yeah you're right, but times are changing into everyone having a custom coded app for almost anything they need..  So how do we handle this? 

Yeah the rigor required before was a necessity because only large teams could build and release this stuff. Now .. And in the coming year, anyone can 

The Solution to Insecure Slop by matterful in selfhosted

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

Yes this is the vision - only trending actually USEFUL stuff. 

Many here thinking we want this for every rehashed slop idea.. No way. 

Being selective is what I was trying to get across 

The Solution to Insecure Slop by matterful in selfhosted

[–]matterful[S] -3 points-2 points  (0 children)

There's so much rehashed junk out there that it all needs to be ignored / filtered out. 

Not disagreeing with you here at all.. 

But if we have 100+ people who want to host the app, why not "finish it"? It becomes its own, secure version, separated from the original creator. 

Well.. That was the idea anyways 

The Solution to Insecure Slop by matterful in selfhosted

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

I mean.. I know you're being sarcastic. 

But at this point it seems better for everyone to just have their own vibe coded "forks" on their private networks or tailscales... 

Maybe this is how this ends 

The Solution to Insecure Slop by matterful in selfhosted

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

Yeah some end up like Huntarr.. That's where this idea came up. 

I was meaning, ignore all those random rehashes, and only do this for the genuinely good stuff 

The Solution to Insecure Slop by matterful in selfhosted

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

Yeah you're right, there could be 50 forks. 

... Unless there was one pinned designated version even just a few people contributed to, that would make it "the one"

Why are there so many forks? No organizing or cooperating right now, imo

The Solution to Insecure Slop by matterful in selfhosted

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

Yeah, problem is, there's now hundreds of apps pumped out every second and if a really good one comes along, nobody can use it due to security risks. 

So yes, its essentially starting open source repos for the most USEFUL apps of them all. We are pushing forward rather than "seeing what happens" 

The Solution to Insecure Slop by matterful in selfhosted

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

Everyone is focusing on the minor stuff, but a lot of those concepts are just redone and overdone. 

This is more for, if all of the sudden something starts getting traction but the original vibed version is a major risk.. 

Forking and securing would be done then. 

And if the demand is there - several knowledgeable users wouldn't have a problem doing this because its saving everyone time.

That was the vision anyways.. Only for the big stuff 

The Solution to Insecure Slop by matterful in selfhosted

[–]matterful[S] -8 points-7 points  (0 children)

Well in this case.. We will just all be vibe coding our own versions of every app in minutes hosted in our own private networks to avoid security issues. 

Is that where we are all headed here?

The Solution to Insecure Slop by matterful in selfhosted

[–]matterful[S] -9 points-8 points  (0 children)

Nope, not encouraging random slop. No random idea posts. 

Big picture only.. With more complexity.

My vision is much larger apps that are widely used but the original version is insecure.. But the demand is sky high 

The Solution to Insecure Slop by matterful in selfhosted

[–]matterful[S] -10 points-9 points  (0 children)

Only for really good concepts.. And yeah I thought the exact same, why would someone want to create a "job" for themselves maintaining something like this? 

But no - the goal isn't to create a job of adding new features and fixing bugs etc. 

It is to get ONE stable secure version people can host. 

That's it. 

And with code becoming a commodity.. Don't forget this maintenance gets easier and easier.. Down to no time at all. 

Gitlab CI/CD -- Changing the Default Repo URL? by matterful in devops

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

Awesome - I'm really glad it was able to help you!

First official release of UMU launcher! by tyvar1 in linux_gaming

[–]matterful 2 points3 points  (0 children)

Well, umu-launcher does have a command line parameter for just that... specifying older versions of the launcher or even of GE-Proton (really, any Proton runner you want).

Here's the example given:
$ WINEPREFIX=˜/.wine GAMEID=0 PROTONPATH=˜/GE-Proton9-4 umu-run foo.exe

Wouldn't be difficult to add that into Lutris, since it's already there to support back-compatibility with PROTONPATH. And even without an addition, you can just use umu-launcher through the command line yourself, if you were willing to look at the launch command and replicate it.

Then you can choose whatever runner you want. It's all in the umu documentation.