1,174 Matching Annotations
  1. Dec 2022
    1. As Chris brains Jeremy with abocce ball, the deer’s head is prominent in the background of the shot. Wewould hypothesize that the deer is a reminder not only of his mother (viahis earlier experience with the dying doe), but also of his ancestors moregenerally. African rhythms begin to pulse as Chris takes down Jeremy, andas Chris’s eyes flick to the buck’s head, lyrics are whispered in Swahili, thesame as the opening credits, translating to “Something bad is coming, listento your ancestors, run.” Through this non-diegetic song, with its whisperedmessage from the ancestors, the deer effectively speaks. It then aids Chris inhis escape when the buck’s horns serve as a weapon to kill Dean Armitage

      BIG!!!!

    2. He is tied up in the game room, facingan old television set, above which is the taxidermied head of a large buck.Its appearance of life-in-death not only foreshadows Chris’s future state ifthe Armitages’ plot is carried off successfully, as a Black body occupied bywhite consciousness, but it also reverberates with characterizations of thehistorical devaluation of Black lives in Atlantic slavery, as socially deadnon-subjects
    3. eacts in a strangely unsympathetic way. “Well, you know what I say?”he responds. “I say, one down, a couple hundred thousand to go. No, I don’tmean to get on my high horse, but I’m telling you, I do not like the deer.I’m sick of it. They’re taking over. They’re like rats. They’re destroying theecosystem. I see a dead deer on the side of the road, I think to myself, ‘That’sa start.’

    Tags

    Annotators

  2. Nov 2022
  3. www.mygard.info www.mygard.info
    1. Donations

      To add some other intermediary services:

      To add a service for groups:

      To add a service that enables fans to support the creators directly and anonymously via microdonations or small donations by pre-charging their Coil account to spend on content streaming or tipping the creators' wallets via a layer containing JS script following the Interledger Protocol proposed to W3C:

      If you want to know more, head to Web Monetization or Community or Explainer

      Disclaimer: I am a recipient of a grant from the Interledger Foundation, so there would be a Conflict of Interest if I edited directly. Plus, sharing on Hypothesis allows other users to chime in.

  4. Oct 2022
  5. www.indxd.ink www.indxd.ink
    1. https://www.indxd.ink/

      A digital, web-based index tool for your analog notebooks. Ostensibly allows one to digitally index their paper notebooks (page numbers optional).

      It emails you weekly text updates, so you've got a back up of your data if the site/service disappears.

      This could potentially be used by those who have analog zettelkasten practices, but want the digital search and some back up of their system.


      <small><cite class='h-cite via'> <span class='p-author h-card'>sgtstretch </span> in @Gaby @pimoore so a good friend of mine makes [INDXD](https://www.indxd.ink/) which is for indexing analog notebooks and being able to find things. I don't personally use it, but I know @patrickrhone has written about it before. (<time class='dt-published'>10/27/2022 17:59:32</time>)</cite></small>

    1. @route @twalpole as a community I think we're super grateful for your work on a CDP alternative to chromedriver/selenium, poltergeist etc. I do think collaboration could be very valuable though, although it would likely mean abandoning one of the projects and teaming up on the other, you both obviously have very deep knowledge of CDP and therefore would get a load more done than any of us "end users" trying to wade in there. The status for us on our Rails project is that Apparition fails with a ton of errors, they all seem related to handling timing events (accept_prompt doesn't work, opening new windows seems problematic etc etc etc) whereas Cuprite only rails with a cookie gem we're using (easy fixed) and doesn't support drag_to yet. So to me Cuprite seems more complete, but I don't know much about the internals.
    2. As a history mark, when back then I asked Thomas if he started to work on CDP, he said yes but never finished it, so I started this project from scratch which by now feels completed. After releasing it I only yesterday realized that he open-sourced his project and keeps working on it. I think it just feels hard to throw everything you have written to trash, but I wasn't proposed at the beginning to work together on common project and this is the reason Cuprite had began. Though since this project is completed I see no sense to work on something else especially for me, the only difference would be in Ruby implementation which is boring as you can do things in a different manner and CDP has issues too so the difference could be only how we workaround them.
    3. Haven't really looked through your code, so not sure what the difference is - I would guess not too much. I told you about my version when we were discussing the issues you were having on cuprite -- It was 70+ percent done so I released it and finished up most of the rest. I guess one difference is that you appear to be aiming at bleeding edge Chromium, whereas I'm more focused on things working on Chrome release since I think that's more important for people to test with (no customer is going to be running Chromium alpha).
    1. In Mostaque’s explanation, open source is about “putting this in the hands of people that will build on and extend this technology.” However, that means putting all these capabilities in the hands of the public — and dealing with the consequences, both good and bad.

      THis focus on responsibility and consequences was not there, in the early days of open source, right?

  6. Sep 2022
    1. Think about how good it is if you can build a system at “2 half brain quality” and then people just need use 1 half of their brain to maintain it. You can fix bug in a blink of an eye, run tests and give it to tester, done. Everything will be done in a easiest way and fixing bug or refactoring can be easy like breathing. The most heavy task in programming is not about building application, but it’s about maintain them and if you wrote something you can’t understand, then you will suffer for the rest of your life.
    1. In the article, "The New Normative: Queer Politics in The Outs," author John Sherman, a freelance writer from Brooklyn, implores reader's to give credit to show's casually- revolutionary representation of queer characters. Sherman indicates to reader's that this is a rarely great representation for its time (2012) because it gives gay characters a non-stereotypical story line. It allows it's characters to be people who just happen to be gay. In just the pilot episode, it's not hard to see this truth. With the first four queer male characters being introduced, they all have different characteristics, priorities, and dynamics with eachother that don't center around their gayness. This gives a depth to the queer character being represented without relying on the fact that their gay to do so. I think that the positive reaction to this show bodes very well for the style of queer representation being presented and will hopefully inspire more writing and content making of this kind which non-chalently gives a voice gay to story lines in a relatable- human way instead of a stereotypical and tokenising way.

      I believe that Shitt's Creek also does this fairly well. Although I've only seen a couple episodes myself- I saw the character of David as a complete person and story line not defined by his gayness or partner choices although it is an obvious part of his identity.

    1. The rigidness and immobility of the note book pages, based on the papern stamp andimmobility of the individual notes, prevents quick and time-saving retrieval and applicationof the content and therefore proves the note book process to be inappropriate. The only tworeasons that this process is still commonly found in the studies of many is that firstly they donot know any better, and that secondly a total immersion into a very specialized field ofscientific research often makes information retrieval easier if not unnecessary.

      Just like Heyde indicated about the slip box note taking system with respect to traditional notebook based systems in 1931, one of the reasons we still aren't broadly using Heyde's system is that we "do not know any better". This is compounded with the fact that the computer revolution makes information retrieval much easier than it had been before. However there is such an information glut and limitations to search, particularly if it's stored in multiple places, that it may be advisable to go back to some of these older, well-tried methods.

      Link to ideas of "single source" of notes as opposed to multiple storage locations as is seen in social media spaces in the 2010-2020s.

    1. When contracting with vendors that support open source, ensure that they commit to support future development of the underlying system and contribute their developments back to the community.

      Use contracting to align vendor values with library values

      Put in place agreements with open source support vendors that ensures a long-term commitment to the project by contributing spec development back to the community.

    1. In a recent example, Stable Diffusion, an open source AI system that generates images from text prompts, was released with a license prohibiting certain types of content. But it quickly found an audience within communities that use such AI tools to create pornographic deepfakes of celebrities.

      This is a big question, whether use restrictions, which are becoming prolific (RAIL license, for example), can be enforced. If not, and that's a big if, it might create a situation of "responsibility washing" - licensors can argue they did all that's possible to curb harmful uses, and these will continue to happen in a gray / dark zone

  7. Aug 2022
    1. This describes one of the most pleasing hacks I've ever come across. I just now tracked it down and added it to my bookmarks. (Not sure why it wasn't already there.)

      You could also conceive of going one step further. When your app (doesn't actually have to be a game, though admittedly it's much easier for you if it is) is compiled with tweak.h, it gives it the power to paint the source file on the screen—so you don't actually have to switch over to your text editor to save it, etc. Suppose you want to provide custom inputs like Bret Victor-style sliders for numeric values. You could edit it in your text editor, or you could derp around with it in-app. Tweaking the value in-app should of course both update it wrt the app runtime but also still write the file to disk, too, so if live reloading is turned on in your text editor, whatever changes you make inside the live process image gets synced out.

  8. Jul 2022
    1. With practice, your SourceNotes will become more like data and your Points moreanalytical.

      This distinguishing factor is a more useful one than those in other systems.


      Compare this with the idea of Beatrice Webb's "analytic notes" versus "synthetic notes" or "scientific notes" which she describes in My Apprentice (1926).

      see: - https://hypothes.is/a/Fb3Y4Au1Ee2p_sdveWOJKw - https://hypothes.is/a/WGPrOAoOEe2WJV9yx2SVZg - https://hypothes.is/a/2gdRwgoMEe2mdccJDX6zTw

      Web considers "analytic note taking" to be the raw data collection and arrangement (in the same vein of creating databases in the computer science space, which didn't exist when she did her work) upon which historical work is based.

      She views "synthetic notes" as observations of behaviours and writings which probably more closely resembles the idea of "literature notes" (Ahrens) or "source notes" (Allosso). Some of the difference is that she's viewing her notes as a tool for her particular work (sociology) rather than as a broader enterprise which might be used in all fields.

      Webb's synthetic notes are also likely bound up in her idea of Herbert Spencer's "synthetic philosophy" of thinking, which may require some more reading of these sections on my part to better distinguish her specific meaning.


      Webb didn't seem to have a version of "permanent notes" in her conceptualization. Perhaps this is an indication that the evolution of the note really only occurred as it was placed into published writing. This may potentially preclude the reuse of the evolved ideas unless they are separately re-subsumed into one's note collection.

      Ahrens' conceptualization of the zettelkasten has all the writing, revision, and evolution work occurring in the slip box itself so it's always available and reusable. Many modern note taking and writing systems would seem to elide this part. (Is this true in practice? Can we provide examples?)

  9. www.bookstackapp.com www.bookstackapp.com
    1. https://twinery.org/

      Twine is an open-source tool for telling interactive, nonlinear stories.

      You don’t need to write any code to create a simple story with Twine, but you can extend your stories with variables, conditional logic, images, CSS, and JavaScript when you're ready.

      Twine publishes directly to HTML, so you can post your work nearly anywhere. Anything you create with it is completely free to use any way you like, including for commercial purposes.


      Heard referenced in Reclaim Hosting community call as a method for doing "clue boards".


      Could twinery.org be used as a way to host/display one's linked zettelkasten or note card collection?

    1. Dec 13, 2021 — I want to talk about how open source has in the most cases, been turned into exploitation by the biggest organisations in the world.exploiting meaningwhat is an exploit in computer securityit exploit definition owaspexploit vs vulnerabilityexploit in cyber security exampletypes of exploitsPeople also search for
  10. Jun 2022
    1. Therefore, according to Forward and Hoyt [16], the criterion to evaluate the effectiveness of a de-orbit technique is not just whether it reduces orbital lifetime compared to atmospheric drag decay, but whether it reduces the product of orbital lifetime and collision cross-sectional area of the spacecraft, namely the ATP. As a matter of fact, Forward and Hoyt also demonstrated that the Terminator TetherTM can significantly reduce the ATP value for most LEO orbit

      good source for the same comment

  11. May 2022
    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.

  12. Apr 2022
    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. 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)

  13. 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

  14. rom-rb.org rom-rb.org
  15. Feb 2022
    1. “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.

    2. 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. 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)

  16. Jan 2022

    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

  17. Dec 2021
    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?
  18. Nov 2021
  19. Oct 2021
  20. Sep 2021

    Tags

    Annotators

  21. 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.”

  22. Jul 2021
    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.

  23. 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...

  24. May 2021
  25. Apr 2021
    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.

  26. Mar 2021
    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).
    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.
    1. 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. 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