714 Matching Annotations
  1. Last 7 days
    1. Projects like the Open Journal System, Manifold or Scalar are based on a distributed model that allow anyone to download and deploy the software (Maxwell et al., 2019), offering an alternative to the commercial entities that dominate the scholarly communication ecosystem.

      Might Hypothes.is also be included with this list? Though it could go a bit further toward packaging and making it more easily available to self-hosters.

  2. Apr 2022
    1. mental health as pointed out by OECD

      OECD?

    2. ndicate the addictions that theInternet generates. Once the dependencies arefixed and eliminated,

      their big problem doesn't have any source. Working definition?

    3. digitalizationprocess is also reflected as an importantcomponent in the innovation development

      digitalization as innovation in business/political strategies

    1. personal integrative experience - an experience of ‘‘flow,’’ - inwhich the participant is fully emerged in the creative activity [48]

      Is there a way to convert the actions associated with the AE Group into a more "personal integrative experience"?

      a writing task? an assignment to consider it on own time?

    2. mechanistic explanations, theproduction of visual art involves

      What mechanisms does the production of visual art involve?

    3. valuative reception of artwork is anaesthetic experience, in which the parietal regions of the brain,especially the SPL, are associated with visuo-spatial explorationand attention [45]

      Possibility for why the Art Evaluation Group didn't have statistical significance

      (note: the ROI was in the left hemisphere)

    4. recentmeta-analysis by Mihov et al. (2010) demonstrated a relativedominance of the right hemisphere during abstract thinking

      Possibility for why the Art Evaluation Group didn't have statistically significant differences

    5. Such methodologicalconcepts might improve the art experience [22], [23], [24
    6. activation of the reward circuitby visual art perception for example [6]
  3. Mar 2022
    1. Based on the ISO 12913-2, albeit with small changes, the most appropriate causal/sematic classifications found here with respect to heritage could therefore be ‘social communal, ‘electro-mechanical, ‘voice and instrument’, ‘transport sounds’, and ‘other’ sounds. The accessibility of these classifications could then lead to a framework with a view to determine potential heritage importance of sounds.

      A well thought out set of categories for urban sounds, designed for the preservation of heritage

  4. rom-rb.org rom-rb.org
    1. We are looking for sustainable sponsorship. If your company is relying on rom-rb or simply want to see rom-rb evolve faster to meet your requirements, please consider backing the project
    1. Such exercises are somewhat akin to the reproducibility exercisescommonly used in quantitative methods instruction.

      Testing annotation. This claim comes from analyzing _ _

  5. Feb 2022
    1. Intruguing argument about how to allow more tinkering with software -- making it really easy to contribute, not just possible.

      I think for example the note-taking community is on a path towards that -- a lot of the fun is about finding your own worflow and contributing to editor plugins you like.

    2. “Well, it’s Open Source, I guess I could go download the source code… but… meh, it’s so far out of my way, not worth it,” and the urge fizzles out. I think that a lot of potential human creativity is being wasted this way.

      This reminds me of physical tinkering, like building or fixing your own small furniture. That's also hard with the products we often buy today -- it's difficult to fix minature electronics which are meant to be replaced.

      But with software (esp. open source) it could be easier, as everyone can have the same tools. I very much resonate with the idea of tinkering more and using less standards.

    3. Making changes or additions to the standard library was as easy as making changes to my own code

      For many people, making changes to code at all is hard. The few times I remember actually forking a library to add functionality, it meant hours reading into the codebase and polishing my change to commit it upstream.

      I like the author's argument, but it's not not just the friction to view source code -- many technical architectures are also needlessly complex or non-standard.

    1. Very interesting intro to financial programming at large banks. Basically, these systems replace Excel spreadsheets and thus treat everything as data with a minimal deployment process.

      It's bad that it diverges so much from normal Python programming. We can learn from some of these approaches, and so can they.

      For more context: https://news.ycombinator.com/item?id=29104047

    1. Hypothesis wurde 2011 als non-profit Organisation in San Francisco gegründet. Die Hypothes.is-Server stehen in Kalifornien. Hypothes.is ist Open Source Software und steht unter einer BSD-Lizenz. 

      -2011 -San Francisco -Open Source -BSD-Lizenz

    1. Stacker

      What is Stacker about. How reliable of a source are they? Are they fact checked, and if so how? Go over their about me page to see if this a source I feel comfortable citing. (Conclusion: I am actually pretty impressed. Mission statement is "We are on a mission to produce and distribute engaging data journalism to the world’s news organizations. Founded in 2017, Stacker combines data analysis with rich editorial context, drawing on authoritative sources and subject matter experts to drive storytelling." but they also are very transparent on the sources for the data. It is a good mix of government and private sector sources with reputations for accuracy)

  6. Jan 2022
    1. Testament of Pietrobono Burzelli

      This is his will- This is so cool!

    Tags

    Annotators

    1. In my very next letter, Letter XVI, I reported that Conor had perhaps heard our concerns about the cult connotations, and also decided to move away from the use of it too.

      I always thought of the #RoamCult hashtag as a bit tongue-in-cheek, but certainly something with a more positive framing could be chosen.

      It's interesting to hear that the project seems to have gone quiet and that the perception is that people are leaving for other projects (many of them open source, which is one of the spaces many of the early adopters were already working in).

      There's definitely a drive in a lot of this space for people to own their own data given it's direct value to them over other (more social facing) tools.

    1. Oh, I just figured out a workaround for my project, in case it helps someone. If you want the source of truth on the prop to come from the child component, then leave it undefined in the parent. Then, you can make the reactive variable have a condition on the presence of that variable. eg: <script> let prop; $: prop && console.log(prop); </script> <Child bind:prop/> Might not work for every use case but maybe that helps someone.
    1. Miracles reawaken the awareness that the spirit, not the body, is the altar of truth.

      How many times you thought a heavy bank account will make you happy? How many times you thought the same about careers, romantic lovers, fame or children and villa on a sheer? You might have also had some reveries that drinking alcohol will do or using drugs of any kind. Dig deep in this idea: what is it that you really want? If you look good enough you'll see the only reason why you're seeking all those things -- the joy is tied to them within your mind and it is joy indeed you really want. And yet, how many times your idols failed you? Weren't you shocked by the amount of side effects they bring? You thought a zillion coins will give you peace and happiness but what you've got is constant worry and distress. Is it not time for you stop chasing carrots but focus on your real goal instead?

      If you would look on anyone more closely to figure out their motivation and what exactly makes them tick, you'll be surprised to see that you are not the only one who's chasing happiness, it is at root for anyone indeed. There is no difference between a mother of a baby and user of some drug except in ways they're looking for it: the mother plans to get it from her baby the other - from the drug. Even the biggest tyrants you can name were doing what they've done only because they honestly believed: this is the way to joy. And so the universal goal is equal but everyone has a unique and special plan on how to get it, a map their very own. But if you've dared to lift this heavy brick of paper, it means you are among of those who've started to suspect: your plan has failed.

      what you seek for is a source of joy as you conceive it. T-24.5.1

      It never is the idol that you want. But what you think it offers you T-30.3.4

      You must have noticed an outstanding characteristic of every end that the ego has accepted as its own. When you have achieved it, it has not satisfied you. T-8.8.2

      It is essential that you accept the fact, and accept it gladly, that there is no form of littleness that can ever content you. You are free to try as many as you wish, but all you will be doing is to delay your homecoming. T-15.3.2

      I will not value what is valueless. W-133

      The world I see holds nothing that I want. W-128

      Seek not outside yourself. For it will fail, and you will weep each time an idol falls. T-29.7.1

      Perceiving equality, the Holy Spirit perceives equal needs. This invites Atonement automatically, because Atonement is the one need in this world that is universal. T-6.2.5

      Accept the plan you did not make W-186.5

      Only God's plan for salvation will work. W-71

  7. Dec 2021
    1. Open Source Software

      The argument for aligning OER with Open Source Software feels natural at first, but Jöran Muuß-Merholz argues that "Open is, what opens access" and that GoogleDocs might actually be more important for OER than LibreOffice. It's a utilitarian perspective. https://open-educational-resources.de/offen-ist-was-zugang-schafft-oder-warum-google-docs-fuer-oer-wichtiger-als-libre-office-ist/ (translated by Google Translate)

    1. oh by the way did i tell you it's hard like probably it's it's also really hard but i really don't want to stop here on a on a low note

      This is a great video on the reality of open source software. Open source hardware also faces similar funding issues.

      As long as open source is fundamentally dependent on the private sector, it will exist within at best a parasitic relationship. To truly develop an autonomous open source model requires a structural change in funding that allows it to stand alone and apart from corporate sponsorship.

      This is a classic chicken-and-egg situation. We want people to sponsor us, but many of those people also work for the private sector. Governments and NGOs may sponsor us, but they also depend on private sector for tax and donation revenues.

      This requires a much deeper discussion that unpacks the fundamental assumptions that underpin our economic, social and political systems. The structural challenges of funding open source exposes the constraints of our current system.

      Unless we examine the fundamental assumptions by which our current civilization operates, we cannot make the structural changes that would enable open source to reach its full potential, which is maximum access to shared intellectual and material resources for the benefit of all.

    1. Standard algorithms as a reliable engine in SaaS https://en.itpedia.nl/2021/12/06/standaard-algoritmen-als-betrouwbaar-motorblok-in-saas/ The term "Algorithm" has gotten a bad rap in recent years. This is because large tech companies such as Facebook and Google are often accused of threatening our privacy. However, algorithms are an integral part of every application. As is known, SaaS is standard software, which makes use of algorithms just like other software.

      • But what are algorithms anyway?
      • How can we use standard algorithms?
      • How do standard algorithms end up in our software?
      • When is software not an algorithm?
  8. Nov 2021
  9. Oct 2021
    1. Open source software is cited as the first domain where networked open sharing produced a tangible benefit

      The phrase should be:

      The Free Software and Open-source movements were the first domains where networked open sharing produced a tangible benefit.

      Why?

      Free Software movement started in 1983.

      Open-source movement started in 1998.

  10. Sep 2021
    1. (grid 2 325k),
    2. the field of comprehensive community initiatives (CCIs)

      How to evaluate comprehensive community initiatives and using what methods? 1) Lower expectations: Process documentation - lower expectations of evidence of impact 2) Force a Fit: force initiative into accepted evaluative method 3) Let time tell - wait until CCI is "ready" to be evaluated using common methods. FROM THE BOOK: http://www.aspenroundtable.org/vol2/connell.htm

    3. (grid 1 227k),

    Tags

    Annotators

    1. (They blame Chrome's "feature" addition treadmill, where "they keep adding stupid kitchen sinks for the sole and only purpose to make others unable to keep up.")
  11. Aug 2021
    1. I joined Caldera in November of 1995, and we certainly used "open source" broadly at that time. We were building software. I can't imagine a world where we did not use the specific phrase "open source software". And we were not alone. The term "Open Source" was used broadly by Linus Torvalds (who at the time was a student...I had dinner with Linus and his then-girlfriend Ute in Germany while he was still a student)

      From Linus Torvalds Remembers the Days Before ‘Open Source’:

      Torvalds counters that “I wouldn’t trust Lyle Ball’s recollection 100% about me… since my girlfriend-at-the-time (now wife) name was Tove, not Ute.”

  12. Jul 2021
    1. Looking deeper, you can see a large amount of issues open, bugs taking months to fix, and pull requests never seem to be merged from outside contributors. Apollo seems unfocused on building the great client package the community wants.
    2. This sort of behaviour indicates to me that Apollo is using open-source merely for marketing and not to make their product better. The company wants you to get familiar with Apollo Client and then buy into their products, not truly open-source software in my opinion. This is one of the negatives of the open-core business model.
    1. Growth hacking and lowest common denominator experiences are their problems, so we should avoid making them our problems, too. We already have various tools for enabling growth: the freedom to use the software for any purpose being one of the most powerful. We can go the other way and provide deeply-specific experiences that solve a small collection of problems incredibly well for a small number of people. Then those people become super-committed fans because no other thing works as well for them as our thing, and they tell their small number of friends, who can not only use this great thing but have the freedom to study how the program works, and change it so it does their computing as they wish—or to get someone to change it for them. Thus the snowball turns into an avalanche.

      This is exactly how I feel about Joplin - the open-source note taking application, developed as an alternative to Evernote.

  13. Jun 2021
    1. I’d still argue that offices can and do produce spontaneous, productive encounters.

      But so does any other form of collaboration. Most of the internet is run by code that was written by people communicating over email and IRC. There was no "open source office" that these people collaborated in.

    1. This, it seems to me, would be something like a readerly utopia. It could even (if we want to get all grand and optimistic) turn out to be a Gutenberg-style revolution — not for writing, this time, but for reading.

      I love the idea of this but implementation, particularly open implementation seems nearly impossible.

      Even getting digital commonplaces to align and register is tough enough much less doing multi-modal registration with the locations that books might live.

    1. Users who have installed it decided to trust me, and I'm not comfortable transferring that trust to someone else on their behalf. However, if you'd like to fork it, feel free.

      Interesting decision... Seems like the project could have been handed off to new maintainers instead of just a dead-end abandoned project and little chance of anyone using it for new projects now.

      Sure you can fork it, but without a clear indication of which of the many forks in the network graph to trust, I doubt few will take the (massively) extra time to evaluate all options and choose an existing fork as a "leader" (or create their own fork) to go with continuing maintenance...

  14. May 2021
    1. You can see the implementation here: https://github.com/sveltejs/sapper/blob/339c417b24e8429d3adc9c9f196bf159a5fce874/runtime/src/server/middleware/get_page_handler.ts#L137
  15. Apr 2021
    1. :structured - Lumberjack::Formatter::StructuredFormatter - crawls the object and applies the formatter recursively to Enumerable objects found in it (arrays, hashes, etc.).
    1. Manifold – Building an Open Source Publishing Platform

      Zach Davis and Matthew Gold

      Re-watching after the conference.

      Manifold

      Use case of showing the process of making the book. The book as a start to finish project rather than just the end product.

      They built the platform while eating their own cooking (or at least doing so with nearby communities).

      Use for this as bookclubs. Embedable audio and video possibilities.

      Use case where people have put journals on the platform and they've grown to add meta data and features to work for that.

      They're allowing people to pull in social media pieces into the platform as well. Perhaps an opportunity to use Webmentions?

      They support epub.

      It can pull in Gutenberg texts.

      Jim Groom talks about the idea of almost using Manifold as an LMS in and of itself. Centering the text as the thing around which we're gathering.

      CUNY Editions of standard e-books with additional resources.Critical editions.

      Using simple tools like Google Docs and then ingest them into Manifold using a YAML file.

      TEI, LaTeX formats and strategies for pulling them in. (Are these actually supported? It wasn't clear.)

      Reclaim Cloud has a container that will run Manifold.

      Zach is a big believer in UX and design as the core of their product.

    1. I also sell Sidekiq Pro and Sidekiq Enterprise, extensions to Sidekiq which provide more features, a commercial-friendly license and allow you to support high quality open source development all at the same time.
  16. Mar 2021
    1. This is not a fork. This is a repository of scripts to automatically build Microsoft's vscode repository into freely-licensed binaries with a community-driven default configuration.

      almost without a doubt, inspired by: chromium vs. chrome

    1. Sorry you’re surprised. Issues are filed at about a rate of 1 per day against GLib. Merge requests at a rate of about 1 per 2 days. Each issue or merge request takes a minimum of about 30 minutes (across at least 2 people) to analyse, put together a fix, test it, review it, fix it, review it and merge it. I’d estimate the average is closer to 3 hours than 30 minutes. Even at the fastest rate, it would take 3 working months to clear the backlog of ~1000 issues. I get a small proportion of my working time to spend on GLib (not full time).
    2. Age of a ticket is completely irrelevant as anyone can request anything but the number of developers is limited. If you'd like to see something implemented, please consider providing a patch. Thanks!
    3. Sorry if I sounded rude. I am using Gnome on a daily basis and am highly appreciating all the work anyone has put into it. I was just surprised when I found an AskUbuntu post from 2010 linking to this bug.
    4. Wow 14 years. I still keep stumbling over this issue...
    1. The reason we've avoided registering "Cinnamon" as a desktop name is that it opens up issues with many upstream apps that currently OnlyShowIn=Gnome or Gnome;Unity or just Unity. The relationship Mint has with Gnome and Ubuntu isn't genial enough that we could get them to add Cinnamon to their desktop files, so we would have to distribute and maintain separate duplicate .desktop files just for Cinnamon for these upstream packages.
    1. here is my set of best practices.I review libraries before adding them to my project. This involves skimming the code or reading it in its entirety if short, skimming the list of its dependencies, and making some quality judgements on liveliness, reliability, and maintainability in case I need to fix things myself. Note that length isn't a factor on its own, but may figure into some of these other estimates. I have on occasion pasted short modules directly into my code because I didn't think their recursive dependencies were justified.I then pin the library version and all of its dependencies with npm-shrinkwrap.Periodically, or when I need specific changes, I use npm-check to review updates. Here, I actually do look at all the changes since my pinned version, through a combination of change and commit logs. I make the call on whether the fixes and improvements outweigh the risk of updating; usually the changes are trivial and the answer is yes, so I update, shrinkwrap, skim the diff, done.I prefer not to pull in dependencies at deploy time, since I don't need the headache of github or npm being down when I need to deploy, and production machines may not have external internet access, let alone toolchains for compiling binary modules. Npm-pack followed by npm-install of the tarball is your friend here, and gets you pretty close to 100% reproducible deploys and rollbacks.This list intentionally has lots of judgement calls and few absolute rules. I don't follow all of them for all of my projects, but it is what I would consider a reasonable process for things that matter.
    2. I suspect you aren't seeing much discussion because those who have a reasonable process in place, and do not consider this situation to be as bad as everyone would have you believe, tend not to comment on it as much.
    1. JavaScript needs to fly from its comfy nest, and learn to survive on its own, on equal terms with other languages and run-times. It’s time to grow up, kid.
    2. If JavaScript were detached from the client and server platforms, the pressure of being a monoculture would be lifted — the next iteration of the JavaScript language or run-time would no longer have to please every developer in the world, but instead could focus on pleasing a much smaller audience of developers who love JavaScript and thrive with it, while enabling others to move to alternative languages or run-times.
    1. Goal: Give bug trackers like bugsnag access to sprockets generated source maps.
    2. If you don't mind putting the sourcemap url in the minified JS
    3. minified_url: MINIFIED_URL_PATH, source_map: HTTP::FormData::File.new(LOCAL_SOURCEMAP_PATH)
    4. //= link application.js.map
    5. While I understand orgs wanting not to expose their unminified source, it's security through obscurity (meaning it's not adding any real security).
    6. The only place I can find it is in the sprockets-rails gem. javascript_include_tag calls this: def find_debug_asset(path) if asset = find_asset(path, pipeline: :debug) raise_unless_precompiled_asset asset.logical_path.sub('.debug', '') asset end end
    1. Sentry supports un-minifying JavaScript via Source Maps. This lets you view source code context obtained from stack traces in their original untransformed form, which is particularly useful for debugging minified code (e.g. UglifyJS), or transpiled code from a higher-level language (e.g. TypeScript, ES6).
    1. For the $$$ question, nothing comes to mind. These problems i'm hitting up against are larger than a contractor could solve in a few hours of work (which would be hundreds/thousands of dollars).
    2. Yeah, can we pay money to make this go faster? Serious question.
    3. Progress is slow though. I want to change how assets are loaded, the current implementation of "pipelines" is challenging to work with.
    4. Our team is also looking into generating source maps in production/staging for error reporting (via Airbrake).
    5. I want source map in prod too (for error tracking, same as @vincentwoo)
    6. Could you explain your use case in a bit more detail? How are you using source maps without source map comments? Are you uploading them to a bug tracker?
    1. I'm trying to get official time at work to dedicate to source maps, and haven't made much progress there.