cultural reviewer and dabbler in stylistic premonitions

  • 38 Posts
  • 263 Comments
Joined 3 years ago
cake
Cake day: January 17th, 2022

help-circle

  • as a mod/admin, i would appreciate being able to edit post titles. there have been a fair number of times where i asked a poster to do so, and then waited a while for them to before deleting the post if they don’t.

    and/or, it would be nice to have a way for us to temporarily semi-delete a post while waiting for OP to make requested changes to it; that is, to hide it from the community view but leave it visible to people with the URL, or people who find it via the user profiles of the poster or commenters in it.

    editing titles would be awkward without an edit history or, at the least, a way to see that some 2nd party had edited it, and editing post bodies would be even more so. but it would make sense and be useful with an edit history, i think.

    i would also appreciate having content addressability, portable identity, composable moderation, and… perhaps a pony 😂


  • three suggestions:

    1. fyi, since your post links to https://lemmy.world/c/remy and https://lemmy.zip/c/remy icymi the preferred way to link to communities (so that everyone can access them via their own home instance) is like this: !remy@lemmy.zip. When someone types that in the lemmy web interface, it will auto-complete and expand it into link markup like [!remy@lemmy.zip](https://lemmy.zip/c/remy), but when that markup is rendered it will actually become a link to access the community via the reader’s home instance. For instance, for me that link will actually go to https://lemmy.ml/c/remy@lemmy.zip where i can interact with the community whereas https://lemmy.zip/c/remy will take me to the lemmy.zip website where i do not have an account. Here is a non-escaped example (my previous examples are all escaped with backtick characters to prevent them from rendering) which anyone should be able to click to load it through their own instance: !remy@lemmy.zip. Please ensure that your client can both generate and follow community links like this! (as well as user links to lemmy and other activitypub things; user links work the same except they’re prefixed with @ instead of !.)

    2. you don’t need multiple communities for your app; users from .world can post on .zip and vice-versa (and it is easy for them to if you link to the community the way described above).

    3. will you ever consider open sourcing it? :)


  • Nope.

    Nope, it is.

    It allows someone to use code without sharing the changes of that code. It enables non-free software creators like Microsoft to take the code, use it however they like, and not have to share back.

    This is correct; it is a permissive license.

    This is what Free Software prevents.

    No, that is what copyleft (aims to) prevent.

    Tired of people calling things like MIT and *BSD true libre/Free Software.

    The no True Scotsman fallacy requires a lack of authority about what what constitutes “true” - but in the case of Free/Libre software, we have one: https://en.wikipedia.org/wiki/The_Free_Software_Definition

    If you look at this license list (maintained by the Free Software Foundation’s Licensing and Compliance Lab) you’ll see that they classify many non-copyleft licenses as “permissive free software licenses”.

    They’re basically one step away from no license at all.

    Under the Berne Convention of 1886, everything is copyrighted by default, so “no license at all” means that nobody has permission to redistribute it :)

    The differences between permissive free software licenses and CC0 or a simple declaration that something is “dedicated to the public domain” are subtle and it’s easy to see them as irrelevant, but the choice of license does have consequences.

    The FSF recommends that people who want to use a permissive license choose Apache 2.0 “for substantial programs” because of its clause which “prevents patent treachery”, while noting that that clause makes it incompatible with GPLv2. For “simple programs” when the author wants a permissive license, FSF recommends the Expat license (aka the MIT license).

    It is noteworthy that the latter is compatible with GPLv2; MIT-licensed programs can be included in a GPLv2-only work (like the Linux kernel) while Apache 2.0-licensed programs cannot. (GPLv3 is more accommodating and allows patent-related additional restrictions to be applied, so it is compatible with Apache 2.0.)




  • I often see Rust mentioned at the same time as MIT-type licenses. Is it just a cultural thing that people who write Rust dislike Libre licenses?

    The word “libre” in the context of licensing exists to clarify the ambiguity of the word “free”, to emphasize that it means “free as in freedom” rather than “free as in beer” (aka no cost, or gratis) as the FSF explains here.

    The MIT license is a “libre” license, because it does meet the Free Software Definition.

    I think the word you are looking for here is copyleft: the MIT license is a permissive license, meaning it is not a copyleft license.

    I don’t know enough about the Rust community to say why, but from a distance my impression is that yes they do appear to have a cultural preference for permissive licenses.







  • Fuck this project, but… their source code can be free and open source even if they distribute binaries which aren’t. (Which they can do if they own the copyright, and/or if it is under a permissive non-copyleft FOSS license.)

    And if the source code is actually FOSS, and many people actually want to use it, someone else will distribute FOSS binaries without this stupid EULA. So, this BS is still much better than a non-FOSS license like FUTO’s.


  • I immediately knew this was going to be from Microsoft users, and yeah… of course, it is.

    Binaries distributed under this EULA do not meet the free software definition or open source definition.

    However, unlike most attempts to dilute the concept of open source, since the EULA is explicitly scoped to binaries and says it is meant to be applied to projects with source code that is released under an OSI-approved license, I think the source code of projects using this do still meet the open source definition (as long as the code is actually under such a license). Anyone/everyone should still be free to fork any project using this, and to distribute free binaries which are not under this EULA.

    This EULA obviously cannot be applied to projects using a copyleft license, unless all contributors to it have dual-licensed their contributions to allow (at least) the entity that is distributing non-free binaries under this EULA to do so.

    I think it is extremely short-sighted to tell non-paying “consumers” of an open source project that their bug reports are not welcome. People who pay for support obviously get to heavily influence which bugs get priority, but to tell non-paying users that they shouldn’t even report bugs is implicitly communicating that 2nd and 3rd party collaboration on fixing bugs is not expected or desired.

    A lot of Microsoft-oriented developers still don’t understand the free software movement, and have been trying to twist it into something they can comprehend since it started four decades ago. This is the latest iteration of that; at least this time they aren’t suggesting that people license their source code under non-free licenses.




  • Arthur Besse@lemmy.mltolinuxmemes@lemmy.worldthe perfect browser
    link
    fedilink
    English
    arrow-up
    2
    ·
    edit-2
    30 days ago

    The three currently-maintained engines which (at their feature intersection) effectively define what “the web” is today are Mozilla’s Gecko, Apple’s WebKit, and Google’s Blink.

    The latter two are both descended from KHTML, which came from the Konquerer browser which was first released as part of KDE 2.0 in 2000, and thus both are LGPL licensed.

    After having their own proprietary engine for over two decades, Microsoft stopped developing it and switched to Google’s fork of Apple’s fork of KDE’s free software web engine.

    Probably Windows will replace its kernel with Linux eventually too, for better or worse :)

    How else are Chrome, Edge, Brave, Arc, Vivaldi and co getting away with building proprietary layers on top of a copyleft dependency?

    They’re allowed to because the LGPL (unlike the normal GPL) is a weak copyleft license.