184 Matching Annotations
  1. Last 7 days
  2. Apr 2021
  3. Mar 2021
    1. his environment of uncontrolled information is not all bliss, however. Some critics point out that the same giant media companies that dominated the older forms of media produce much of the content available on the internet.

      Tada! And major companies also own most of the infrastructure on which the internet runs.

  4. Feb 2021
  5. Jan 2021
    1. I started using Cronicle a few weeks ago and really like it. Runs on a server... https://github.com/jhuckaby/Cronicle

      This also ticks a lot of my desired features.

      Really easy to set up if you already have node ready to go.

      UI is very slick and feels right to me out of the box.

      Multi-server support.

      Jobs can be assigned to categories. A given category can have max concurrent processes running at the same time (so run 1 backup task a time, even though 5 tasks are scheduled within the same time period). Individual tasks can also be set to be singleton or configurable max concurrency.

      Supports configurable retry (number of attempts, delay between).

      Supports optional catchup runs if runs are missed or queued runs.

      Supports killing and erroring out if timeouts or resource limits are hit.

      Time from download to first job setup... 2 minutes? Very intuitive UI.

      Has management API, not clear if it has an existing good CLI interface.

      Also supports setting up users to be able to run pre-defined scripts and see output.

      Need to figure out how to back-up and restore jobs.

    2. RUNDECK

      Very quick impression is this ticks a lot of my desired features.

      I'm not wild about the community edition default dashboard - I'd rather a more high level view of everything configured and its statuses.

      UI is clunky when compared to Cronicle. Lots of steps to get from setting it up to actually running something. No quick click from a run task to its log output. No good resources/stats view that I found.

      Like the fact it keeps track of logs, runtime (and can alert if runtime deviates from normal), gives you an estimated time to complete, lets you run on a schedule and/or manually.

      Like the fact it supports farming tasks off through SSH or other, or running them locally. Can auto-discover nodes using a script you provide (e.g. query AWS nodes) or using static config.

      Really interested in the multi-user capabilities. This may solve a problem I didn't really know I had at work (giving a semi-technical person access to kick off jobs or monitor them before asking me).

    3. Running all that manually (more than 100 scripts across all devices) is an awful job for a human. I want to set them up once and more or less forget about it, only checking now and then.

      My ideals for all of my regular processes and servers:

      • Centralized configuration and control - I want to go into a folder and configure everything I'm running everywhere.
      • Configuration file has the steps needed to set up from scratch - so I can just back up the configuration and data folders and not worry about backing up the programs.
      • Control multiple machines from the central location. Dictate where tasks can run.
      • [nice to have] Allow certain tasks to running externally, e.g. in AWS ECS or Lambda or similar
      • Command-line access for management (web is great for monitoring)
      • Flexible scheduling (from strict every minute to ~daily)
      • Support for daemons, psuedo-daemons (just run repeatedly with small delays), and periodic tasks.
      • Smart alerts - some processes can fail occasionally, but needs to run at least once per day - some processes should never fail. A repeating inaccurate alert is usually just as bad as no alert at all.
      • Error code respect (configurable)
      • Logs - store the program output, organize it, keep it probably in a date-based structure
      • Health checks - if it's a web server, is it still responding to requests? Has it logged something recently? Touched a database file? If not, it's probably dead.
      • Alerts support in Telegram and email
      • Monitor details about the run - how long did it take? How much CPU did it use? Has it gotten slower over time?
      • Dashboard - top-level stats, browse detailed run stats and logs

      So much of the configuration/control stuff screams containers, so more and more I'm using Docker for my scripts, even simpler ones.

      I'm pretty sure a lot of this is accomplished by existing Docker orchestration tools. Been delaying that rabbit hole for a long time.

      I think the key thing that makes this not just a "cron" problem for me, is I want something that monitors and manages both itself and the tasks I want to run, including creating/setting up if not already. I also want to ideally focus my mental energy into a single controller that handles my "keep this running" things all together, be they servers or infrequent tasks.

      Doesn't have to be a single project. Might be multiple pieces glued together somehow.

  6. Dec 2020
  7. Nov 2020
    1. The beauty of the bicycle infrastructure network in Copenhagen is the uniform design of the infrastructure. There are, by and large, four types of infrastructure - all represented in this graphic. Based on the speed limit for cars, you select the appropriate style of infrastructure and off you go.
      • 10-30 kph (under 18 mph): no separation necessary
      • 30-50 kph (18-31 mph): painted bike lanes to the right of the parking lane
      • 50-70 kph (31-43 mph): curb-separated bike lanes to the right of the parking lane
      • 70+ kph (over 43 mph): full median-separated bike lanes
  8. Oct 2020
    1. The default groups, that we talked about before, like domain users and domain admins are security groups. They're used to grant or deny access to IT resources.
    2. A distribution group, is only designed to group accounts and contacts for email communication. You can't use distribution groups for assigning permission to resources.
    1. The service that hosts copies of the Active Directory database are called domain controllers, or DCs
      • Hosts a replica of the Active Directory database and group policy objects.

      • Serve as DNS servers to provide name resolution and service discovery to clients.

      • Provides central authentication through a network security protocol called Kerberos

      • Decides whether or not clients have access to shared resources like file systems and printers

    2. Active Directory has been used to centrally manage networks of computers
      • A native service for Microsoft Windows
      • Knows how to speak LDAP protocol and can interoperate with Linux, OS-X and other non-windows hosts
      • Central repository of Group Policy Objects (GPOs)
    3. One of the most common methods for this authentication is using Kerberos.
      • Kerberos is a network authentication protocol that is used to authenticate user identity, secure the transfer of user credentials, and more
    4. role-based access control, or RBAC
      • Is an approach to restricting system access to authorized users.

      • Controlling access to resources isn't all you can do. You can also centralize configuration management.

        You wouldn't want to setup printers or software for each and every user.

    1. Useful mass transportation doesn’t suddenly appear. It is carefully nurtured from a tiny seedling of a good idea to a fully-formed organism that breathes life into a city. It is a process that takes time and effort and patience as well as money.

      Could sub out mass transportation with open scholarly infrastructure! ... "Useful mass transportation doesn’t suddenly appear. It is carefully nurtured from a tiny seedling of a good idea to a fully-formed organism that breathes life into a city. It is a process that takes time and effort and patience as well as money."

  9. Sep 2020
  10. Aug 2020
  11. Jul 2020
  12. Jun 2020
  13. www.tumblr.com www.tumblr.com
    1. Opting out of ads or paying not to have ads will be the likely initial way that we'll all move towards the inevitable truism of platform business, which is that ad-only models aren't predominant for a reason.

      I personally wouldn't bother to pay. I'll just block the ads or get the content / tool someplace else. Abundant alternative options....

    1. Cities are cradles. Nests made of carefully knitted infrastructure holding us up. When a city's infrastructure is exposed - a hole in the pavement, arteries under sun - we're reminded of our dependence on a deeper physical reality and our implicit vulnerability as a result. We're reminded that our cities are engineered and technical places as much as they are natural expressions of the Human and the Social, whose buildings echo ancient grouping of people at work, play, or home. What we expect from infrastructure is that it works, because when it doesn't , it isn't. We want infrastructure to seamlessly integrate with the existing world — in the ground like water rather than an accessory above. After all, infrastructure is here to support us; an expression of what may be our most endemic myth, that the world is here for us. But with every receding seam, from cable to code, comes a techno-political risk. Without edges we cannot know where we are and nor through whom we speak.

      "our most endemic myth, that the world is here for us."

      I thought about the article about how we have a bad understanding of mapping the exact placements of utilities under manhattan.

    1. But that is changing.

      who would've thought we'd cycle back to being at war and distance

      as divisive as ever (?)

      how technology is accused of bringing the faraway closer but distancing the nearby

    1. Media is supported by ads, ads want clicks, clicks come from outrage, so therefore – the media’s goal has shifted to create as much outrage as possible

      our social and media infrastructure are outrage machines, icentivised

  14. May 2020
  15. Apr 2020
    1. Establish standard models and criteria for funding alternatives to “pay for access” or “pay to publish” (transactional funding models) so that libraries can more easily invest in diverse content and services, including open infrastructure

      Yes!

    1. pas forcément rationalisables

      la nature dynamique du phénomène numérique le rend justement non cristallisable; son actualisation permanente (donc toujours virtuel, jamais tout à fait actuel) en fait un structure «pas forcément rationalisable»

  16. Feb 2020
  17. Jan 2020
    1. Between 2011 and 2013, china used 50% more cement than the United States in the 20th century.Of the world’s 100 highest bridges, 81 are in China, including some unfinished ones.

      China's infrastructure is growing amazingly fast

  18. Dec 2019
  • Tags

    Annotators

    URL

  • Tags

    Annotators

    URL

  • Tags

    Annotators

    URL

  • Nov 2019
    1. From Peg Cheechi, an instructional designer at Rush University: informing faculty members about the advantages of working with experts in course design.

      The Chronicle of Higher Education is a website and newspaper informing students and faculty of college affairs and news.

      Rating: 9/10

  • Oct 2019
  • Jul 2019
  • Jun 2019
    1. What are the risks in digitizing these materials outside the library? Are there possibilities of this collection not being well integrated with other holdings? Did you collaborate with metadata experts?

    1. On one hand, DH pedagogy can no longer be meaningfully said to be entirely in service of or secondary to the research project.

      !!!

      Yes! How does DH end up caught in the trap of focusing solely on research? I'm loving the notion of more attention to DH pedagogy separate from the research discussion

  • May 2019
    1. By “Infrastructure” we mean

      ​The definition of "open infrastructure" (or the software component of open infrastructure) should include an explicit requirement for open-source code.​ Even an explicit recommendation short of a requirement would be better than the current definition, which is entirely silent the value of opening the code. The Elsevier acquisition of bepress (to use one example among many) would have been much less harmful to the community if the code had been open and user institutions could hold on to the platform, fork it if they wanted, take it in their own direction, and continue using it without becoming Elsevier customers.

    1. Hey all, this is Michael – I am writing to test out this platform and to begin to build something in this document. I realize it’s slightly obscure at the moment how this pad will come to be useful during Publishing Sphere – I believe this will be come clearer in the coming days as we begin to roll out some of the sites, info, and programming for the gathering.

      Danny and I will be meeting tomorrow (Thursday, the 2nd of May) to discuss the publishing apparatus we have been discussing, and will begin to introduce it to the group as something to work off, develop in new directions, or to create publication systems concurrent to this one. Once we have this initial formulation mapped out, I’ll let him introduce it to you all to begin to discuss and edit.

      Shortly, I’ll post some info that I think is relevant to the gathering more generally, and then some additional information about you all so that you might begin to become more aware of the other members of the group. I’m truly looking forward to witnessing how you might all begin to work with one another.

      More soonest~

      M.

  • Apr 2019
    1. It's the act of creating the curriculum in a particular form that will be useful to Minnesota 3rd grade teachers that generates revenue for me, and not the content which is created.

      This is the clearest expression for me, of what David Wiley might be talking about when he calls OER infrastructure.

    1. chemistry lab simulation is the “wrong” content if students are supposed to be learning world history

      Isn't this exactly why it isn't helpful to think of content as infrastructure?

    2. Apache is a piece of software that meets the need of its developers

      Okay, so the open source software analogy has deep roots. But I still (looking at this a dozen years later) think this analogy is flawed. Apache was a webserver (infrastructure) that could serve any page (content). I think the proper analog to Apache in OER is a platform or app (Pressbooks, Hypothes.is), not any particular Pressbook or annotation.

    3. The example of the Linux kernel shows that this is completely possible.

      I think the Linux kernel analogy breaks down even more in considering "the other 93%" of educational content, which David has already identified here as more niche, less kernelesque, than content for core courses. Seems to me, the more specialized and rarely used something is — either in digital technology or in content — the less likely it is going to be the focus of widespread, shared activity.

      If commercial publishers could rely on OER content for core classes and generate revenue from wrapping them in additional services (as David describes here), what is their incentive to devote any resources to labor-intensive, niche content that would have far lower revenue margins?

    4. Traditional textbook content like words and images are just like the operating system kernel – kind of boring.

      This is the part of the argument here I don't find convincing. I'm not sure we can liken content — yes even "traditional textbook content" — to OS kernels or roads as a kind of "boring" infrastructure. Content is an expression of knowledges/understandings right? If anything, content seems more like the "interesting" part that relies on the kernels/roads.

      Yet I am interested in the idea of thinking of content as PUBLIC infrastructure, in the sense that like roads, we have common interests in securing public sources for the resources necessary to produce and maintain educational content.