The smallest footprint for an actual scripting probably will be posix sh - since you already have it ready.

A slightly bigger footprint would be Python or Lua.

If you can drop your requirement for actual scripting and are willing to add a compile step, Go and it’s ecosystem is pretty dang powerful and it’s really easy to learn for small automation tasks.

Personally, with the requirement of not adding too much space for runtimes, I’d write it in go. You don’t need a runtime, you can compile it to a really small zero dependency lib and you have clean and readable code that you can extend, test and maintain easily.

haven’t actually proven to be effective at stopping cheaters

This is what OP said, and it’s completely correct. It’s not that much impact in comparison to “regular” anti cheat systems. And both of those only detect either cheap/bad or known hacks.

Server-sided and data based anti cheats is what would actually be a huge step up. You’re running a 8 K/D in a game where the best players are between 1-2? Banned. You just flicked two enemies within 100ms? Banned. Suspicious activity that’s not that blatant needs to be reviewed.

The thing is - that’s fucking expensive, complicated and needs to be done one a per-game basis, and since its just cheaper to throw you under the bus with a kernel anticheat and claim it’s the best one, that’s being done.

Read up on the dangers.

Anything is beatable, hackable and abusable given the time and resources, and it shouldn’t be my system because some idiotic management took the decision to enforce ring0 access anti cheat to ban some percent more hackers.

No one said that anti cheat efforts do not make an impact, but the impact of ring0 anti cheats is massively overrated

Or you can just use vscodium.

If you use a dockerized environment, that will only work better on Linux. .NET8 is AFAIK natively supported on Linux, so there shouldn’t be too much of an issue apart from the usual clunkyness. Visual Studio will probably be more of a problem. The “easiest” way would probably be to switch to jet brains or vscode. If you are hardstuck on VS for whatever reasons, you probably should be able to do some voodoo with running it in docker and using the container as a remote desktop, but this will be PITA to setup and maintain.

Again, you may quote the FSF, but there are too many users of open source, as well as developers, who got into it for the reasons I stated. I can assure you that they are not doing it so that corporations can profit off their software without giving back.

If you are developing open source, you are not necessarily developing FOSS. If you are developing FOSS, you are also developing open source.

FOSS is well defined by the FSF, and it has been for ages, and to be frank, therefore no one cares for anyone’s personal definition of it.

What I am against is having the cake and eating it, as it’s being proposed with this licensing. Either you do FOSS, or you don’t. Either you do open source, or you don’t. Either you do proprietary software, or you don’t. It’s really that simple, because depending on your project, you take the terms that you see fitting and live with the consequences. The whole goal of this proposal was to be taken more serious as open source developers and projects, and to ensure funding for further development. Cherry picking the best parts of every model, and making irrational demands does not achieve that.

As I said, I’m absolutely on board that open source licensing and open source development being taken for profit by corpos absolutely sucks, and the usual licensing models have not aged well with the much wider adoption and usage of open source, and there is a need for change - as it’s being done e.g. by elastic, redis and others with their dual licensing.

It doesn’t matter how hard you want to call it FOSS, but with this licensing terms you describe it is not FOSS, period. And to be honest, you calling out various people for not getting what FOSS is, while you fully ignore the agreed on definition by people who are actually doing FOSS is you discrediting yourself.

You haven’t found a license like this, because your model is flawed: A licensing like this will disqualify you from any kind of usage in an actual FOSS licensed environment. Personal users, which will not be providing revenue, will not be really affected by this, and are irrelevant for your point. Corporate users, which you will mostly target by this new license probably won’t be able to use your funky new license because they will need to check with legal, and your software will need to have a lot of USPs for someone to bother with that. A 1% corpo-richness-tax will not be approved by any kind of bigger company, because it’s a ridiculous amount from the perspective of your potential customers.

You’re taking yourself way to important. Open source software is not replaceable as a whole, but individual projects are. If you want to earn money with your project, that’s good on you, license it accordingly, but do not try to upsell it as FOSS.

And I fully get your point, and I’m currently working on the same problem in my in-development project, and I’m not sure yet whether to dual-license it, for similar reasons you stated, and live with the consequences of providing OSS, but non-FOSS software, or do FOSS and provide it for actually free.

Edit: Also, the xz backdoor has nothing to do with funding. Any long time maintainer (as in not just a random person contributing pull requests) going rogue can happen in funded scenarios as well.

I don’t think that the current tools will be using it internally, since this would require the tools actually supporting the CLI launcher, and in the best case we would have something like the proton config in steam in every tool separately again.

I think that you will need to have your launcher installed, but you will have this new launcher as your entry point, from which you will start your games using proton from the linked project.

But - it’s a PoC right now, maybe both ways will be possible.

From a wishful perspective, it would be super neat if this new launcher would hook into the installed regular tools, and automagically make those use the preconfigured proton runtime it brings. Shouldn’t this be possible using LD_PRELOAD?

Right now it’s a PoC (proof of concept, a rough implementation of an idea), to emulate launching games from other stores as if they were launched from steam using proton.

What this could be used for is to create a new Linux launcher, where you setup proton once, and launch all games using this launcher.

This simplifies usage for you as the end user, since you would only need to install the launcher, and it sets up ProtonGE, and you’re done. It also enables simple Proton usage for other games (Epic, Lutris, whatever).

Additionally it helps unifying development. Windows games under Linux have a lot of moving parts: there’s Proton as a compatibility layer. There’s integration between steam, proton and your system (sniper/vessel). There’s protonfixes which is game specific changes in proton. Each of which itself consists of components and stuff I’ve missed. In short, it’s complicated. Unifying all this components with one tool, with one battle tested installation and compatibility and with a single source of truth in development could be another big step in Linux gaming.

TLDR - potentially a new launcher for games under the Linux, enabling any game to be played using proton, when supported, not only steam games.

Before you talked about the Fediverse as a whole, now from a single user perspective.

IMO it affects the Fediverse as a whole by abusing it. The whole idea is an open network, where instances can federate with each other to bilaterally share information and create a seemingly single platform. This is not the case with the planned Threads integration, because they explicitly plan to feed on the content, but hiding sharing their own content behind an (for most of their userbase) obscure opt-in.

From a single user perspective it doesn’t affect you directly. But it affects the platform you are part of with malicious intent.

I am not against Threads joining the Fediverse, and I do actually think it would be great for the growth of the Fediverse if actual big players join, and if it brings content that I personally do not like to see, I can use the tools available (e.g. blocking user/communities/instances) to hide it. But only if they plan on joining as a “regular instance” like any other - but Meta does not intent doing so, since they have chosen the opt-in with obvious intent of simply gaining additional content on their walled platform for their own gain.

The problem is not them reading data, but that Threads will take Fediverse content, and display it on Threads. In the opposite direction, Fediverse will only see the select few user content that do actually opt-in, and let’s be honest here, most users won’t know what the Fediverse is, except for again the few people that are on both platforms. This is absolutely not “playing nice” as you’ve put it before, and purely parasitic and, again, purely a greed decision by Meta. I don’t really know why you are shilling so hard trying to excuse absolutely unexcusable behavior.

https://www.threads.net/@mosseri/post/C051TLnud8U

There’s your playing nice. They want to feed on ActivityPub data, while only contributing in a per-user opt-in selection. It’s a joke, and both their motivation and what they are doing is absolutely fucked. It’s another cog in their data ingestion machine that they can keep fucking around with, again.

I really can not comprehend why anyone would give this advance of trust to Meta, when all signs are showing you to bail.

Meta has React, RocksDB and pytorch, and a few other “niche” frameworks and tools. “Half of the internet […] run[ning] on open source code and infrastructure that Meta built and maintains” is a big, big exaggeration. Also maintainance is done by the OSS community for big parts, and I’m really curious what open source infrastructure Meta is running.

I’m not saying Meta has no relevance in OSS, but I can hardly think of an open source org that does open source purely for its own benefit. React helps them shape the web in the way Meta wants it, their ML stuff is important for their own internal needs (ads, BI, and the whole social networking, etc.), their AR/VR/XR contributions are for the Quest, and KI/LLM since they need it themselves instead of relying/partnering with OpenAI. Meta (the company) absolutely does not stand by the principles of open source, no matter how much you want to sugarcoat it.

It’s not a hate train, it’s being cautious. And do you really think that Meta is open sourcing because of their passion for FOSS and standing by those values? They’ve taken an internal framework they’ve build, open source it so that they can advertise how open and great they are on the page you linked, and after it gains traction (which it will, since it’s used by Meta it must be good /s) they can reduce their own internal efforts to a minimum, since the community will contribute. Open source may be a passion for the developers of Meta, but the company Meta does not give a single flying fuck about FOSS or the Fediverse.

Well, guess how the comfy OK Google or hey siri works, hearing you while you say it all across the room. Or that noise cancelation for your calls. Admittably, the way he’s put it sounds really tinfoil hat weird, but he’s got a point there.

Any current mobile phone is so very crammed with sensors of any kind, which do make a lot of features possible/usable/comfortable and the same sensors may be used to track a good lot of your behavior, if used for malicious purposes. And we know that for a fact with targeted ads, where several people I’ve talked to noticed the same, where that even talking about a topic may be enough for ads to be show up. Check https://adssettings.google.com/ for example, it’s actually scary what Google “assumes” about you, and even scarier how on point those assumptions are. A lot of this information is sourced from your devices sensors, and the argument of “there’s just not that much computing power to process this data” is simply not valid anymore.