• 0 Posts
  • 46 Comments
Joined 7 months ago
cake
Cake day: March 22nd, 2025

help-circle







  • a friend of mine is getting their PhD in germany; the bureaucracy is nightmarish! and slow…sooooo slooooooow!

    they regularly have issues getting funds approved, even when applying months in advance, and regularly doesn’t have confirmation that his position will be continued into the next semester, and on and on… it’s seriously non-stop bullshit!

    makes me very glad that austrian bureaucracy, even though massively inefficient and excessive, at least works on human timelines!

    …most of the time, at least…






  • are you dumb?

    none of the links you posted talk about restrictions on certain materials within libraries, e.g. all of them allow you access any information at any time.

    ALL of the links you posted talk about restrictions on the membership registration process, not what you can and can’t borrow from the library.

    this isn’t about censorship, it’s just about establishing who you call when a kid misbehaves on library grounds or damages something the library owns.

    that’s why a guardian is required to co-sign memberships: kids break shit. like, all the time!



  • what a ridiculous idea. that’s not how anything works:

    copyright applies to the intellectual property, not the exact file.

    so the code itself is the copyrighted thing, not the file you download.

    it doesn’t matter whether you download the gpl version, you type out the gpl version by hand, or delete all new code until only gpl code is left.

    all you would need to proof is that the code is identical to the gpl code. how you got to that code is completely irrelevant.

    you have some fundamental misunderstandings about copyrighted material, intellectual property, and fair use.

    most importantly: copyright applies to intellectual property. the idea of a thing, not the physical thing.

    so in the case of this emulator, the file and where you got it from is completely irrelevant; only the content of the file, the code, has any meaning. which means any files that contain the same code are identical in the eyes of the law, regardless of how you got them.

    copyright is not a contract, but a license. and a license is a manual that explains how intellectual property (the idea of a thing, not the physical thing) is allowed to be used by someone. it’s not specific to an individual, which is why contracts have to be signed by both parties. so no, you don’t have a contract and no obligation to adhere to the new one at all. you can choose to use the old license, as long as you don’t use any of the new code.

    unless you want to modify and/or distribute the new code, the license (CC-BY-NC-ND) is irrelevant for the user.

    and you can modify your own private copy as much as you want, you just can’t distribute it, or modify and use it in a way that is illegal in some other way. but that’s about it.

    and all of this applies to both US and german law.

    and none of this is remotely relevant, because the gpl version is still available for download!

    nothing got replaced, so the gpl license is very much still applicable to that version of the software!

    “new” does not mean that the old version went anywhere; it’s still around. and you can still use, modify, and distribute it under the gpl.





  • 9bananas@feddit.orgtoTechnology@lemmy.world*Permanently Deleted*
    link
    fedilink
    English
    arrow-up
    2
    arrow-down
    1
    ·
    3 months ago

    yes and no:

    the copyright owner can do whatever they want, but they can’t really revoke a GPL license. that’s not really a thing.

    and the part about

    If you obtained your copy under the old license you can use it under the old license when you obtain a new copy you have a new license agreement.

    seems to me like you are implying that “use under the old license” means “run the program on my own machine”, but that’s not true, since GPL explicitly allows redistribution and modification.

    under a GPL license, you effectively give up control over your software voluntarily:

    The GNU General Public Licenses are a series of widely used free software licenses, or copyleft licenses, that guarantee end users the freedom to run, study, share, or modify the software.

    (highlighted the relevant portion for your convenience)

    this makes revoking the license effectively impossible.

    you could continue development under a different license, but that gets legally tricky very quickly.

    for example: all the code previously under GPL, stays under GPL. so if someone where to modify those parts of the code and redistribute it as a patch, you couldn’t legally do anything about that.

    which seems to be what the OOP claims the change to a CC-BY-NC-ND forbids, apparently misunderstanding, that this new license only applies to code added to the repo since the license change, not the code from before the license change.