/tg/Station 13

Bottom post of the previous page:

Nexendia wrote:So that makes the code near useless for anyone that branched from tg?

Unfortunately, yes. More unfortunately, "branches forked from /tg/station" includes basically everyone.

Cheridan wrote:

Nexendia wrote:So that makes the code near useless for anyone that branched from tg?

Unfortunately, yes. More unfortunately, "branches forked from /tg/station" includes basically everyone.

Good thing rules were made to be broken, right?

https://www.digg.com/r/SS13/comments/ ... tion_team/

Goon wrote: I am sure many will make a point of yelling "DAMAGE CONTROL", "Fucking GOONLUMINATI" "lol HORSE AFTER THE CART" or something else. The bile poured out at us since the leak has been rather astonishing. We will always have our detractors. However, we hope that people get some use and enjoyment out of this code now that it is out there. We will not be seeking to have any githubs / bitbuckets / codebazaars / internetvaluewarehouses pulled down, so sharing the "leaked" link isn't really going to be an issue. The spam can stop.

Does this imply that they are okay with people using the leaked code? If so does this change /tg/'s postion on using the leaked code due terrorism.

Does this mean we will see new servers that are forked goon code?

starmute wrote:Does this imply that they are okay with people using the leaked code? If so does this change /tg/'s postion on using the leaked code due terrorism.

They still probably want everybody involved to choke on an indeterminate amount of cocks, but they're not going to make a huge deal out of it now that its already out and everywhere because they know screaming DELEEETE THIIIIIIIS does literally nothing on the internet.

The only reason they even released the code was to save face.

starmute wrote: Does this imply that they are okay with people using the leaked code? If so does this change /tg/'s postion on using the leaked code due terrorism.

Read the rest of the thread. It doesn't matter how "okay with it" they are, that's not how licenses work. If they wanted to officially and legally change the license to not include Share-Alike they would need authorization from everyone who's ever contributed to goonstation.

Wyzack wrote:Does this mean we will see new servers that are forked goon code?

Absolutely.

From what little I'm aware of licensing can't we just just comment specific code as CC BY-NC-SA 3.0 and still keep our catch all GNU AGPL v3 for everything else?

And don't say "we don't have any premise for having certain code have something other than AGPL v3" cause we do. Tgui is CC BY-SA 4.0.

Incoming wrote:From what little I'm aware of licensing can't we just just comment specific code as CC BY-NC-SA 3.0 and still keep our catch all GNU AGPL v3 for everything else?

And don't say "we don't have any premise for having certain code have something other than AGPL v3" cause we do. Tgui is CC BY-SA 4.0.

Not accurate. The assets are CC BY-SA, same as most of our assets.

The clientside code is licensed under MIT. MIT is compatible with AGPL. MIT has very few restrictions and therefore has great license compatibility.

https://github.com/tgstation/-tg-station/pull/14933

So uh, since I know nothing about this license stuff, what happens if you just ignore the license incompatibilities and incorporate their code?

In reality though I assume it would be more logical (if not more practical due to code differences/incompatibilities) to write new code based off what we see in gooncode?

Highly trained teams of legal ninja's from the EFF swoop in your window and you sword fight them to the death.

If you're skilled enough to beat them stallmanu himself will come down on a ray of light and fight you with the gnu.

in all honesty probably nothing but we should avoid it anyway.

I wonder how he leaked it.

Goon coder had their password leaked, so the hacker found it, logged in, and got the code.

Zilenan91 wrote:The only reason they even released the code was to save face.

Or maybe they realised there's no point closing the barn doors when the horse has already bolted.

Not everyone is a whiney pathetic cry baby, zilenan

lumipharon wrote:So uh, since I know nothing about this license stuff, what happens if you just ignore the license incompatibilities and incorporate their code?

someone can sue you for violating a license and will probably win the case

it is unlikely to happen but we don't use licenses for nothing

Highlight of my year

I get some sort of sadistic satisfaction from this. Smug goon bastards

Goon Mining for /tg/ when?

Just say you took 'inspiration' from the goon code.

Steelpoint wrote:Goon Mining for /tg/ when?

Just say you took 'inspiration' from the goon code.

its on my todo list, a mashup of tg and goon mining

Waiting for Lifeweb code leak 2022 now

"borrow" all the terrain assets so we can start making our away missions look less ass.

MMMiracles wrote:"borrow" all the terrain assets so we can start making our away missions look less ass.

So much good stuff, don't even know where to begin.

Haha nope sorry.
sprite's aren't compatible either.

we can take literally nothing from this codebase.

(I mean technically the *IDEAS* are easier to get from the code/sprites than from playing goon, but we could already take the ideas)

Cheridan wrote:It is licensed under CC BY NC SA. The SA part means Share-Alike, which is a requirement that all derivatives of the licensed material be licensed under the same license. The license we use for our code is AGPL, which is not compatible with CC BY NC SA.

HOWEVER, our art assets are already licensed as CC BY NC SA, which is compatible with AGPL as they are not technically required for compiling the product. Meaning that we can freely incorporate any sprites in the release.

So does that mean we can use all the Wraith sprites/UI and apply it to Revenant?

Remie Richards wrote:Haha nope sorry.
sprite's aren't compatible either.

we can take literally nothing from this codebase.

(I mean technically the *IDEAS* are easier to get from the code/sprites than from playing goon, but we could already take the ideas)

How the fuck are Sprites not compatible?

Cheridan was wrong, ours are CC BY SA, not CC BY NC SA, because for whatever reason we allow people to sell our sprites.
this is woefully not compatible with CC BY NC SA, which does /not/ allow selling of material.

I cry.

So, can't we just change our license somehow?

Remie Richards wrote:Cheridan was wrong, ours are CC BY SA, not CC BY NC SA, because for whatever reason we allow people to sell our sprites.
this is woefully not compatible with CC BY NC SA, which does /not/ allow selling of material.

Dumb question, but is there a way to transition from CC BY SA, to CC BY NC SA?

DemonFiren wrote:So, can't we just change our license somehow?

Helios wrote: Dumb question, but is there a way to transition from CC BY SA, to CC BY NC SA?

That's what I'm looking in to.
to see if we can draw a line in the sand as it were.

We can't relicense the assets we already have, as that would require gathering anyone who as ever sprited for tg, and asking them to agree.

But I haven't yet found anything stopping us saying
"All assets prior to 03/03/2016 are licensed as CC BY SA, all assets after this date are licensed as CC BY NC SA, unless otherwise stated"

We have a similar line in the sand for when we went from GPL -> AGPL.

Remie Richards wrote:Cheridan was wrong, ours are CC BY SA, not CC BY NC SA, because for whatever reason we allow people to sell our sprites.
this is woefully not compatible with CC BY NC SA, which does /not/ allow selling of material.

I don't really see why we couldn't use CC BY NC SA sprites since our license is just a more permissive version of the same license. Just keep a readme somewhere of icon(states) that can't be commercialized.

Incoming wrote:

Remie Richards wrote:Cheridan was wrong, ours are CC BY SA, not CC BY NC SA, because for whatever reason we allow people to sell our sprites.
this is woefully not compatible with CC BY NC SA, which does /not/ allow selling of material.

I don't really see why we couldn't use CC BY NC SA sprites since our license is just a more permissive version of the same license. Just keep a readme somewhere of icon(states) that can't be commercialized.

No, it's explicitly stated those two are not compatible.
I'm leaving what we have as CC BY SA, but I'm going to make everything in the FUTURE CC BY NC SA, so we *can* use goon sprites/sounds, if we want (and also because selling other people's sounds/sprites is dumb)

Edit: https://github.com/tgstation/-tg-station/pull/15903

Is this because of Erro selling ian mugs?

Malkevin wrote:Is this because of Erro selling ian mugs?

No.

and Erro can continue to sell those mugs if he chooses, given that the Ian sprite will remain CC-BY-SA.

Malkevin wrote:Is this because of Erro selling ian mugs?

No.

and Erro can continue to sell those mugs if he chooses, given that the Ian sprite will remain CC-BY-SA.

public domain everything

Cheridan wrote:Good news, everyone! Goon has made a full public release of their code in response to the leak!

where actually is this release because i can't fuckin' find it

It was taken down pending a new release which has the code and assets from the devs who don't agree to the release being removed or remade.

They posted it on the /r/SS13 on digg. Many Developers for SS13 servers post there often.

Here's a link to the Goon teams 'official' announcement on the issue, as well as a link in the comments to their official code release: https://www.digg.com/r/SS13/comments/ ... tion_team/

Jordie0608 wrote:the code and assets from the devs who don't agree to the release being removed or remade.

what's the point of this with the leak out there?

Ricotez wrote:

Jordie0608 wrote:the code and assets from the devs who don't agree to the release being removed or remade.

what's the point of this with the leak out there?

Respecting the wishes of content creators.

Cheridan wrote:

Ricotez wrote:

Jordie0608 wrote:the code and assets from the devs who don't agree to the release being removed or remade.

what's the point of this with the leak out there?

Respecting the wishes of content creators.

I mean what is the point of content creators objecting against having their stuff in the official release if it's in the leak anyway?

¯\(°_o)/¯

Presumably most codebases with scruples would decline using leaked material, as we do.

lol

nothing got scrubbed from the re-re-release except server specific key stuff that literally only pertains to hosting the LLJK servers, guys

Ricotez wrote:I mean what is the point of content creators objecting against having their stuff in the official release if it's in the leak anyway?

Also the leak was not-quite-functional so the goon devs patched up the broken bits.

by the way, having sprites with a different content license is probably fine as long as the images with the more specific license are attributed clearly.

The CC licenses are not like the GPL in that they don't infect other works (other than derivatives) around them.

Licensing is confusing, weird, and due to the sordid history of the codebase probably irrelevant. Personal I like my experiences on goon code. I just cant stand the players or their hilariously explotible AI rules. Oh and you had to be an admins but-buddy to become Hos due to MUH GUNS. Their blob mode is good, add it to the shameless ripoff pool. Most of the secret shit was just a wired code meme surpassed by the rest of science powerecreep. oh and they still have original bombcode with silly caps so making ridiculous station killers is braindead easy.

Yeah they don't have caps on canister bombs so you can crash the server by setting off a bunch of those at once.

Taking a farty 2D spaceman simulator game to reallife court would be hilarious.

So I went digging through their code for the chem recipes, honestly I don't get why they aren't just up on the wiki, the shit needed to make half of them is game mode specific and even then absurdly hard to make, for example in order to make a werewolf serum there must already be a werewolf on the station in the first place.

Gibe recipies pls