27 Matching Annotations
  1. Jan 2026
    1. commented here on h. "Wrt permanence, my own h. bookmarks and annotations flow directly into my local notes, through the h. API.

      The h. software is open sourced, so theoretically one would be able to run their own instance of it. Except for the social function of it. Like you I follow Chris Aldrich annotations feed (which is how I ended up here), and several others. When others bookmark the same stuff I do but use very different tags for it, is where it gets interesting. Like years ago in the del.icio.us bookmarking service, the difference in tags signifies a social or sectoral distance. Basically you're finding a sliver of overlap between two different mindsets / contexts / interests. I then can add those people to the feeds I follow."

    1. The year I built 110 tools # I started my tools.simonwillison.net site last year as a single location for my growing collection of vibe-coded / AI-assisted HTML+JavaScript tools. I wrote several longer pieces about this throughout the year: Here’s how I use LLMs to help me write code Adding AI-generated descriptions to my tools collection Building a tool to copy-paste share terminal sessions using Claude Code for web Useful patterns for building HTML tools—my favourite post of the bunch. The new browse all by month page shows I built 110 of these in 2025!

      Simon Willison vibe coded over 100 personal tools in 2025. This chimes with what Frank and Martijn were suggesting. Up above he also indicates that it is something that became possible at this scale only in 2025 too.

  2. Dec 2025
    1. This way I made a lot of existing apps that I happily paid for absolutely obsolete. The stuff that I created was simply doing more of what I wished for, building on the ideas of all the apps I have seen before. A next iteration, but just for me.

      Making personal tools makes generic ones obsolete. Yet, the generic ones do serve as starting point for inspiration and design choices. Personal iterations on top of what went before.

    2. So far I have built six different apps this way in the past few weeks. A personal transit tracker. A task manager tailored to my exact workflow. Small tools that solve specific problems in my life.

      [[Martijn Aslander]] has made several personal tools for his iphone.

    1. The cost goes beyond simple inefficiency and becomes a mountain of invisible labor, usually absorbed by the most junior person in the room or whoever has the misfortune of being labeled as “good with computers.” It becomes a drag on every collaboration, the friction in every workflow, the meetings that take an extra ten minutes while someone (who is often paid twice the average salary of the other people in the meeting) figures out why they can’t access the shared folder the rest of us have been using for months. It’s the quiet erosion of patience and goodwill among people who are constantly expected to know and fix things that shouldn’t need fixing in the first place.

      The cost of lack of skills is not just in the individual knowledge worker, it gets externalised to others to fix it, or multiplied in groups waiting on you to get something working. The incompetence spreads out.

    2. The number of professionals in journalism, media, communications, and academia who still don’t understand how to use the very tools they depend on for their livelihood is, frankly, staggering

      knowledge workers are the largest group of people who don't know their own tools. Vgl [[Kenniswerk is ambacht 20040924200250]]

    1. PKM gaat over ideeën en kennis. Ik beweeg ook mensen. Ik organiseer projecten, bouw gemeenschappen, verbind organisaties. Daarvoor heb ik iets nodig dat mijn hele werkelijkheid verbindt: mensen, locaties, gebeurtenissen, transacties, kansen, ideeën en projecten.

      Key statement. PKM is about ideas and knowledge (at least to himself, my PKM combines that with practice) "I need something that combines my entire personal reality" Ppl, locations, events, transactions, opportunities, ideas, projects etc.

    2. De technologie van ThetaOS en de code zijn op zich niet heel complex. Maar wat telt is het inzicht dat ik ermee kan vergaren en ontsluiten. Je hebt al informatie over je leven. Die informatie zit verspreid over tientallen apps die niet met elkaar praten: vele kopieën van dezelfde naam, in WhatsApp, mail, agenda's of banktransacties. Net als adressen, locaties, namen van organisaties of projecten en ga zo maar door.

      The tech is straigthforward: sqlite, node.js and html/css. The value is the combination of different sources into personal tool.

  3. Oct 2024
    1. For a long time, I thought of HTML as a tool for publishing on the web, a way to create websites that other people can look at. But all these websites I’m creating are my local, personal archives – just for me. I’m surprised it took me this long to realise HTML isn’t just for sharing on the web.

      Yes. I use lots of small local html/php pages. Also webforms to search websites elsewhere, without going there. I had local pages to browse local image files in the 90s. I started writing html by hand in '93 and still do for local stuff. I do use a local on-device webserver though, as I include php.

    2. https://web.archive.org/web/20241017043750/https://alexwlchan.net/2024/static-websites/

      I like this idea of having static html as page to explore folders, I had that in the 90s to better search for image files. Author offers no clues as to how he uses the affordance it provides though, in terms of 'showing the metadata' they care for and the little bits of extra functionality. And I wonder about the effort involved when adding new files. Presumably new files are added manually too, otherwise it's not 'static html'. Stores files by year, type and first letter of file name. That makes no immediate sense to me in terms of finding things back. Then again I never understood why you would have folders for file types. It's like sorting items on the type of box it came in. Good example though of making your computer your own.

  4. Jul 2024
  5. Feb 2024
  6. May 2023
    1. Making these models smaller and more specialised would also allow us to run them on local devices instead of relying on access via large corporations.

      this. Vgl [[CPUs, GPUs, and Now AI Chips]] hardware with ai on them. Vgl [[Everymans Allemans AI 20190807141523]]

    2. One alternate approach is to start with our own curated datasets we trust. These could be repositories of published scientific papers, our own personal notes, or public databases like Wikipedia.We can then run many small specialised model tasks over them.

      Yes, if I could run my own notes of 3 decades or so on an LLM locally (where it doesn't feed the general model), that I would do instantly.

    3. We will have to design this very carefully, or it'll give a whole new meaning to filter bubbles.

      Not just bubble, it will be the FB timeline. Key here is agency, and design for human biases. A model is likely much better than I to manage the diversity of sources for me, if I give it a starting point myself, or to see which outliers to include etc. Again I think it also means moving away from single artefacts. Often I'm not interested in what everyone is saying about X, but am interested in who is talking about X. Patterns not singular artefacts. See [[Mijn ideale feedreader 20180703063626]]

    4. I expect these to be baked into browsers or at the OS level.These specialised models will help us identify generated content (if possible), debunk claims, flag misinformation, hunt down sources for us, curate and suggest content, and ideally solve our discovery and search problems.

      Appleton suggests agents to fact check / filter / summarise / curate and suggest (those last two are more personal than the others, which are the grunt work of infostrats) would become part of your browser. Only if I can myself strongly influence what it does (otherwise it is the FB timeline all over again!)

      If these models become part of the browser, do we still need the browser as a metaphor for a window on the web, or surfing the net? Why wouldn't those models come up with whatever they grabbed from the web/net/darkweb in the right spot in my own infostrats? The browser is itself not a part of my infostrats, it's the starting point of it, the viewer on the raw material. Whatever I keep from browsing is when PKM starts. When the model filters / curates why not put that in the right spots for me to start working with it / on it / processing it? The model not as part of the browser, but doing the actual browsing, an active agent going out there to flag patterns of interest (based on my prefs/current issues etc) and organising it for me for my next steps? [[Individuele software agents 20200402151419]]

    5. Those were all a bit negative but there is some hope in this future.We can certainly fight fire with fire.I think it’s reasonable to assume we’ll each have a set of personal language models helping us filter and manage information on the web

      Yes, agency at the edges. Ppl running their own agents. Have your agents talk to my agents to arrange a meeting etc. That actually frees up time. Have my agent check out the context and background of a text to judge whether it's a human author or not etc. [[Persoonlijke algoritmes als agents 20180417200200]] [[Individuele software agents 20200402151419]]

    6. But some people will realise they shouldn’t be letting language models literally write words for them. Instead, they'll strategically use them as part of their process to become even better writers.They'll integrate them by using them as sounding boards while developing ideas, research helpers, organisers, debate partners, and Socratic questioners.

      This hints towards prompt-engineering, and the role of prompts in human interaction itself [[Prompting skill in conversation and AI chat 20230301120740]]

      High Q use of generative AI will be about where in a creative / work process you employ to what purpose. Not in accepting the current face presented to us in e.g. chatGPT: give me an input and I'll give you an output. This in turn requires an understanding of one's own creative work processes, and where tools can help reduce friction (and where the friction is the cognitive actual work and must not be taken out)

  7. Mar 2023
  8. Jan 2023
    1. I don't presently have plans to expand this into an annotation extension, as I believe that purpose is served by Hypothesis. For now, I see this extension as a useful way for me to save highlights, share specific pieces of information on my website, and enable other people to do the same.

      I wonder if it uses the W3C recommendation for highlighting and annotation though? Which would allow it to interact with other highlighting/annotation results.

      To me highlighting is annotation, though a leightweight form, as the decision to highlight is interacting with the text in a meaningful way. And the pop up box actually says Annotation right there in the screenshot, so I don't fully grasp what distinction James is making here.