Jonkman Microblog
  • Login
Show Navigation
  • Public

    • Public
    • Network
    • Groups
    • Popular
    • People

Notices by Alan Zimmerman (alanz@social.coop), page 12

  1. صفر (charlyblack@mastodon.social)'s status on Thursday, 26-Jul-2018 02:45:08 EDT صفر صفر

    review of "The Known Citizen: A History of Privacy in Modern America" by Sarah Igo

    "The midcentury fear that a subliminally designed newspaper advertisement could invade your headspace seems laughable compared to Facebook ads tailored to your browsing history, friends, and previous clicks."

    http://www.publicbooks.org/privacy-cultures/

    In conversation Thursday, 26-Jul-2018 02:45:08 EDT from mastodon.social permalink Repeated by alanz

    Attachments

    1. Privacy Cultures
      from Public Books
      In “USS Callister,” a much-discussed episode of Black Mirror, a reticent computer programmer collects DNA around his office from discarded objects like lollipops and coffee cups. He uses that DNA to ...
  2. Anarcha-Ecologist Catgirl (Em) (greenandblack@social.coop)'s status on Wednesday, 25-Jul-2018 15:59:06 EDT Anarcha-Ecologist Catgirl (Em) Anarcha-Ecologist Catgirl (Em)

    It's amazing that proprietary social networks have managed to create systems that elicit the most engagement out of negative emotions. Looking at Facebook/YouTube/reddit comments is like watching a perpetual shouting match

    In conversation Wednesday, 25-Jul-2018 15:59:06 EDT from social.coop permalink Repeated by alanz
  3. ar.al🌻 (aral@mastodon.ar.al)'s status on Tuesday, 26-Jun-2018 13:10:08 EDT ar.al🌻 ar.al🌻

    Web+

    My new site progressively enhances the centralised Web with peer-to-peer functionality using the DAT protocol. It’s a Web+ site: a little bridge between the centralised Web and the Peer Web.

    Peer web: dat://ar.al/2018/06/26/web+/

    Centralised web: https://ar.al/2018/06/26/web+/ https://mastodon.ar.al/media/1dw4DNXcAmY6TRvoRxY

    In conversation Tuesday, 26-Jun-2018 13:10:08 EDT from mastodon.ar.al permalink Repeated by alanz
  4. 🏵️ virtualice 🏵️ (cobaltvelvet@octodon.social)'s status on Tuesday, 26-Jun-2018 12:38:37 EDT 🏵️ virtualice 🏵️ 🏵️ virtualice 🏵️

    you may not like it but lisp is what peak programming looks like

    In conversation Tuesday, 26-Jun-2018 12:38:37 EDT from octodon.social permalink Repeated by alanz
  5. Ya favorite tho(ugh)t (are0h@playvicious.social)'s status on Tuesday, 26-Jun-2018 12:25:05 EDT Ya favorite tho(ugh)t Ya favorite tho(ugh)t

    I very strongly believe the future of the web is people taking back control their space rather than relying on the convenience of using the services of corporate structures.

    These places time and time again have proven they do not have our interest at heart and exploit our desire for convenience for their gain.

    We gotta flip the script and stop expecting places who have never had our interests in mind to change.

    We can do better. We don't need them.

    In conversation Tuesday, 26-Jun-2018 12:25:05 EDT from playvicious.social permalink Repeated by alanz
  6. ⦺ irick 🐁🐈⚩ (irick@vulpine.club)'s status on Tuesday, 26-Jun-2018 11:13:42 EDT ⦺ irick 🐁🐈⚩ ⦺ irick 🐁🐈⚩

    "What do feel you get out of your minor in electrical engineering?"
    Me: "A constant sense of wonder at the fact everything is not currently on fire."

    In conversation Tuesday, 26-Jun-2018 11:13:42 EDT from vulpine.club permalink Repeated by alanz
  7. Alex Schroeder 🐝 (kensanata@octodon.social)'s status on Tuesday, 26-Jun-2018 05:37:49 EDT Alex Schroeder 🐝 Alex Schroeder 🐝

    I was talking to a friend who was thinking about the internet we want to have, decentralized, less silos, a bit like the nineties where it was possible to have static pages, host email, write your own CGI scripts, and it was all step by step easy and possible if that was what you wanted. And we got talking about the kind of things we need to today to get this back. Do you have reading suggestions? Blogs to read? Projects? People to follow?

    In conversation Tuesday, 26-Jun-2018 05:37:49 EDT from octodon.social permalink Repeated by alanz
  8. switching.social (switchingsocial@mastodon.at)'s status on Tuesday, 26-Jun-2018 08:59:58 EDT switching.social switching.social
    • mhall119

    .@mhall119 is developing an ethical alternative to #MeetUp called #GetTogether.

    There's already a flagship site up and running:

    https://gettogether.community/

    The dev is working on #ActivityPub support and is requesting feedback on what more needs to be done:

    https://github.com/GetTogetherComm/GetTogether/issues/60

    If you're interested in helping federate GetTogether, join the discussion at the link above.

    #Alternatives

    In conversation Tuesday, 26-Jun-2018 08:59:58 EDT from mastodon.at permalink Repeated by alanz
  9. Scott Murray (scott@vis.social)'s status on Monday, 25-Jun-2018 23:47:09 EDT Scott Murray Scott Murray

    “If you want to make a safe place to create... you have to start by making the most vulnerable people safe first. So you have to take the people who have been most marginalized, most pushed away from conventional tech and say ‘you are going to be at the center of this, you’re going to be the first people we reach out to, to say does this work for you? Does this meet your needs?’”

    —Anil Dash on CodeNewbie podcast

    https://www.codenewbie.org/podcast/from-tech-blogger-to-fog-creek-ceo

    In conversation Monday, 25-Jun-2018 23:47:09 EDT from vis.social permalink Repeated by alanz
  10. Dominic Duffin (dominicduffin1@mastodon.technology)'s status on Tuesday, 26-Jun-2018 06:03:14 EDT Dominic Duffin Dominic Duffin
    • Rysiekúr Memesson

    @rysiek This illustrates nicely one of the most powerful things about federation, namely that the entire network can't just disappear due to the closure of one organisation. For this reason, I'd bet that the fediverse will outlive all the current centralised social networks.

    In conversation Tuesday, 26-Jun-2018 06:03:14 EDT from mastodon.technology permalink Repeated by alanz
  11. ❦ Billy Blaze ❦ (ckeen@mastodon.social)'s status on Tuesday, 26-Jun-2018 06:18:20 EDT ❦ Billy Blaze ❦ ❦ Billy Blaze ❦

    Maybe #scuttlebutt does not scale up to the internet, but it looks like human scale and given the gossip nature and connecton modes one would probably not exceed following the dunbar number of people anyway?

    In conversation Tuesday, 26-Jun-2018 06:18:20 EDT from mastodon.social permalink Repeated by alanz
  12. Adrian Cochrane (alcinnz@floss.social)'s status on Monday, 25-Jun-2018 19:15:47 EDT Adrian Cochrane Adrian Cochrane

    The Vala language, in which I implement Odysseus, is (much like CoffeeScript is to JS) a relatively simple transpiler to C. One who's main job is to add additional typechecking & abstract most uses of function pointers, void pointers, & memory management away behind pretty C#-like syntax.

    That is it parsed it's own Syntax to an AST, typechecks it, compiles it down into an AST for C, and has the C compiler parse that again to output assembly.

    Not a bad language, I much prefer it over Java.

    In conversation Monday, 25-Jun-2018 19:15:47 EDT from floss.social permalink Repeated by alanz
  13. Strypey (strypey@mastodon.nzoss.nz)'s status on Monday, 25-Jun-2018 08:30:42 EDT Strypey Strypey

    'The Architecture of Open Source Applications' is a set of free books (gratis *and* libre - #CC #BY 3.0) intended to help programmers learn about the various ways of structuring an applications, and which ones to use in which situations
    http://aosabook.org/

    In conversation Monday, 25-Jun-2018 08:30:42 EDT from mastodon.nzoss.nz permalink Repeated by alanz
  14. Chris Tallerås🎨🇳🇴 (christalleras@mastodon.art)'s status on Monday, 25-Jun-2018 08:41:56 EDT Chris Tallerås🎨🇳🇴 Chris Tallerås🎨🇳🇴

    I've uploaded my first video to https://share.tube/ (Peertube) It's my "How to import a workspace to Krita" video. Peertube is going to be the main platform I post videos to now. 😎 🤘

    https://share.tube/videos/watch/75fe7034-48aa-4ec1-8425-0582fff42df6

    #krita #peertube #sharetube #art #creativetoots #creative #mastoart

    In conversation Monday, 25-Jun-2018 08:41:56 EDT from mastodon.art permalink Repeated by alanz
  15. pinkprius (pinkprius@chaos.social)'s status on Monday, 25-Jun-2018 12:10:51 EDT pinkprius pinkprius

    #latestagecapitalism
    source: https://en.wikipedia.org/wiki/List_of_minimum_annual_leave_by_country

    In conversation Monday, 25-Jun-2018 12:10:51 EDT from chaos.social permalink Repeated by alanz
  16. Kurt Mosiejczuk :flan_cleaver: (kurtm@bsd.network)'s status on Monday, 25-Jun-2018 08:07:22 EDT Kurt Mosiejczuk :flan_cleaver: Kurt Mosiejczuk :flan_cleaver:

    I saw boosted onto my timeline a slashdot story being hysterical about "Google adding DRM" to android apps.

    First, that's misleading. They are adding digital signatures to them. You know, to help prevent tampering with the files you are installing. Sort of DRM, but I don't see them panicking about Debian using signed .deb files.

    Second, the link wasn't to slashdot. It was to federati.net. We're used to mastodon not tracking us. But apparently some GNU Social instances do. 😠

    In conversation Monday, 25-Jun-2018 08:07:22 EDT from bsd.network permalink Repeated by alanz
  17. ❦ Billy Blaze ❦ (ckeen@mastodon.social)'s status on Monday, 25-Jun-2018 10:09:31 EDT ❦ Billy Blaze ❦ ❦ Billy Blaze ❦

    Hm, so far I did accounting with ledger on my own, now I need some kind of easy visualisation and data entry via a web interface. Is there something you can recommend?

    #ledger #plaintextaccounting #askmastodon

    In conversation Monday, 25-Jun-2018 10:09:31 EDT from mastodon.social permalink Repeated by alanz
  18. Tsundoku Psychohazard (enkiv2@eldritch.cafe)'s status on Monday, 25-Jun-2018 09:15:48 EDT Tsundoku Psychohazard Tsundoku Psychohazard

    To distribute or not to distribute? Why licensing bugs matter | the morning paper https://blog.acolyer.org/2018/06/25/to-distribute-or-not-to-distribute-why-licensing-bugs-matter/

    In conversation Monday, 25-Jun-2018 09:15:48 EDT from eldritch.cafe permalink Repeated by alanz

    Attachments

    1. File without filename could not get a thumbnail source.
      To distribute or not to distribute? Why licensing bugs matter
      By adriancolyer from the morning paper

      To distribute or not to distribute? Why licensing bugs matter Vendome et al., ICSE’18

      Software licensing can quickly get quite complicated, with over 100 known open source licenses out there, and distributions often including components with a mix of licenses. Unsurprisingly, developers find it hard to determine appropriate licenses for their work, and to interpret the implications of including third-party software under different licenses.

      We present a large-scale qualitative study aimed at characterizing licensing bugs, with the goal of understanding the types of licensing bugs developers face, their legal and technical implications, and how such bugs are fixed.

      The result is a helpful catalogue of seven different categories of licensing bugs, with 21 sub-categories in total between them. Although the authors are not lawyers (as far as I can tell), it still constitutes a very useful list of things to think about. “Our proposed catalog can serve as a reference for developers and lawyers dealing with potential licensing issues.”

      The catalogue is drawn from an open coding exercise based on a statistically significant sample of 1,200 discussions randomly selected from a population of 59,426 discussions across a collection of issue trackers and mailing lists. The mailing lists were Apache’s legal-discuss, Debian’s debian-legal, Fedora’s fedora-legal-list, Gnome’s legal-last and OpenStack’s open-discuss. For issue trackers, the authors looked for issues using the keyword license on all 136 Bugzilla issue trackers in the Bugzilla installation list, as well as the issue trackers of 86,032 GitHub projects (selected to try and make sure these were not toy projects).

      Who cares about licensing?

      Before diving into the catalogue itself, it’s worth briefly reviewing the different stakeholders involved in licensing issues: there are holders of IP (e.g. trademark holders, patent holders, copyright holders), lawyers, and lawmakers, and then we can also call out:

      • Integrators, that reuse open source software within their own systems
      • Package maintainers, who are responsible for maintaining packages and integrating patches or bug fixes.
      • Distributors – any individual or entity distributing software
      • Developers (in general)
      • Community – either people involved in a specific open source community, or the open source community as a whole.

      Catalog overview

      The taxonomy is composed of 21 distinct sub-categories organised in 7 distinct high-level categories. Due to space limitations we only discuss a subset of the sub-categories (14). The complete taxonomy description and frequencies of each category can be found in the attached appendix.

      That appendix sounds like a useful resource. Unfortunately it’s not included in the only openly hosted version of the paper I could find (on the first author’s personal site, and linked at the top of this post). The descriptions we do get are still very useful though.

      It is important to remark that the results discuss the interpretation of developers and/or legal practitioners. Therefore it is possible that the legality of these interpretations or discussions may change (e.g., new interpretations can causes new legal precedents in the U.S.A.), on the enforceability may change in different jurisdictions.

      Selected licensing issues explored

      Let’s take a brief look inside each of the seven major categories.

      Laws and their interpretations

      At the base level, there is confusion over what is copyrightable? Software is copyrightable, but higher level designs and ideas may fall out of scope. Disagreements on the scope of copyright can lead to difficulties.

      A related issue is understanding what is a derivative work? (A work partially owned by the copyright author on which it is originally based). “… one of the most important features of open source licenses is that they should allow the creation and redistribution of derivative works.” It’s often unclear whether B should be treated as a derivative work of A, or just something that uses / bundles A. For example, Linus Torvalds asserts that merely using the kernel by making system calls does not constitute creating a derivative work. There is still plenty of disagreement even on this though.

      This is all further complicated by the fact that copyright, trademark, and patent laws are national in scope. Thus we often find clauses relating to choice of jurisdiction.

      … we observed that clauses related to choice of jurisdiction were a controversial topic within Debian in terms of their impact on software’s freeness. However, the distribution may be impacted by external factors like trade restrictions to a particular country or distribution of what a country considers sensitive material. While organizations or communities may want to facilitate global reuse, the organizations and individuals must comply with these trade laws.

      Policies of the ecosystem

      This category concerns issues relating to the licensing policies of specific open source communities such as the Apache Foundation, Eclipse Software Foundation, and Debian. These give community guidelines that projects within the foundation are expected to follow. For example, projects at Eclipse under the EPL cannot ship external libraries under the LGPL as part of their distribution. This makes for more complex user installation procedures if users have to assemble the last mile themselves.

      The FSF has specific guidelines on whether software with various licenses can be combined/derived alongside software licensed under the FSF licences.

      You need to think broader than just source code, images, fonts, databases, text files and so on all need consideration…

      Since IP clearance/evaluation extends to all bundled artifacts (not only source code and binaries), a non-free image or font could prevent the distribution of the software.

      Potential license violations

      Some licenses are incompatible with each other, and issues can arise when including dependencies or reusing source code that is incompatible with either the declared license, or with the the license of other reused components. Generally such an issue impacts the ability to distributed the software. As a specific example, Apache License 2.0 is incompatible with GPL v2. (See the full list here).

      Non-source code licensing

      When evaluating license compliance, you also need to consider non-source code artefacts, and in particular the need to make the source of those artefacts available. In GPL for example, source is defined as “the preferred form of the work for making modifications to it“. So if you distributed a PDF of a document, you would also need to distribute the source that generates that PDF.

      Documentation, like source code, is also protected by copyright.

      Even documentation shipped in HTML format has been questioned, since HTML is not the preferred form for making changes.

      Similar issues occur with other media such as fonts, images, and audio. An MP3 is likely not the preferred form for editing audio for example.

      Licensing content

      A license inconsistency occurs when there is a mismatch between the documented license and the actual source code licensing, e.g. inconsistencies between software licensing an the spec file documenting included licenses.

      Other IP issues

      Do you have the rights to use a contribution? . This is the arena of CLAs (Contributor License Agreements) and CTAs (Copyright Transfer Agreements). The fundamental difference between the two is that in the former case the author retains the copyright, and grants a license. In the latter case the author transfers the copyright. Without either of these, how can you protect the integrity of your software package?

      Projects that require CTAs/CLAs do it to reduce their legal risks… It is important to note that CLAs/CTAs are optional in the sense that an organization is not required to use them. However, it demonstrates that these open source communities would rather reject contributions than increase the legal risk of distributing code that may contain a license violation.

      Another thorny area is patents. From the debian-legal mailing list. It’s hard (bordering on impossible?) to know what patents may apply to a piece of software, including patents going through the approval process which may later be granted. A number of licenses include specific clauses relating to patents and their litigation.

      You also need to be careful to respect trademarks.

      Licensing semantics

      The final category includes licensing bugs relating to difficulties and/or confusion over the use of dual licensing or understanding the implications of particular clauses. As an example, developers considering migration to GPL 2.0+ need to consider the “or later” clause. How do you know you will agree with the terms of a future version of the GPL?

  19. Antanicus (antanicus@social.coop)'s status on Monday, 25-Jun-2018 02:44:45 EDT Antanicus Antanicus
    • Adrian Cochrane

    @alcinnz

    > We need to find a way to finance our user-facing software/hardware

    - No need to search further: the multi-stakeholder cooperative is the solution: user members are charged a fee, working members make a living, investing members get a return and everybody gets a vote.

    In conversation Monday, 25-Jun-2018 02:44:45 EDT from social.coop permalink Repeated by alanz
  20. Joseph Nuthalapati :fbx: (njoseph@social.masto.host)'s status on Sunday, 24-Jun-2018 15:56:37 EDT Joseph Nuthalapati :fbx: Joseph Nuthalapati :fbx:

    "Mark’s manifesto isn’t about building a global community, it is about building a global colony – with himself as king and with his corporation and the Silicon Valley oligarchy as the court."

    "Where Mark asks you to trust him to be a benevolent king, I say let us build a world without kings."

    A very well-written article with a lot of quotable sentences.

    https://ar.al/notes/encouraging-individual-sovereignty-and-a-healthy-commons/

    In conversation Sunday, 24-Jun-2018 15:56:37 EDT from social.masto.host permalink Repeated by alanz
  • After
  • Before
  • Help
  • About
  • FAQ
  • TOS
  • Privacy
  • Source
  • Version
  • Contact

Jonkman Microblog is a social network, courtesy of SOBAC Microcomputer Services. It runs on GNU social, version 1.2.0-beta5, available under the GNU Affero General Public License.

Creative Commons Attribution 3.0 All Jonkman Microblog content and data are available under the Creative Commons Attribution 3.0 license.

Switch to desktop site layout.