3,565 Matching Annotations
  1. Feb 2026
    1. Setting context length Setting a larger context length will increase the amount of memory required to run a model. Ensure you have enough VRAM available to increase the context length.

      This setting is in ollama desktop interface. Does it set it for the terminal too? Or are these two separate instances?

    2. Context length is the maximum number of tokens that the model has access to in memory. The default context length in Ollama is 4096 tokens. Tasks which require large context like web search, agents, and coding tools should be set to at least 64000 tokens.

      Default ollama context length is 4k. Recommended minimum for websearch, agents and coding tools (like Claude Code or Open code) is 64k. I've seen 128k recommendations for Claude Code

    1. Definities Volgens de Van Dale is soevereiniteit een synoniem van autonomie en zelfbestuur, maar de opstellers van een nieuw rapport zien dat toch anders. In hun optiek verwijst digitale autonomie naar het vermogen van de Rijksoverheid om onafhankelijk en zelfvoorzienend te opereren in het digitale domein. Een digitaal autonome overheid heeft controle over haar eigen digitale infrastructuren, systemen en gegevens zonder buitensporige afhankelijkheid van externe partijen, met name buitenlandse entiteiten. Digitale soevereiniteit gaat volgens de opstellers van het rapport nog een stap verder. Het verwijst naar de volledige onafhankelijkheid en de afdwingbare jurisdictie van de Rijksoverheid over haar digitale domein, zonder de mogelijkheid voor buitenlandse entiteiten om controle of invloed uit te oefenen.

      This is the definition of autonomy / sovereignty that MinBZK uses (and me). Source Strategische Verkenning Digitale Autonomie en de Rijksoverheid. Vgl Actieagenda Digitale Autonomie

  2. Jan 2026
    1. German initiative for digital autonomy / sovereignty, called Digital Independence Day, short DI Day (pronuncation d-day). Every 1st sunday of the month is a DI Day, where people are encouraged, and assisted, to switch to more privacy oriented and open services/applications away from existing silos.

    1. Your assistant. Your machine. Your rules. Unlike SaaS assistants where your data lives on someone else’s servers, OpenClaw runs where you choose—laptop, homelab, or VPS. Your infrastructure. Your keys. Your data.

      you run openclaw yourself. I think I saw [[Martijn Aslander p]] use it on a VPS yday.

    2. OpenClaw is an open agent platform that runs on your machine and works from the chat apps you already use

      openclaw an agent platform you interact with through regular chat apps.

    3. Two months ago, I hacked together a weekend project. What started as “WhatsApp Relay” now has over 100,000 GitHub stars and drew 2 million visitors in a single week.

      Openclaw started as a side project in #2025/11

    1. He talks about the intended audience for his work, whom he is speaking to. “My work addresses black [American] people, everybody else gets to listen in.” How having a limited imagined audience for your work is not an exclusionary act. How it is something that breathes life into the work, injects meaning and passion into a creative expression, impossible to achieve if that work would have been imagined for everyone. After which that life, meaning and passion can be appreciated as well by anyone outside those that are originally being addressed.

      n:: Imagined/intended audience as means to creative expression, not an exclusion: n:: there's a diff between imagined audience, and actual audience after creation. vgl [[Assumed audience definieren 20211113212257]] ref the video interview by [[Arthur Jafa c]]

    2. He talks about the spectrum between good and bad, hence the title of the interview ‘not all good, not all bad’. That us typically wanting to pigeonhole someone or something as either good or bad, before finding out an aspect about it that doesn’t fit, should not lead to then fully switching to labeling it the opposite. You have to get comfortable with the discomfort of juggling different and opposite notions about someone or something at the same time.

      vgl [[Holding questions 20091015123253]] mbt ongemak / vgl complexiteit

    1. Digitale soevereiniteit gaat over controle op drie niveaus: geografisch, juridisch en operationeel. Als data en kritische bedrijfsprocessen in datacentra binnen Nederland of Europa staan, dan ben je geografisch en juridisch in control, omdat deze datacenters vallen onder Nederlandse en Europese jurisdictie. Dat is echter niet voldoende, want voor digitale soevereiniteit is ook operationele controle nodig.

      Dit klopt niet: je bent juridisch niet in control als andere mogendheden tegelijkertijd ook jurisdictie hebben. Hier wordt geografische control gelijkgesteld aan juridische, en dat is precies wat niet het geval is (en wel zou moeten zijn)

      voor soevereiniteit zegt het hier ook operationale control nodig.

    2. Het lijkt in het huidige debat alsof de hele overheid voor haar digitalisering moet overgaan naar autonome of soevereine toepassingen, en wel meteen. Dat is echter niet haalbaar en ook niet nodig. Het begint met het maken van heldere keuzes voor welke data en systemen digitale autonomie en soevereiniteit nodig zijn, en voor welke niet. Zodat vervolgens in een realistisch tempo en haalbare stappen de overgang ingezet kan worden.

      Deze zinnen hebben alleen betekenis als je de definitie van soevereiniteit hierboven als operationele control volgt. (operationeel heeft te maken met autonomie juist). Dat meteen is een flauw trucje om 'onhaalbaar' te kunnen zeggen. digitale autonomie en soevereiniteit wordt hier gekoppeld aan 'data en systemen' die dat nodig hebben. Maar het hangt aan de overheid als instituut, dwz je hebt het altijd nodig. Hooguit is iets minder ondermijnend dan andere dingen. (Digid, vs verkeerslichtbesturing)

    3. Daarom is voor digitale soevereiniteit ook operationele controle nodig. Dat realiseer je door waarborgen in te bouwen, die je in staat stellen om de controle te houden. Dit wordt bepaald door de keuze en een specifieke implementatie van de componenten waaruit de cloud is opgebouwd. Software van niet-Europese partijen kan binnen die veilige kaders nog steeds gebruikt worden. Nog beter is het om toepassingen te gebruiken van Nederlandse of Europese aanbieders. Ook dan zijn waarborgen nodig, zoals afspraken over verkoop aan ongewenste partijen.

      Dit klopt alleen binnen bovenstaande definities. Omdat ze de crux, een ander land claimt jurisdictie naast de onze, hierboven hebben weggemoffeld.

    4. Digitale autonomie gaat over het zelfstandig keuzes kunnen maken in het digitale domein. Het gaat over het behouden van beslissingsbevoegdheid, zonder volledige onafhankelijkheid. Digitale soevereiniteit gaat een stap verder. Het betekent volledige controle en zeggenschap over data, digitale infrastructuur en technologieën.

      Hmm. Twee andere definities weer: digi-autonomie 'zelfstandig keuzes kunnen maken in het digitale domein' (het houden v beslissingsbevoegdheid) digi-soevereiniteit 'gaat stap verder', als zeggenschap over data, digi infra en technologieen.

      Ik zie dat beiden als autonomie, en soevereiniteit dat niemand je kan beinvloeden via je digi tooling.

      Dit is een opinie van Centric en Uniserver.

    1. The choice is ours. We simply need to choose whom we admire. Whom we want to recognize as successful. Whom we aspire to be when we grow up. We need to sing the praises of our true heroes: those who contribute to our commons.

      Key point here is that bigtech is the outcome of a specific definition of succes (centralised growth vs spreading) (not mentioned that funding vc style necessitates growth / extraction)

    1. Supporting Forgejo with work on dependency features would help too. The goal would be feature parity with GitHub and GitLab so self-hosted forges work with the same security tooling.

      a call for direct funding of Forgejo to reach feature parity w Github / gitlab. Forgejo is fork of Gitea (like Codeberg too).

    2. Procurement requirements could include open supply chain tooling. If an agency requires SBOMs, they could also require that generation doesn’t depend on proprietary services. If they require vulnerability scanning, the scanner could consume open advisory databases. Germany’s ZenDiS and openCode.de initiatives are relevant here. Connecting them with existing open solutions would be more efficient than starting fresh.

      Add (kick-out!) requirements to procurement specs. This is a way ensure open source and standards get adopted. Mentions ZenDiS, openCode.de as relevant examples. - [ ] return to look at ZenDiS and opencode.de

    3. The strategy is to unbundle the parts of a package manager and standardize them individually. Registry APIs, dependency graphs, vulnerability feeds, update notifications. Each piece can be commodified without replacing entire systems. Eat the elephant one bite at a time.

      yes, this is also how you tackle all the other silos. Deconstruct and recombine along different principles

    4. Treat dependency intelligence as infrastructure worth funding directly. The Sovereign Tech Fund model applies: direct funding to open source projects that serve as foundations. Ecosyste.ms, VulnerableCode, OSV, PURL implementations, CycloneDX/SPDX tooling, Forgejo’s dependency features all fit this category.

      suggests see Dependency intelligence as infrastructure, and fund directly, as through the [[Legal Information Sovereign Tech Agency]] fund.

    5. The gap between these columns is where standardization would reduce switching costs. Not building a European deps.dev, but defining a common dependency graph API. Not building a European Dependabot, but standardizing how dependency updates get proposed. A protocol for package management could let different implementations compete on the same interfaces. GitHub and GitLab bundle dependency features into their platforms: dependency graphs, vulnerability alerts, automated updates. A self-hosted Forgejo or Gitea instance doesn’t have equivalent tooling. But if those features were built on open standards and open data sources, switching forges wouldn’t mean losing supply chain visibility. The dependency intelligence could come from any provider that implements the same interfaces, rather than being locked to the forge vendor. Some gaps need new standards rather than adoption of existing ones. There’s no good specification for package version history across registries. Codemeta describes a package at a point in time, not its release history. PkgFed proposes using ActivityPub to federate release announcements, similar to how ForgeFed handles forge events.

      This points to where standards can reduce friction. a common dependency graph API standard for proposing dependency update protocol for package management dependency features based on open standards / open data so that dependency intelligence is not a lock-in element.

      New standards need for package version history across registries. Mentions PkgFed en Forgefed vgl [[PkgFed ActivityPub for Package Releases]]

    6. Most standards work in this space focuses on compliance artifacts: SBOMs for the Cyber Resilience Act, attestations for procurement requirements. Less attention goes to the underlying tools developers actually use. The dependency graph that feeds the SBOM generator, the metadata lookup that powers vulnerability scanning, the notification when a new version ships.

      Says standards in this topic are aimed at compliance. SBOMs for the Cyber Resilience Act e.g. [[Cyber Resilience Act CRA EU 20231026123507]]

    7. Other areas don’t, which keeps switching costs high. Dependency graph APIs vary by platform, vulnerability scanning integration is proprietary per forge, Dependabot and Renovate each have their own config format, and package metadata APIs differ across registries.

      Areas that do not have (de facto) standards, meaning high switching costs: dependency graph APIs vulnerability scanning integration package metadata APIs are all different.

    8. some areas have formal specifications. PURL provides a standardized way to reference packages across ecosystems. OSV and OpenVEX let advisory data flow between systems. CycloneDX and SPDX handle SBOMs. SLSA, in-toto, and TUF cover provenance. OCI standardizes container images.

      Formal standards exist for some areas only. Mentions Purl for references to packages OSV OpenVEX for advisory data flows Cyclone DX and SPDX for SBOMs, SLSA in-toto, TUF on provenance OCI for container images. How many of these are indeed formal standards? Does he mean documented ?

      • [ ] return to search if these are formal standards, and by which standards body, plus links
    9. Eaves’s commodification argument depends on standards to reduce switching costs. In the package management landscape, some de facto standards have emerged. Git is nearly universal for source hosting. Semver is the dominant versioning scheme, even if ecosystems interpret it differently. Lockfile formats vary by ecosystem, but they’ve become standards in practice: every dependency scanning company builds the same set of parsers to extract dependency information from all of them. Syft, bibliothecary, gemnasium, osv-scalibr, and others all parse the same formats. I made a dataset covering manifest and lockfile examples across ecosystems, and a similar collection of OpenAPI schemas for registry APIs. These are what made git-pkgs come together quickly.

      In package management there are a range of de facto standard modes of operation. These are not formal standards, just emerged in practice.

    10. Dries Buytaert extended this to procurement: governments buy from system integrators who package and resell open source, but that money doesn’t reach the maintainers who build it. If procurement scoring rewarded upstream contributions, money would flow differently. Open source is “the only software you can run without permission” and therefore useful for sovereignty, but it needs funding to work.

      See [[Funding Open Source for Digital Sovereignty]]

    11. Ploum made a related point: Europe doesn’t need a European Google. The European contribution to software has been infrastructure that serves as collective commons: the web, Linux, Git, VLC, OpenStreetMap.

      [[Why there’s no European Google]]

    12. The security and metadata tooling built on top of these registries tends to be US-based regardless of where the registry itself is hosted. A European company running Forgejo for code hosting still typically uses US services for dependency updates, vulnerability scanning, license compliance, and SBOM generation. Self-hosting the forge doesn’t change the intelligence layer.

      common situation. You stack tools, and may only have one of them in the EU or selfhosted

    13. The package registries follow a similar pattern, with a few European exceptions: Registry Owner Country npm Microsoft US PyPI Python Software Foundation US RubyGems Ruby Central US Maven Central Sonatype US NuGet Microsoft US Crates.io Rust Foundation US Go module proxy Google US Docker Hub Docker Inc US Conda/Anaconda Anaconda Inc US CocoaPods CocoaPods US Pub.dev Google US CPAN Perl Foundation US Homebrew Homebrew US Hex.pm Six Colors AB Sweden Packagist Private Packagist Netherlands CRAN R Foundation Austria Clojars Clojars Germany

      package registries, names 4 EU based ones. Hex.pm, packagist, cran, clojars. Are these aimed at different things or comparable?

    14. Most git forges are US-based: Forge Owner Country GitHub Microsoft US GitLab GitLab Inc US Gitea Gitea Ltd US HuggingFace Hugging Face Inc US

      It says most are US, but lists none other. I think it should say Gitea Ltd as UK? bc of the Ltd? Gitea has been forked into Forgejo (and Codeberg). Gitea is open source, GitLab has an open source community version, but otherwise closed.

    15. The same logic applies to the software supply chain, though that layer gets less attention in sovereignty discussions than cloud and storage.

      This article applies the same logic as David Eaves in [[The Path to a Sovereign Tech Stack is Via a Commodified Tech Stack]] to the 'software supply chain' here interpreted as: git forges, dependency intelligence layer on top of them, and package registries (like npm etc).

    16. Europe shouldn’t try to build its own AWS. Instead, governments should use procurement power to enforce interoperability standards.

      (David Eaves argument recap:) The answer is not in replicating similar type of organisations (like AWS) but in interoperability. I tend to agree. The problem w hyperscalers is the hyper and the scale. We don't do that for internet infrastructure either. Vgl [[The Path to a Sovereign Tech Stack is Via a Commodified Tech Stack]]

    17. If governments required that kind of compatibility as a condition for contracts, smaller providers could compete. Sovereignty through standards rather than state-owned infrastructure.

      Premisse: if public procurement demanded interoperability / compatibility, it would allow more competition. 'Sovereignty through standards'. I agree that interoperability is the way to go (vgl [[SEMIC Conf woensdag 20251126092049]]. However in public procurement often the ask is for the type of integration of 1 provider, which precludes a tapestry of interoperable elements. So there's more to it than this.

    1. Mais en novembre, le groupe français a répondu à un nouvel appel d’offres, cette fois pour identifier et localiser des étrangers. Cela s'appelle du skip-tracing, et une urgence pour l'ICE. Capgemini rafle la plus grosse part du marché, avec jusqu'à 365 millions de dollars à la clé. C'est écrit noir sur blanc : plus la société française localisera de migrants, plus elle pourra empocher d'argent. Les bonus financiers, en effet, sont basés sur le taux de réussite dans la vérification des adresses des étrangers.

      End of 2025 Capgemini entered into a new contract w ICE wrt skip-tracing. 365M USD, but Capgemini earns more when they locate more foreigners. --> this is worse than 'being IBM' bc now they have a direct financial stake in locating additional people.

    2. Le champion français des services informatiques compte 350 000 collaborateurs dans le monde, et une filiale américaine installée près de Washington. Celle-ci travaille avec plusieurs agences gouvernementales : ministère de la Santé, des Anciens Combattants et, depuis plus de quinze ans, le département de la Sécurité intérieure. Des contrats que nous avons consultés sur les bases de données publiques. Pour l'ICE, Capgemini gère par exemple un standard téléphonique réservé aux victimes de crimes commis par des étrangers. Une création de Donald Trump.

      Capgemini's US branch obv has many contracts w branches of the US admin. DHS has been a client for 15yrs. ICE has contracted a hotline to report crime by 'foreigners' to Capgemini eg

    1. Freedom internet provider on the difficulty of blocking Russian state media sites. - there is a court order to block sanctioned websites - however there is no official list of sanctioned websites - there are several lists from different MS and branche organisations with suggested sites, but this is never an official list or effort. - one of those lists, the one from Lithuania contains sites that are clearly not Russian state media (an Indian social media platform, and a generic video sharing site)

    1. Dutch ABP (a 500 billion pensionfund) dropped a third of their US treasury bills, 10 billion of 29 billion (March '25) to now 19 billion (Sept '25). The money was reinvested in Dutch and German bonds.

    1. he Commission has extended its ongoing formal proceedings opened against X in December 2023 to  establish whether X has properly assessed and mitigated all systemic risks, as defined in the DSA, associated with its recommender systems, including the impact of its recently announced switch to a Grok-based recommender system.

      The existing investigation of X under the DSA wrt recommender systems is extended in scope to include the recommender functions that Grok is announced to provide

    2. The new investigation will assess whether the company properly assessed and mitigated risks associated with the deployment of Grok's functionalities into X in the EU. This includes risks related to the dissemination of illegal content in the EU, such as manipulated sexually explicit images, including content that may amount to child sexual abuse material.

      A new investigation under the DSA wrt Grok and the production/dissemination of illegal incl sexualised imagery and CSAM

    1. Ranking of cities by how well cycling is organised / accomodated. In the European ranking (which is the same top 5 as the global one), Utrecht and Amsterdam, plus obv CPH itself, Gent and now Paris.

    1. In 5 yrs Paris has doubled cycling's modal share, and become 5th ranking city in the Copenhagenize urban cycling index. Last summer ([[Paris Versailles 2025]]) we noticed the difference (compared to [[Paris 2021]] but also thought a lot still looked improvised not embedded yet. So probably some way until it's truly ingrained

    1. blogger Fabrizio Ferri Benedetti on their 4 modes of using AI in technical writing. - watercooler conversations, to get code explained - text suggestions while writing/coding (esp for repeating patterns in your work - providing context / constraints / intent to generate first drafts, restructure content, or boilerplate commentary etc. - a robotic assembly line, to do checks, tests and rewrites. MCP/skills involved.

      Not either/or but switching between modes

    1. OpenHands demonstrated strong capabilities, particularly for complex refactoring tasks. With better configuration and more explicit instructions about development workflows, it could likely match Copilot's reliability. The open-source nature also makes it attractive, since the entire system can be self-hosted and confugred for every team's or project's needs.

      openhands useful but likely needs more explicit instructions than others

    2. OpenHands: Capable but Requiring InterventionI connected my repository to OpenHands through the All Hands cloud platform. I pointed the agent at a specific issue, instructing it to follow the detailed requirements and create a pull request when complete. The conversational interface displayed the agent's reasoning as it worked through the problem, and the approach appeared logical.

      Also used openhands for a test. says it needs intervention (not fully delegated iow)

    3. When an agent doesn't deliver what you expected, the temptation is to engage in corrective dialogue — to guide the agent toward the right solution through feedback. While some agents support this interaction model, it's often more valuable to treat failures as specification bugs. Ask yourself: what information was missing that caused the agent to make incorrect decisions? What assumptions did I fail to make explicit?This approach builds your specification-writing skills rapidly. After a few iterations, you develop an intuition for what needs to be explicit, what edge cases to cover, and how to structure instructions for maximum clarity. The goal isn't perfection on the first try, but rather continuous improvement in your ability to delegate effectively.

      don't iterate for corrections. Redo and iterate the instructions. This is a bit like prompt engineering the oracle, no? AI isn't the issue, it's your instructions. Up to a point, but in flux too.

    4. A complete task specification goes beyond describing what needs to be done. It should encompass the entire development lifecycle for that specific task. Think of it as creating a mini project plan that an intelligent but literal agent can follow from start to finish.

      A discrete task description to be treated like a project in the GTD sense (anything above 2 steps is a project). At what point is this overkill, as in templating this project description may well lead to having the solutions once you've done this.

    5. The fundamental rule for working with asynchronous agents contradicts much of modern agile thinking: create complete and precise task definitions upfront. This isn't about returning to waterfall methodologies, but rather recognizing that when you delegate to an AI agent, you need to provide all the context and guidance that you would naturally provide through conversation and iteration with a human developer.

      What I mentioned above: to delegate you need to be able to fully describe and provide context for a discrete task.

    6. The ecosystem of asynchronous coding agents is rapidly evolving, with each offering different integration points and capabilities:GitHub Copilot Agent: Accessible through GitHub by assigning issues to the Copilot user, with additional VS Code integrationCodex: OpenAI's hosted coding agent, available through their platform and accessible from ChatGPTOpenHands: Open-source agent available through the All Hands web app or self-hosted deploymentsJules: Google Labs product with GitHub integration capabilitiesDevin: The pioneering coding agent from Cognition that first demonstrated this paradigmCursor background agents: Embedded directly in the Cursor IDECI/CD integrations: Many command-line tools can function as asynchronous agents when integrated into GitHub Actions or continuous integration scripts

      A list of async coding agents in #2025/08 github, openai, google mentioned. OpenHands is the one open source mentioned. mentions that command line tools can be used (if integrated w e.g. github actions to tie into the coding environment) - [ ] check out openhands agent by All Hands

    7. You prepare a work item in the form of a ticket, issue, or task definition, hand it off to the agent, and then move on to other work.

      compares delegation to formulating a 'ticket'. Assumes well defined tasks up front I think, rather than exploratory things.

    8. While interactive AI keeps you tethered to the development process, requiring constant attention and decision-making, asynchronous agents transform you from a driver into a delegator.

      async means no handholding, but delegation instead. That is enticing obviously, but assumes unattended execution can be trusted. Seems a big if.

    9. why asynchronous agents deserve more attention than they currently receive, provides practical guidelines for working with them effectively, and shares real-world experience using multiple agents to refactor a production codebase.

      3 things in this article: - why async agents deserve more attention - practical guidelines for effective deployment - real world examples

    10. asynchronous coding agents represent a fundamentally different — and potentially more powerful — approach to AI-augmented software development. These background agents accept complete work items, execute them independently, and return finished solutions while you focus on other tasks.

      Async coding agents is a diff kind of vibe coding: you give it a defined more complex tasks and it will work in the background and come back with an outcome.

    1. Further ReadingI’m not gonna pretend to be an expert here (any more than I’m an expert Obsidian plugin developer :p) but here are some resources that helped me figure out Claude CodeKent writes a lot about how he uses Obsidian with Claude Code.This is an incredible hub of resources for using Claude Code for project management, by someone who also uses Obsidian.This take on Claude Code for non-developers helped solidify my understanding of how it all works; it hallucinates less, for one thing.Eleanor Berger has fantastic tips for working with asynchronous coding agents and is incredibly level-headed about the LLM landscape.This article does a great job of breaking down all the nitty-gritty of how Claude Code works.Damian Player has a step-by-step guide on using Claude Code as a non-technical person that goes into more depth.Here’s a tutorial from a pro that breaks down best practices for using Claude Code, like the importance of planning and thinking things through, and exactly why a good CLAUDE.md file matters.

      Links w further reading wrt Claude Code and Obsidian. Most of these are links to X. Ugh.

    2. Little Tips for Claude Code + Obsidian

      Some tips on her usage of Claude Code. - Put all your work in a folder next to the obsidian folder - to treat skills and commands like functions. Don't ever repeat them. - Install and use git locally to have a commit history. - On each step that you need to correct Claude code, tell it to write down directions or rules to avoid a mistake in the future. - circumvent public API liimits by changing the query slightly, or hit it in parallel

    3. Terminal Practice with GamesSome folks I’ve talked to are a little intimidated by the terminal. Want to practice in a low-stakes way?

      now we're back to terminal, I am still not sure about her set-up.

    4. As for the privacy concerns? There isn’t anything private in my vault, so I don’t really care about Anthropic access.

      if you don't have personal stuff or personal data on others in your vault, privacy is less a concern with cloud models. True. Except I think any pkm is about personal knowledge and while not personal data per se, there is a vulnerability involved there.

    5. My favorite kind of problem is a solvable problem. I know a lot of people who just brute force or deal with their issues, but I try to notice pain points and deal with them. This isn’t just an AI thing, this is a life thing.

      Interesting point, and fair enough. Start from the friction points. Like w open data [[Open data begint buiten 20200808162905]]

    6. Building the habit of delegating — and using language clear and precise enough for a teenaged girl who doesn’t live in my house to understand — has really helped with leveraging LLMs.

      Ha! n:: habit building of delegating, good point using precise language to teens as training for llms

    7. Suddenly, I can actually make use of the APIs I’ve always known existed.

      yes, recognisable, there are a whole bunch of APIs on things I woud like to use that I'm not bc figuring out their workings in Postman takes too much effort

    8. But these days I’m not generally trying to do things faster, I’m trying to do them with less attention. All these searches and tasks run in the background, which means they actually get done. When I had to actively sit there and click through things, half of it never happened because something else more important would come up, or I just didn’t feel like doing grunt work just then.

      Speaks of how the purpose is not being faster but gtd with less attention on things you don't want to free up attention for. As long as you keep it away from your own key things I suppose. The periphery of what you pay attention to. The many little side projects on the someday/maybe list, the ones just out of reach. Enticing promise! This is the lure ofc.

    9. Setting Claude Code Up in ObsidianI was genuinely surprised at how easy the terminal plugin was to install for Obsidian. In Obsidian, I went to community plugins, searched for “terminal,” and installed the Terminal plugin by polyipseity. Then I clicked the “open terminal” button on the left-hand side. That’s it.There’s a dedicated Claudian plugin (subtly different from the Claudsidian solution people), but the Terminal felt a little higher fidelity to how I’m used to doing things, and a little simpler to understand. Plus, Claudian looks great but honestly I don’t think I can live without plan mode, which the readme says it doesn’t currently support. Plan mode is nice because it asks questions, really thinks things through, and can be trusted not to do dumb destructive things.

      There is a terminal plugin for Obsidian that you can connect to Claude Code (apparently). She advices against the Claudian plugin bc it lacks plan mode (i.e. not immediately act)

    10. If you have been following along with me for years you know I don’t hype things just because people are hyping things. But Claude Code finally has made AI a core part of my processes instead of just a thing I use sometimes as an extra source or bonus spell checker or quicker way to reformat files.

      She feels Claude Code is now a core tool in her workflows

    11. The UI feels so intuitive, like an old-school MUD.

      UI? Are we still talking about the terminal? Ah no, she means the desktop version, see [[Claude Code for VSCode - Visual Studio Marketplace]] for the VScode plugin as well.

    Tags

    Annotators

    URL

    1. May I encourage all reading this to find ways to talk to people, to nudge people to take action, to become “upstanders” (as opposed to “bystanders”). An upstander is someone who takes positive action, no matter how small, to counter evil.

      upstanders vs bystanders, and shifting the percentages a bit towards the former.

    1. https://web.archive.org/web/20260123124049/https://www.computerworld.com/article/4118639/aws-european-cloud-service-launch-raises-questions-over-sovereignty.html

      AWS European cloud service launch raises questions over sovereignty. not really though. It's quite obvious what kind of attempt this is. There are plenty that now feel nervous but will opt for anything that lets them say with plausible deniability that they did something without going through the actual work of a full transition

    2. While there are questions around the implications of the ownership structure, AWS’s European Sovereign Cloud still provides a greater level of sovereignty compared to its standard public cloud service in terms of enabling regulatory compliance, according to analysts. This could appeal to European organizations, they said, depending on their sovereignty requirements.

      for companies perhaps, not for public sector in any way though. precisely bc the core problem is not 'regulatory compliance' (and doesn't that imply their current public cloud is a bit shit then?)

    3. “There has been a pivotal shift in the last few months; we have seen a fundamental switch from just interest in sovereign solutions to actual buying behaviors,” said Maisto. “The demand is there. Organizations are investing money into sovereign migration projects, and we have not seen this before,” he said.

      companies are voting with their procurement now

    4. In the end, most customers will opt for strategies that comprise a mix of sovereignty levels depending on their needs.

      yes, during transition bc of pragmatics, same for my company, but while fully understanding the desired end-state, which is no big players USA or wherever based.

    5. Google and Thales, for instance, or Microsoft and Bleu, a joint venture between Orange and Capgemini. This involves the hyperscaler providing access to its technology, while the two companies remain independent. Buest said the arrangement provides a higher level of “operational sovereignty” compared to AWS European Sovereign Cloud, though it still involves some level of technological dependence on the hyperscaler.

      sovereignty washing efforts include US hyperscalers partnering with EU based entities. Mention of Thales is significant here, as they are a large defence entity. They should know better.

    1. The other one that happened was just before Russia invaded Ukraine, they managed to disable the Viasat modems. And this is an interesting case. These modems are used for satellite communications. And they were able to attack these modems so that they physically disabled themselves. It was not like the denial of service attack on the network. No, they managed to wipe the firmware of all these modems in such a way that it could not be replaced. The reason we know about this stuff so well is it turns out there were lots of windmills that also had these modems. In Germany, apparently 4,000 of these modems stopped working. And there were 4,000 wind turbines that could no longer be operated. So this was a military cyber attack that happened as Russia was invading Ukraine. And it was of great benefit to them because it disabled a lot of military communications in Ukraine. But this is the kind of thing that can happen, only that it’s quite rare.

      Russia compromised Viasat modems before the Feb2022 invasion, to disrupt Ukraine's satcoms for the military. However these modems are also used in German windparks, losing control over 4000 windmills.

    1. The best time to learn how to work together with a group of people is before a crisis, not during it. Crisis engineering tells us that a team is more likely to be successful if everyone has already worked together.

      general lesson why training is needed, even if that training is just 'being a group with activities'

    2. Most of the antennas that ship with evaluation boards are not very good. One option for an upgrade if you’re using the recommended 868 MHz network is the Taoglas TI.08.A. IMPORTANT: Never turn on a LoRa device without an antenna attached! The power sent to the antenna can destroy the device if there is no antenna attached to radiate it.

      suggested antenna for 868MHz network. Taoglas

    3. LILYGO T-Echo If you’d like a device that good for hacking and comes in a small case, The LILYGO T-Echo is a simple small low-power ready-to-use handheld device for about €80. It has ~3cm square e-ink display, a case with a few buttons, Bluetooth, GPS, and about a day’s worth of battery. Input/output/charging is via USB-C (but use a USB-A to USB-C cable). Received messages are displayed on the e-ink screen and can be cycled through with the buttons. Sending messages requires connecting with another device via Bluetooth.

      another device, bit more expensive but w case and gps

    4. This is a great option for your “everyday carry” Meshtastic node. It’s the size and shape of a few credit cards. It’s also convenient to give to your less technical family and friends.

      regular general use device

    5. Heltec V4 or later If you have more time than money, try the Heltec V4 or later, currently one of the cheapest boards available at around €20. It has a postage stamp-sized OLED screen, a couple of tiny buttons, WiFi/Bluetooth, and USB-C input/power (but use a USB-A to USB-C cable). Received messages are displayed on the OLED and can be cycled through with tiny buttons. Sending messages requires connecting to it via WiFi or Bluetooth. It has no case, but the little plastic box it comes in can easily be turned into one with a sharp pen knife. It also has no battery, but it is a good idea to have a separate power bank anyway since you need a working phone or computer to send messages. It has no GPS.

      heltec v4 cheapest. Use case it came in to make casing out of. use a usb-a to usb-c cable to charge!

    6. SenseCap Solar P-1 Pro For people who can afford €100, this is the best option to add a LoRa node that will keep running without external power. It is a solar-powered battery-backed LoRa node ready to attach to your balcony or roof or fence. The P-1 Pro includes batteries and GPS; the P-1 does not.

      solar powered device. Can it be flashed for meshcore? useful as repeater?

    7. Solar powered, battery-backed outdoor: SenseCap Solar P-1 Pro Cheapest: Heltec V4 Everyday carry and/or for non-techies: SenseCap Card Tracker 1000E Portable, good for hacking: LILYGO T-Echo

      4 diff LoRa devices named. I have 4 Heltec v4's whic don't have gps it says here.

    8. How to form an Internet Resiliency Club: Collect a group of internet-y people within ~10 km of each other Decide how to communicate normally (Signal, Matrix, email, etc.) Buy everyone LoRa (Long Range) radios and a powerbank with trickle charge Install Meshtastic on the LoRa radios Choose a LoRa channel to communicate on Organize meetups, send messages over Meshtastic, have fun If you work for a internet infrastructure company, you can suggest giving interested employees a LoRa radio, a mobile phone powerbank, and maybe even a small solar panel for their personal use (perhaps as part of an annual gift or bonus).

      this is half a plan. The LoRA stuff is to be able to keep comms within the group up if they fail. And the group is then expected to bootstrap general connectivity. The rest of the page only deals with LoRa and choosing devices. No word on the actual work of achieving internet resilience, other than 'collect a group of internet-y people'.

    9. Ham radio is too expensive, difficult, and power-hungry Initially I looked into ham radio, but it is just too expensive, difficult, and power-hungry to be practical. Then Alexander Yurtchenko told me about LoRa (Long Range) radio and Meshtastic, a cheap, low-power method of sending text messages across a few kilometers.

      Don't really agree with this. Ham radio isn't this by def. There's a reason hamradio is part of national civil protection services ([[DARES – Dutch Amateur Radio Emergency Service]]) It does require ham licenses.

    10. I started thinking about what I could personally do without any help from government or businesses. What if I could organize a group of volunteer networking experts who could communicate without any centralized infrastructure? We could effectively bootstrap communications recovery with just a few volunteers and some cheap hardware.

      ah. so a group of people who know how to get connectivity going, using meshcore to be able to initially coordinate?

    11. What made me finally take action is watching a video created by Ukrainian IXP 1-IX to teach other European countries what Ukrainian internet operators have learned about hardening and repairing internet infrastructure leading up to and following the 2022 Russian invasion. The practical realities of keeping networks operating during war were sobering: building camoflouged router rooms with 3 days of generator power, replacing active fiber optic cable with passive, getting military service exemptions for their personnel, etc.. You can watch the most recent version, “Network Resilience: Experiences of survival and development during the war in Ukraine”, a 30 minute presentation at RIPE 90.

      Trigger for author was seeing how Ukraine worked on internet resilience. Power outage is one, internet infra itself (routing, fiber) too

    12. I am Valerie Aurora, a systems software engineer with 25 years of experience in open source software, operating systems, networking, file systems, and volunteer organizing. When I moved from San Francisco to Amsterdam in 2023, I started looking for ways to give back to my new home. In addition to systems consulting, I am a special rapporteur for the EU’s Cyber Resilience Act, serve as a RIPE Meeting program committee member, and speak at European technical conferences.

      Valerie Aurora, AMS based, 25+ SE experience. RIPE member, rapporteur for CRA

    1. Organizations that understand the Al Capone theory of sexual harassment have an advantage: they know that reports or rumors of sexual misconduct are a sign they need to investigate for other incidents of misconduct, sexual or otherwise. Sometimes sexual misconduct is hard to verify because a careful perpetrator will make sure there aren’t any additional witnesses or records beyond the target and the target’s memory (although with the increase in use of text messaging in the United States over the past decade, we are seeing more and more cases where victims have substantial written evidence). But one of the implications of the Al Capone theory is that even if an organization can’t prove allegations of sexual misconduct, the allegations themselves are sign to also urgently investigate a wide range of aspects of an employee’s conduct.

      The 'Al Capone theory' of sexual harassment: the harassment is one expression of underlying behaviour that can also take other forms of misconduct. Reports or rumors of the one may result in the need to research the others.

    1. While the initial results fall short, the AI field has a history of blowing through challenging benchmarks. Now that the APEX-Agents test is public, it’s an open challenge for AI labs that believe they can do better — something Foody fully expects in the months to come.

      expectation that models will get trained against the tests they currently fail.

    2. “The way we do our jobs isn’t with one individual giving us all the context in one place. In real life, you’re operating across Slack and Google Drive and all these other tools.” For many agentic AI models, that kind of multi-domain reasoning is still hit or miss.

      I understand this para but the phrasing is off. slack and google drive is not 'multi-domain' but tools. Seems like two arguments joined up: multitool / multidomain, meaning ai agents can't switch. (In practice I see people build small agents for each facet and then chain / join them)

    3. The new research looks at how leading AI models hold up doing actual white-collar work tasks, drawn from consulting, investment banking, and law. The result is a new benchmark called APEX-Agents — and so far, every AI lab is getting a failing grade. Faced with queries from real professionals, even the best models struggled to get more than a quarter of the questions right. The vast majority of the time, the model came back with a wrong answer or no answer at all.

      In consulting, investment banking, law, ai agents had 18-24% score or worse (and in real life circumstances you don't know which is which so you need to check all output)

    1. FTM over de baten van de WOO, na OSF rapport baten van transparantie. Wijst ook op hoe groepen overheidsorganisaties (als universiteiten, ministeries) en ook de vorige MinBZK de WOO wel willen inperken. Vanwege de kosten, die vooral hoog uitvallen door de gebrekkige staat van de informatiehuishouding

    1. Moldova is formally leaving the CIS agreements. In practice they left in 2023. Read some comments asking 'why only now'. Part of it is that Moldova has Russian troops on its territory, depended for exports on Russia and wasn't clearly on an European path. With the EU path better locked in and having spent time on reducing exposure, it seems the recent elections marked that now the time is ready to make the formal renouncements. Vgl [[Chisinau Moldova 2012]] when I worked there

    1. increase options in order to rebuild sovereignty – sovereignty that was once grounded in rules, but will increasingly be anchored in the ability to withstand pressure.This room knows this is classic risk management. Risk management comes at a price, but that cost of strategic autonomy, of sovereignty can also be shared.

      very much this. sovereignty anchored in withstanding pressure, and the effort shared in networks of likeminded parties. This is networked agency for nations!