31 Matching Annotations
  1. Apr 2024
    1. but the process of identifying trustworthy mailers and notifying them does not scale well to large numbers of small mailers

      bias against small players?

  2. Nov 2023
    1. Ausführlicher Kommentar zu den 2,4 Billionen (Tausend Milliarden, im Artikel falsch übersetzt) Dollar, die laut dem COP27-Bericht von 2022 erforderlich sind, um Klimaschutz und -Anpassung in den Ländern des globalen Südens (außer China) zu finanzieren. Der auf Konsens ausgerichtete COP-Prozess sei außerstande, die nötigen Entscheidungen zu treffen. Der Betrag entspricht grob den aktuellen weltweiten Militärausgaben. https://www.repubblica.it/commenti/2023/11/19/news/cambiamenti_climatici_spesa_annua-420689085/?ref=RHRT-BG-I279994148-P4-S3-T1

  3. Oct 2023
  4. Sep 2023
    1. folgezettel pushes the note maker toward making at least one connection at the time of import.

      There is a difference between the sorts of links one might make when placing an idea into an (analog) zettelkasten. A folgezettel link is more valuable than a simple tag/category link because it places an idea into a more specific neighborhood than any handful of tags. This is one of the benefits of a Luhmann-artig ZK system over a more traditional commonplace one, particularly when the work is done up front instead of being punted to a later time.

      For those with a 1A2B3Z linking system (versus a pure decimal system), it may be more difficult to insert a card before other cards rather than after them because of the potential gymnastics of numbering and the natural tendency to put things into a continuing linear order.

      See also: - https://hypothes.is/a/ToqCPq1bEe2Q0b88j4whwQ - https://hyp.is/WtB2AqmlEe2wvCsB5ZyL5A/docdrop.org/download_annotation_doc/Introduction-to-Luhmanns-Zette---Ludecke-Daniel-h4nh8.pdf

  5. Aug 2023
    1. it is technically impossible to feed the entire population of the planet with organic produce.
      • for: never say never, scaling organic production
      • comment
        • claims true at one time in history, may not be true for a later time as progress develops new solutions that make yesterday's impossible, today's possible.
    1. Last fall, I spent several days in New York City, during which time I visited a home owned by a group of pacifist Christians that lives from a common purse—meaning the members do not have privately held property but share their property and money. Their simple life and shared finances allow their schedules to be more flexible, making for a thicker immediate community and greater generosity to neighbors, as well as a richer life of prayer and private devotion to God, all supported by a deep commitment to their church.This is, admittedly, an extreme example. But this community was thriving not because it found ways to scale down what it asked of its members but because it found a way to scale up what they provided to one another.

      fascinating example of anti toxic capitalism...

  6. Jun 2023
    1. I’ll be speaking with and writing about people working on some of the tools and communities that I think help point ways forward—and with people who’ve built fruitful, immediately useful theories and practices

      Sounds interesting. Add to feeds. Wrt [[Invisible hand of networks 20180616115141]] scaling comes from moving sideways, repetition and replication. And that takes gathering and sharing (through the network) of examples. Vgl [[OurData.eu Open Data Voorbeelden 20090720142847]] but for civic tech, socsoft? What would it look like?

  7. Mar 2023
    1. Abb. 9 Im Normalfall erarbeitete man jedoch eine detaillierte interne Feinsortierung des Belegmaterials häufiger Wörter. Naturgemäß hätte jede Dimension der Analyse (chronologisch, grammatisch, semantisch, graphisch) die Grundlage einer eigenen Sortierordnung bilden können.

      Alternate sort orders for the slips for the Wb include chronological, grammatical, semantic, and graphic, but for teasing out the meanings the original sort order was sufficient. Certainly other sort orders may reveal additional subtleties.

  8. Feb 2023
    1. Folgezettel

      Do folgezettel in combination with an index help to prevent over-indexing behaviors? Or the scaling problem of categorization in a personal knowledge management space?

      Where do subject headings within a zettelkasten dovetail with the index? Where do they help relieve the idea of heavy indexing or tagging? How are the neighborhoods of ideas involved in keeping a sense of closeness while still allowing density of ideas and information?

      Having digital search views into small portions of neighborhoods like gxabbo suggested can be a fantastic affordance. see: https://hypothes.is/a/W2vqGLYxEe2qredYNyNu1A

      For example, consider an anthropology student who intends to spend a lifetime in the subject and its many sub-areas. If they begin smartly tagging things with anthropology as they start, eventually the value of the category, any tags, or ideas within their index will eventually grow without bound to the point that the meaning or value as a search affordance within their zettelkasten (digital or analog) will be utterly useless. Let's say they fix part of the issue by sub-categorizing pieces into cultural anthropology, biological anthropology, linguistic anthropology, archaeology, etc. This problem is fine while they're in undergraduate or graduate school for a bit, but eventually as they specialize, these areas too will become overwhelming in terms of search and the search results. This problem can continue ad-infinitum for areas and sub areas. So how can one solve it?

      Is a living and concatenating index the solution? The index can have anthropology with sub-areas listed with pointers to the beginnings of threads of thought in these areas which will eventually create neighborhoods of these related ideas.

      The solution is far easier when the ideas are done top-down after-the-fact like in the Dewey Decimal System when the broad areas are preknown and pre-delineated. But in a Luhmann-esque zettelkasten, things grow from the bottom up and thus present different difficulties from a scaling up perspective.

      How do we classify first, second, and third order effects which emerge out of the complexity of a zettelkasten? - Sparse indexing can be a useful long term affordance in the second or third order space. - Combinatorial creativity and ideas of serendipity emerge out of at least the third order. - Using ZK for writing is a second order affordance - Storage is a first order affordance - Memory is a first order affordance (related to storage) - Productivity is a second+ order (because solely spending the time to save and store ideas is a drag at the first order and doesn't show value until retrieval at a later date). - Poor organization can be non-affordance or deterrent which results in a scrap heap - lack of a reason why can be a non-affordance or deterrence as well - cross reference this list and continue on with other pieces and affordances

  9. Jan 2023
  10. Dec 2022
    1. Isaac and I uh with another colleague we did a little bit of work trying to look at what would the Swedish policy or the UK policy indeed look like if it was carried out globally and it would look at something like two and a half degrees Centigrade of warming if 00:31:58 not more

      !- key point : Sweden's net zero plan scaled globally - would result in a 2.5 deg C or greater world

  11. Sep 2021
  12. Apr 2021
  13. Mar 2021
  14. Jan 2021
    1. Scale, inevitably leads to power-law distributed outcomes, leading to the inevitable concentration of talent and resources among a few investigators pursuing a few lines of inquiry, and their pale second-rate imitators. Through this mechanism science at scale reinforces (and in fact, under sufficient political capture imposes) consensus, further annihilating the possibility of the necessary revolutionary synthesis of ideas.

      The solution to any sort of global leaderboard thing - like Mendeley most read or most cited - is to break it up into local communities - most read among your friends or most cited within only the outer leaves of the topic tree.

  15. Dec 2020
  16. Aug 2020
  17. Jun 2020
  18. May 2020
    1. WhyGeneral infrastructure simply takes time to build. You have to carefully design interfaces, write documentation and tests, and make sure that your systems will handle load. All of that is rival with experimentation, and not just because it takes time to build: it also makes the system much more rigid.Once you have lots of users with lots of use cases, it’s more difficult to change anything or to pursue radical experiments. You’ve got to make sure you don’t break things for people or else carefully communicate and manage change.Those same varied users simply consume a great deal of time day-to-day: a fault which occurs for 1% of people will present no real problem in a small prototype, but it’ll be high-priority when you have 100k users.Once this playbook becomes the primary goal, your incentives change: your goal will naturally become making the graphs go up, rather than answering fundamental questions about your system.

      The reason the conceptual architecture tends to freeze is because there is a tradeoff between a large user base and the ability to run radical experiments. If you've got a lot of users, there will always be a critical mass of complaints when the experiment blows up.

      Secondly, it takes a lot of time to scale up. This is time that you cannot spend experimenting.

      Andy here is basically advocating remaining in Explore mode a little bit longer than is usually recommended. Doing so will increase your chances of climbing the highest peak during the Exploit mode.

    2. This is obviously a powerful playbook, but it should be deployed with careful timing because it tends to freeze the conceptual architecture of the system.

      One a prototype gains some traction, conventional Silicon Valley wisdom says to scale it up. This, according to Andy Matuschak has certain disadvantages. The main drawback is that it tends to freeze the conceptual architecture of the system.

  19. Apr 2020
    1. “scaling out is the only cost-effective thing”, but plenty of successful companies managed to scale up with a handful of large machines or VMs
    2. Scaling is hard if you try do it yourself, so absolutely don’t try do it yourself. Use vendor provided, cloud abstractions like Google App Engine, Azure Web Apps or AWS Lambda with autoscaling support enabled if you can possibly avoid it.

      Scaling shall be done with cloud abstractions

  20. Mar 2020
    1. I would like to make an appeal to core developers: all design decisions involving involuntary session creation MUST be made with a great caution. In case of a high-load project, avoiding to create a session for non-authenticated users is a vital strategy with a critical influence on application performance. It doesn't really make a big difference, whether you use a database backend, or Redis, or whatever else; eventually, your load would be high enough, and scaling further would not help anymore, so that either network access to the session backend or its “INSERT” performance would become a bottleneck. In my case, it's an application with 20-25 ms response time under a 20000-30000 RPM load. Having to create a session for an each session-less request would be critical enough to decide not to upgrade Django, or to fork and rewrite the corresponding components.
  21. Jul 2019
  22. Jun 2019
    1. However, this doesn’t mean that Min-Max scaling is not useful at all! A popular application is image processing, where pixel intensities have to be normalized to fit within a certain range (i.e., 0 to 255 for the RGB color range). Also, typical neural network algorithm require data that on a 0-1 scale.

      Use min-max scaling for image processing & neural networks.

  23. Mar 2019
    1. To solve the problem of ‘scaling up’ requires ‘scaling in’ –by this we mean developing the designs and infrastructure needed to support effective use of an innovation.

      On "scaling-in" rather than "scaling-up".

  24. Sep 2018
    1. As student numbers have increased, teaching has regressed for a variety of reasons to a greater focus on information transmission and less focus on questioning, exploration of ideas, presentation of alternative viewpoints, and the development of critical or original thinking. Yet these are the very skills needed by students in a knowledge-based society.

      Related to Vijay Kumar's iron triangle. You can't increase the number of students without sacrificing quality or increasing costs.

  25. Sep 2017
  26. Aug 2017
  27. Feb 2017