Jonkman Microblog
  • Login
Show Navigation
  • Public

    • Public
    • Network
    • Groups
    • Popular
    • People

Notices by Tsundoku Psychohazard (enkiv2@eldritch.cafe), page 5

  1. Tsundoku Psychohazard (enkiv2@eldritch.cafe)'s status on Friday, 14-Sep-2018 13:14:05 EDT Tsundoku Psychohazard Tsundoku Psychohazard

    cyberpop: virtual reality
    cyberpunk: amphetamine psychosis

    cyberpop: augmented reality makes the city into a wonderland of useful information
    cyberpunk: augmented reality makes the city into a hellstorm of unskippable popup advertisements

    cyberpop: "information wants to be free!"
    cyberpunk: "I might have some information; who wants to know?"

    In conversation Friday, 14-Sep-2018 13:14:05 EDT from eldritch.cafe permalink
  2. Tsundoku Psychohazard (enkiv2@eldritch.cafe)'s status on Thursday, 16-Aug-2018 18:16:18 EDT Tsundoku Psychohazard Tsundoku Psychohazard
    • Nate Cull
    • Kartik Agaram
    • Coffee & Aspirin
    • Federated Republic of Sean
    • Lexi

    @akkartik

    OSMIC is a system for branching revision control on arbitrary byte sequences. Every revision has a unique address (a sequence of positive integers), and you can navigate between any two revisions with only the diff structure itself & a single revision with a known address. (This is a little more impressive than it sounds because of the branching: you absolutely could need to do a long sequence of fast forwards & rewinds.)

    @freakazoid @natecull @deejoe @Lexi

    In conversation Thursday, 16-Aug-2018 18:16:18 EDT from eldritch.cafe permalink
  3. Tsundoku Psychohazard (enkiv2@eldritch.cafe)'s status on Thursday, 16-Aug-2018 17:36:29 EDT Tsundoku Psychohazard Tsundoku Psychohazard
    in reply to
    • Nate Cull
    • Coffee & Aspirin
    • Federated Republic of Sean
    • Lexi

    @freakazoid @natecull @deejoe @Lexi
    One idea from Xanadu (and probably elsewhere too):

    1) your undo stack is literally branching revision tree

    2) that revision tree is permanent and you can point at a particular world state configuration

    In conversation Thursday, 16-Aug-2018 17:36:29 EDT from eldritch.cafe permalink
  4. Tsundoku Psychohazard (enkiv2@eldritch.cafe)'s status on Thursday, 16-Aug-2018 17:22:08 EDT Tsundoku Psychohazard Tsundoku Psychohazard
    • Nate Cull
    • Coffee & Aspirin
    • Lexi

    @Lexi @natecull @deejoe
    This is the thing. We need to separate big computing from small computing.

    If you're getting paid for it or someone gets hurt when it breaks, it's big computing and should be bulletproof. (Throw TDD and formal methods and everything else at it.)

    For everything else, it's small computing, which should be as fast and loose (and flexible and expressive) as possible.

    Big computing is ADA and small computing is LISP.

    In conversation Thursday, 16-Aug-2018 17:22:08 EDT from eldritch.cafe permalink
  5. Tsundoku Psychohazard (enkiv2@eldritch.cafe)'s status on Thursday, 16-Aug-2018 14:31:35 EDT Tsundoku Psychohazard Tsundoku Psychohazard

    This is a very hot take and also not a new one but here we go: the goal of a properly functioning software engineer is to obviate themselves, not by solving the customer's specific problems but by blurring the line between using a computer and programming one to the point where users can solve their own problems.

    In conversation Thursday, 16-Aug-2018 14:31:35 EDT from eldritch.cafe permalink
  6. Tsundoku Psychohazard (enkiv2@eldritch.cafe)'s status on Thursday, 26-Jul-2018 12:36:32 EDT Tsundoku Psychohazard Tsundoku Psychohazard

    There's a lobste.rs mirror on #gopher: gopher://sdf.org:70/1/users/julienxx/Lobste.rs/

    In conversation Thursday, 26-Jul-2018 12:36:32 EDT from eldritch.cafe permalink
  7. Tsundoku Psychohazard (enkiv2@eldritch.cafe)'s status on Wednesday, 18-Jul-2018 07:30:43 EDT Tsundoku Psychohazard Tsundoku Psychohazard
    • Strypey

    @strypey
    (If you've got a hundred bucks to spare & that sounds good to you, I recommend grabbing a cheap pair off Adafruit. Those are the most normal looking and also the most comfortable, because they're mounted in cheap sunglasses.)

    In conversation Wednesday, 18-Jul-2018 07:30:43 EDT from eldritch.cafe permalink
  8. Tsundoku Psychohazard (enkiv2@eldritch.cafe)'s status on Monday, 16-Jul-2018 11:36:32 EDT Tsundoku Psychohazard Tsundoku Psychohazard

    The Twitch streamers who spend years broadcasting to no one - The Verge https://www.theverge.com/2018/7/16/17569520/twitch-streamers-zero-viewers-motivation-community

    In conversation Monday, 16-Jul-2018 11:36:32 EDT from eldritch.cafe permalink

    Attachments

    1. Invalid filename.
      The Twitch streamers who spend years broadcasting to no one
      from The Verge
      Looking for connections in 2018
  9. Tsundoku Psychohazard (enkiv2@eldritch.cafe)'s status on Thursday, 12-Jul-2018 08:56:16 EDT Tsundoku Psychohazard Tsundoku Psychohazard

    Thought as a Technology http://cognitivemedium.com/tat/

    In conversation Thursday, 12-Jul-2018 08:56:16 EDT from eldritch.cafe permalink
  10. Tsundoku Psychohazard (enkiv2@eldritch.cafe)'s status on Tuesday, 10-Jul-2018 20:01:40 EDT Tsundoku Psychohazard Tsundoku Psychohazard

    I feel like I'm repeating myself when I say: knowing the ideological diversity of your enemy is TACTICALLY USEFUL because, when observed closely, any group large enough to be politically powerful is full of hidden fault lines and tense cease-fires

    In conversation Tuesday, 10-Jul-2018 20:01:40 EDT from eldritch.cafe permalink
  11. Tsundoku Psychohazard (enkiv2@eldritch.cafe)'s status on Friday, 29-Jun-2018 18:53:01 EDT Tsundoku Psychohazard Tsundoku Psychohazard

    tired: "drama"
    wired: "hypercare"

    In conversation Friday, 29-Jun-2018 18:53:01 EDT from eldritch.cafe permalink
  12. Tsundoku Psychohazard (enkiv2@eldritch.cafe)'s status on Friday, 29-Jun-2018 07:34:16 EDT Tsundoku Psychohazard Tsundoku Psychohazard

    Software only becomes 'enterprise grade' if, when its behavior is described to an outsider flatly and precisely, the outsider assumes the description is some kind of elaborate joke.

    In conversation Friday, 29-Jun-2018 07:34:16 EDT from eldritch.cafe permalink
  13. Tsundoku Psychohazard (enkiv2@eldritch.cafe)'s status on Wednesday, 27-Jun-2018 15:42:07 EDT Tsundoku Psychohazard Tsundoku Psychohazard

    Against Facebook https://0xadada.pub/2018/05/01/against-facebook/

    In conversation Wednesday, 27-Jun-2018 15:42:07 EDT from eldritch.cafe permalink

    Attachments

    1. Invalid filename.
      Against Facebook
      from 0xADADA
      On the commodification of attention, the abuses of unpaid microwork and strategies of resistance.
  14. 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

    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?

  15. Tsundoku Psychohazard (enkiv2@eldritch.cafe)'s status on Thursday, 21-Jun-2018 19:41:02 EDT Tsundoku Psychohazard Tsundoku Psychohazard
    • Overclocked, Custom Fox

    @Azure
    not nearly enough mermaids who owe me money for my taste tbh

    In conversation Thursday, 21-Jun-2018 19:41:02 EDT from eldritch.cafe permalink
  16. Tsundoku Psychohazard (enkiv2@eldritch.cafe)'s status on Sunday, 17-Jun-2018 17:39:26 EDT Tsundoku Psychohazard Tsundoku Psychohazard
    • Nate Cull

    @natecull
    web squirtles

    In conversation Sunday, 17-Jun-2018 17:39:26 EDT from eldritch.cafe permalink
  17. Tsundoku Psychohazard (enkiv2@eldritch.cafe)'s status on Monday, 04-Jun-2018 18:24:29 EDT Tsundoku Psychohazard Tsundoku Psychohazard

    If you're concerned about Microsoft taking over Github for even irrelevant reasons:

    Take this opportunity to migrate your repos to git-ssb or git-ipfs, instead of moving to another temporary host-tied third party thing like gitlab or bitbucket.

    Your commits are already identified by hashes, so why not switch to hashes entirely & use an NDN/DHT system?

    In conversation Monday, 04-Jun-2018 18:24:29 EDT from eldritch.cafe permalink
  18. Tsundoku Psychohazard (enkiv2@eldritch.cafe)'s status on Monday, 04-Jun-2018 16:10:53 EDT Tsundoku Psychohazard Tsundoku Psychohazard
    • Elly, nasty enby :heart_pan:
    • The_Gibson {UTC -4}

    @thegibson @Elizafox
    The term 'meritocracy' first appeared in a satire that was specifically pointing out the way such a formulation would reward people who are already unfairly privileged by screwing over everybody else.

    In conversation Monday, 04-Jun-2018 16:10:53 EDT from eldritch.cafe permalink
  19. Tsundoku Psychohazard (enkiv2@eldritch.cafe)'s status on Saturday, 02-Jun-2018 21:05:35 EDT Tsundoku Psychohazard Tsundoku Psychohazard

    So this is a thing that happened once:
    https://threadreaderapp.com/thread/1002696910266773505.html

    In conversation Saturday, 02-Jun-2018 21:05:35 EDT from eldritch.cafe permalink

    Attachments

    1. Invalid filename.
      Thread by @jamiebuilds: "I think it's time I publicly shared about how Microsoft stole my code and then spit on it. I'd been waiting for them to do something about i […]"
      Thread by @jamiebuilds: "I think it's time I publicly shared about how Microsoft stole my code and then spit on it. I'd been waiting for them to do something about it, but that is clearly never happening. When we were working on Babel 6, one of […]"
  20. Tsundoku Psychohazard (enkiv2@eldritch.cafe)'s status on Saturday, 02-Jun-2018 12:22:47 EDT Tsundoku Psychohazard Tsundoku Psychohazard

    Life hack: find the video in your youtube recommendations you're least interested in watching, click on it, turn off your speakers, and leave your house for a week.

    In conversation Saturday, 02-Jun-2018 12:22:47 EDT from eldritch.cafe permalink
  • 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.