Text extraction. See Typescript Archive
09:07:58
09:07:58 From Jeff Miller Federation scrape discussion.
09:10:10 From Brian | Plugin | Count | |---------------|-------:| | paragraph | 43177| | markdown | 32509| | html | 19726| | pagefold | 10304| | graphviz | 6957| | image | 5645| | code | 5580| | reference | 4505| | video | 3358| | frame | 3312| | factory | 2732| | roster | 2640| | assets | 1717| | activity | 1689| | map | 1409| | transport | 547| | graph | 432| | mathjax | 362| | method | 289| | fivestar | 234| | plugmatic | 220| | search | 195| | audio | 180| | grep | 127| | data | 81| | zones | 72| | present | 72| | flagmatic | 66| | radar | 59| | chart | 53| | calculator | 43| | changes | 39| | calendar | 39| | rss | 32| | morseteacher | 32| | datalog | 25| | json | 22| | federatedWiki | 20| | register | 17| | slide | 15| | plugins | 14| | line | 13| | importer | 11| | chess | 11| | bikeshare | 10| | signature | 9| | shell | 9| | recycler | 9| | rollup | 8| | reduce | 8| | bytebeat | 8| | turtle | 7| | solo | 7| | pushpin | 7| | cytodemo | 7| | rostermatic | 6| | report | 6| | metamodel | 6| | scatter | 5| | force | 5| | cypher | 5| | wikish | 4| | microtalk | 4| | crazy | 4| | bars | 4| | tab | 3| | process-step | 3| | print | 3| | point | 3| | outline | 3| | tally | 2| | soundcloud | 2| | math | 2| | future | 2| | wsjt | 1| | txtzyme | 1| | turtle-wander | 1| | stats | 1| | popup | 1| | parse | 1| | logwatch | 1| | dotviz | 1| | detect | 1|
09:12:15 From Jeff Miller plugin survey results predict the impact of changing a plugin on the federation, based on its usage
09:14:26 From Jeff Miller "about this page" link to survey results, a little like the lineup diagram (Jeff: I have found the lineup diagram useful when demonstrating wiki to new people) <3 "are any of these paragraph item IDs used by other pages?"
09:15:56 From Jeff Miller another way of demonstrating wiki federation information sharing affordances -- SEARCH IDs
09:18:33
09:18:33 From Jeff Miller Brian imagines the structure of wiki as a set of nested containers -- a site, a page, a paragraph id -- this model may be helpful for reaggregating wiki content to publication output for different purposes and audiences -- extracting wiki content into papers, presentations, etc. with two-way links
09:19:53 From Jeff Miller Ward reflects that technologies are adopted most quickly when the Address an Existing Pain Point. For a free-textbook publisher, their biggest pain point is verifying the intellectual property status of any material. Ward's model for this case was to have an intake wiki managed by the IP team which attaches this information, and once vetted, can be used by any of the textbook authors, maintaining references to the source of that content.
09:21:31 From Jeff Miller Any challenge can be answered by a chain of attribution.
09:22:32 From Jeff Miller (Tableau's directed graph of "data quality" is a closely aligned structure to content source attribution - Jeff's experience there) "where did you get this number from?" "where is this number used for reporting and inference?" (fan-in, fan-out of quantitative reports)
09:24:23 From Jeff Miller "an artist's cottage" (personal wiki), "an artist's cottage courtyard, an artist's retreat" (federated wiki) Wikimedia Commons as an example of source attribution made easily accessible.
09:25:31 From Jeff Miller melting clock conference (Wikimedia Portland conference logo source) Dall-E as a tool for use by artists, judiciously?
09:28:28
09:28:28 From Brian The libcurl bug bounty was early "victum" of LLMs being used in not a great way. https://daniel.haxx.se/blog/2024/01/02/the-i-in-llm-stands-for-intelligence/ is one of the related articles.
09:28:34 From Jeff Miller (a discussion of how to manage the existence of LLM-generated content, especially where those LLMs might be trained on a body like Stack Overflow / Stack Exchange discussions, and Wikipedia) "the i in llm" a victim of sans-serif font confusion variable-width fonts should have stayed on paper. :)
09:30:12 From Jeff Miller positive use of LLM coding tools as a syntax assistant and small-idiom assistant
09:32:33 From Brian I heard, maybe it's a meme, that an new oven comes with an LLM recipe book and often suggests that you cook yourself or other things that are not suitable/useful for recipes...
09:32:33 From Jeff Miller Jeff and Ward relate a positive experience with Javascript syntax assistance and extension of small code structure when experimenting with generating map markers in a frame script.
09:34:43 From Jeff Miller (a discussion of doing small tasks in well-established languages, like "the idiom for reading a file from a URL reference") Reflections on Trusting Trust (as a relevant talk for LLM and for assisted code and library composition)
09:36:53 From Jeff Miller "This library protected the sharp edges of RabbitMQ from confusing developers who aren't expert; but if the library didn't change, but RabbitMQ has moved on... the LLM won't help us understand that point of difference."
09:38:11 From Jeff Miller (today's abstraction over the updated RabbitMQ would be different, so LLMs wouldn't know what the appropriate points of distinction can be) -Eric's story
09:39:18 From Jeff Miller looking under the lamp-post - things that folks are familiar with as problematic, versus things that people aren't familiar with, maybe things hitting dynamic limits that haven't been hit before
09:45:30
09:45:30 From Brian /s do those emails happen before or after the credit card entry...
09:48:55
09:48:55 From Jeff Miller "risk landscape" and "opportunity landscape" as concepts which draw attention to what to work on "whose budget does a system fix come out of?" as a question from Marc about general issues of how to get a fix to happen
09:50:56 From Jeff Miller "Does a learning cycle need to be completed, which isn't fully connected, in order to steer out of vulnerabilities?"
09:52:55 From Brian Is some portion of the company planning to exit in the next 2 years vs planning on staying there for the next 20?
09:53:20 From Jeff Miller Marc reflects on a pattern sometimes applied to fix cross-system problems, by funding them as a percentage of budget (a shared services budget)
09:54:34 From Jeff Miller Marc reflects: is the problem in coordination? (self-service for one team, so we don't have to coordinate with the other team; except that the system isn't sufficient to support this uncoordinated approach)
09:56:31 From Jeff Miller Marc brings in "System II" - the meta-system, how to coordinate and organize work within units of "System I" - people who write software, run marketing campaigns, etc. System II -- coordinate System I so that people don't step on one another's work.
09:57:38 From Jeff Miller System III (efficiency, management); System iV (strategy and opportunity)
09:59:10 From Jeff Miller I'm jumping out early because Sunday is a clash between Sunday Explorers and Ted Young's book club on The Programmer's Brain.
09:59:24 From Brian Bye Jeff, thank you for the notes .
09:59:37 From Jeff Miller save chat!