Jump to content
Search In
  • More options...
Find results that contain...
Find results in...

Schneelocke

Members
  • Content count

    749
  • Joined

  • Last visited

Everything posted by Schneelocke

  1. Schneelocke

    Risen3D Sunk

    I misread what he said. Mea culpa - I should've paid attention when I read Wobbo's post. >_> If you use id's GPL'ed code in a way that violates the GPL, id can go after you for violating the license, but they cannot go after you for violating a contract. I'm not saying that there's never going to be any legal repercussions if you misuse GPL'ed code (whether there are depends on the goodwill of the copyright holder and whether they consider compliance or punishment more important), but it is a difference. But yes, using GPL'ed code in a proprietary project when you did not receive it under another license that allows you to do this from the copyright holder is - to use the *AA's terminology - piracy and should be treated as such. It's definitely not a "gentleman's crime" that nobody cares about and that's not serious.
  2. Schneelocke

    Risen3D Sunk

    I, at least, don't. One may argue that copyright in general is not fair or ethical (at least the way it is today), but the GPL basically boils down to a "tit for tat" kind of thing - feel free to take, but if you do, give back, too. I'm not sure what's unfair about that; quite the opposite, I think that taking *without* giving back is unfair and unethical. Also, since you mention EULAs... the GPL is not a contract, it's a license. You don't have to agree to anything in it, and you're not legally bound by it; however, if you do not accept the GPL, you only have the standard rights like fair use that copyright gives you. If you want to use (and by that I mean "use as a base for your own works") a GPL'ed program, you'll have to accept the GPL. And if you think that's unfair... tough luck.
  3. Schneelocke

    30uv2609 on Google Video

    Yeah, that's me - it seems to be working now. :)
  4. Reality (and I'm sure Grazza will post a much more detailed explanation of what "reality" encompasses now). :) Now, off to watching that new demo. ^^
  5. Schneelocke

    30uv2609 on Google Video

    Cool. :) *downloads* EDIT: I'm not sure if it's you or me, but I seem to be unable to actually connect to you to download anything, and someone else I asked for troubleshooting help also had the same problem, so I'm guessing it's some problem on your end. Just to be sure, can you successfully upload data for other torrents?
  6. Schneelocke

    30uv2609 on Google Video

    No problem. :) I'm still seeding everything myself; it's slow, of course (I can only upload with at most 20 kb/s overall, and I also need some of that for other stuff during the day at least), but it's better than nothing - and the files are still available, at least. :) And of course, everyone else is invited to download and seed the files, too - remember, the more people there are that participate, the faster everyone else will be able to download! :)
  7. Schneelocke

    30uv2609 on Google Video

    OK, cool - I made you a VIP, so you can upload stuff now. ^^
  8. Interesting, although it would've been even more impressive if you hadn't died / respawned. ;)
  9. Schneelocke

    30uv2609 on Google Video

    You can put it on my bittorrent tracker (http://tracker.schneelocke.net/) if you'd like to - just create an account, then tell me about it so I can give you upload priviledges. :) Vince and I successfully used it for various coop runs earlier this year, too. :) An 1.6 GB DVD will take a while to upload, of course, but it'll still be faster (and cheaper, not to mention more convenient) than mailing a physical DVD to interested people, for example.
  10. Schneelocke

    Not Taking Forever

    Probably "interesting, good concept, very atmospheric, will definitely be great once it's finished, but why did he use that ancient engine instead of something more modern with more capabilities and better graphics and less limitations?". ;)
  11. Schneelocke

    Risen3D Sunk

    *Assuming* that the compiler used, the rest of the toolchain and the architecture are all exactly the same and that you used the same optimisation options etc. (Just try setting CFLAGS to something non-standard before you run configure / make, for example.) Besides... when was the last time you downloaded binaries for some project and then compiled it yourself to see whether you would get a byte-exact match? (And if you actually do this and something doesn't match, do you assume that the author inserted a backdoor into the binaries, or do you assume that your toolchain, compiler options etc. didn't match perfectly after all?) What do people ever gain from writing/distributing malware, trojans etc.? Yes, someone *could* just provide community binaries, but you're assuming that the whole thing actually gets noticed (otherwise, why would anyone?), and you're also assuming that the author couldn't already gain something. Depending on what kind of backdoor you're talking about, it might well be worth it even if you can exploit it only for a limited time. And FWIW, not all backdoors would have to be as obvious as the one in csDoom, anyway. Would you notice an off-by-one error leading to an exploitable buffer overflow in some port's server code? I know I probably wouldn't, unless I was actually and actively hunting for things like that. I'm not sure how X-Chat is related. People are providing unofficial builds for X-Chat because the official ones cost *money*; if they didn't, nobody would bother. (And for that matter, back when they didn't, nobody *did* bother, at least as far as I know.) Overall, it's not something I'd worry about. But blindly assuming that published source code means that the published binaries were produced from that exact source code is not always correct; and assuming that if they weren't, this'd be noticed right away (or at least soon) also isn't. Not that it probably matters much, but you should keep in mind that whenever you run someone else's binaries, you're at risk, and published source code will only help with unintentional holes, not with intentional backdoors that the attacker is actively trying to conceal from you.
  12. Schneelocke

    Risen3D Sunk

    Just to add something constructive to the debate: how do you know that the binaries are actually produced from the exact source code you're downloading, instead of a bugged version? Of course, source will help you if you compile it yourself[1], but binaries still have to be trusted either way. :) 1. Not counting the fact that the C compiler itself may be bugged - see Ken Thompson's classic "Reflections on Trusting Trust" talk. But I guess that this is a problem you can mostly ignore when you're only worrying about backdoors in DOOM source ports. :) EDIT: fixed grammar. D'oh.
  13. Schneelocke

    Risen3D Sunk

    If he is, then it's probably because you clicked on AlexMax's helpful little link above. :) http://downtime.templeofhate.com/~niehaus/muh-tation.jpg
  14. Schneelocke

    Not Taking Forever

    Yes, I came across that one, too. Also, it would be nice if it wasn't possible to kill the mushroom pieces you're supposed to move around... :)
  15. Schneelocke

    New tricks (built demos)

    cbt3-013? ;) Seriously, though, looking forward to it... :)
  16. Schneelocke

    Risen3D Sunk

    Doom *was* made available under another license prior to being GPL'ed. But yeah, I agree with you outside of that. The author either has a legal obligation to publish the source, or he doesn't. If he does (because he used the GPL'ed verson of the DOOM sources, for instance, or because he incorporated other GPL'ed code), well, he has only himself to blame; if he doesn't, well... then I'm not sure what his problem is. He made a decision, and he should be able to live with others not agreeing with that decision; either that, or just give in and release the source after all. The kind of stunt that's actually being pulled now is childish and immature, to say the least.
  17. Schneelocke

    Not Taking Forever

    Neat. :) It's too late by now for me to give it a try today, but I'll definitely check it out tomorrow.
  18. Schneelocke

    New HR2 demos

    What a sweet way to end a day, especially one that mostly revolved around an (unsuccessful) visit to an oral surgeon. I'll watch this now before I go to bed, as a treat. :)
  19. Schneelocke

    New HR2 demos

    Cool. :) BTW, it's generally a better idea to make new posts instead of editing old ones - VBulletin does not send out reply notifications for edits, so it's much easier to miss those, especially when you've already read the unedited post. :) Great demos, though. :)
  20. Schneelocke

    PrBoom-Plus, ver. 2.5.1.4

    This one plays back fine for me in PrBoom 2.3.1 (without emulation, naturally :)).
  21. Yes, I typically use 2.3.1 myself for watching demos. The reason initially was that there was nothing newer (prior to the 2.4.x series); later on, IIRC, I didn't switch because of the changes on the Options screen which I had gotten used to, although it's been a long time since I checked that, so this may not be accurate. I should probably switch to something newer, like prboom+. :)
  22. I fail to see why that is an advantage. :)
  23. Just out of curiosity, what is the advantage of using 2.2.3 and not - for example - 2.2.6?
  24. Schneelocke

    Toke it up!

    I think it's a great idea, and a great way to honour Toke's memory.
  25. Schneelocke

    My Heretic Demos!

    Here's a general hint: when uploading a demo, always include a zip file with some basic information like what game/level you played, the skill, the time you got, kills%/secrets%, your name, the port you used for recording, and so on - a raw demo file is useless when you find it again on your HD five years later. :)
×