OneCardboardBox @ OneCardboardBox @lemmy.sdf.org

Posts

15

Comments

228

Joined

2 yr. ago

Barony is fun as hell. Engine is FOSS, but the default game assets require purchase.

You've laid out one potential development cycle: FOSS from the get-go, and open collaboration welcome.

However, that's not the only way that a FOSS game might be developed. The code could be freely licensed, but the upstream developers refuse to accept outside patches. In that case, there's one "original" and then if you don't like it, build your fork.

Alternatively, a game could be developed entirely in-house under proprietary licenses, and then only made FOSS upon commercial release. Contributor patches could improve the project, but conception of the game would be entirely the domain of its original developers.

The man is a monster. I don't know how many of my build jobs have been murdered by this fiend.

How about writing a script to automate the deletion, thus minimizing the chance of human error being a factor? It could include checks like "Is this a folder with .git contents? Am I being invoked from /home/username/my_dev_workspace?"

In a real aviation design scenario, they want to minimize the bullshit tasks that take up cognitive load on a pilot so they can focus on actually flying. Your ejector seat example would probably be replaced with an automatic ejection system that's managed by the flight computer.

I use a fuckload of soap and hope it keeps the grease from re-forming. Is that still bad?

You could delete it from lutris. I think that would nuke the prefix for FO3, thus allowing you to install freshly.

I think multiple comments would reduce clarity. It is rare for any signle point in an opinion to stand on its own as an atomic unit. A reader would need to jump through a thread to follow your line of reasoning in its entirety.

Single points of an argument may be valid or true on their own, but it is the mutual reinforcement of several points in agreement with each other that will educate or convince someone.

Yeah, I believe there's some kind of bridge mode you must enable on the host's interface.

As others have said, a reverse proxy is what you need.

However I will also mention that another tool called macvlan exists, if you're using containers like podman or docker. Setting up a macvlan network for your containers will trick your server into thinking that the ports exposed by your services belong to a different machine, thus letting them use the same ports at the same time. As far as your LAN is concerned, a container on a macvlan network has its own IP, independent of the host's IP.

Macvlan is worth setting up if you plan to expose some of your services outside your local network, or if you want to run a service on a port that your host is already using (eg: you want a container to act as DNS on port 53, but systemd-resolved is already using it on the host).

You can set up port forwarding at your router to the containers that you want to publicly expose, and any other containers will be inaccessible. Meanwhile with just a reverse proxy, someone could try to send requests to any domain behind it, even if you don't want to expose it.

My network is set up such that:

• Physical host has one IP address that's only accessible over lan.
• Containerized web services that I don't want to expose publicly are behind a reverse proxy container that has its own IP on the macvlan.
• Containerized web services that I do want to expose publicly have a separate reverse proxy container, which gets a different IP on the macvlan.
• Router has ports 80 and 443 forwarding only to the IP address for my public proxy

"Still stands" means that there is no known way to achieve it. Not that it's known to be impossible.

Until the discovery of the virtual console glitch for BitFS a few years ago, the A button challenge "still stood" for all cases.

For anyone wondering, this was done on the virtual console version, so the floating point glitch that lets you skip the climbing pole from Bowser in the fire Sea is available.

The A Button Challenge still stands for the console versions.

Did you mean source-available?

I guess? Always thought there was some pedantic Stallman-esque argument for the differentiation between FOSS and OSS, independent of the Open Source vs Source Available distinction.

Not sure if you're able to edit the title, but this doesn't look like FOSS, just open source.

I know this is a joke, but I couldn't be a programmer without some pedantry. LUnix is actually a real OS! I booted it on my Commodore 64 once.

https://en.wikipedia.org/wiki/LUnix

It would have to iterate over all saved keys, which sounds rather inefficient to me and potentially unsafe (timing attacks etc.)

sshd only checks for matches in the user's authorized_keys file, not system wide.

I'm ok if this requires better EM shielding of electric vehicles. RF bands are a natural resource, and we should prevent short term profit-seeking from shitting them up.

HR Giger is happily dead after seeing this

Wait, what's wrong with Grandpa Joe? He was a man sick with the humiliation and hopelessness handed down to him by society. Only the joy of seeing his grandson get a chance to be somebody was enough to cure him.

They would not even need to open source the servers. Just making the server available for users to run (even under a proprietary license) would be enough.

make up is my build command for pushing to prod