🌈 Social 📸 Photography 🌈

Lars Fiedler :darktable:An interesting 30 min. documentation about the "Hit the North" street-art festival in Belfast. Available with FR/GE audio or subtitles in ES/EN. Enjoy.<a href="https://www.arte.tv/de/videos/122702-009-A/360-reportage/" rel="nofollow noopener" translate="no" target="_blank">https://www.arte.tv/de/videos/122702-009-A/360-reportage/</a><a href="https://mastoart.social/tags/tv" class="mention hashtag" rel="nofollow noopener" target="_blank">#tv</a> <a href="https://mastoart.social/tags/documentation" class="mention hashtag" rel="nofollow noopener" target="_blank">#documentation</a> <a href="https://mastoart.social/tags/arte" class="mention hashtag" rel="nofollow noopener" target="_blank">#arte</a> <a href="https://mastoart.social/tags/streetArt" class="mention hashtag" rel="nofollow noopener" target="_blank">#streetArt</a> <a href="https://mastoart.social/tags/mural" class="mention hashtag" rel="nofollow noopener" target="_blank">#mural</a> <a href="https://mastoart.social/tags/graffiti" class="mention hashtag" rel="nofollow noopener" target="_blank">#graffiti</a> <a href="https://mastoart.social/tags/art" class="mention hashtag" rel="nofollow noopener" target="_blank">#art</a>

Alvin Ashcraft 🐿️Supercharge your workflow with real-time information from the Microsoft Learn MCP Server<a href="https://techcommunity.microsoft.com/blog/MicrosoftLearnBlog/supercharge-your-workflow-with-real-time-information-from-the-microsoft-learn-mc/4440286" rel="nofollow noopener" translate="no" target="_blank">https://techcommunity.microsoft.com/blog/MicrosoftLearnBlog/supercharge-your-workflow-with-real-time-information-from-the-microsoft-learn-mc/4440286</a> <a href="https://hachyderm.io/tags/ai" class="mention hashtag" rel="nofollow noopener" target="_blank">#ai</a> <a href="https://hachyderm.io/tags/mcp" class="mention hashtag" rel="nofollow noopener" target="_blank">#mcp</a> <a href="https://hachyderm.io/tags/learn" class="mention hashtag" rel="nofollow noopener" target="_blank">#learn</a> <a href="https://hachyderm.io/tags/microsoftlearn" class="mention hashtag" rel="nofollow noopener" target="_blank">#microsoftlearn</a> <a href="https://hachyderm.io/tags/documentation" class="mention hashtag" rel="nofollow noopener" target="_blank">#documentation</a> <a href="https://hachyderm.io/tags/docs" class="mention hashtag" rel="nofollow noopener" target="_blank">#docs</a>

Still OrchardPAR AILLEURS les mastobébou-tes, si vous avez des tuyaux pour:- un taf en médiathèque, en archive, documentation, qqc avec des bouquins, de la culture- que ça recherche temps partiel- dans les alentours de Nantes ou dans le Pays de Retz / Sud Loire- et la cerise sur le gateau, si c'est en service public (j'accepte en privé mais j'y suis bcp plus frileuse, politiquement)Faites moi signe 🙏 C'est pas la motivation qui manque, mais les offres<a href="https://eldritch.cafe/tags/emploi" class="mention hashtag" rel="nofollow noopener" target="_blank">#emploi</a> <a href="https://eldritch.cafe/tags/autisme" class="mention hashtag" rel="nofollow noopener" target="_blank">#autisme</a> <a href="https://eldritch.cafe/tags/tdah" class="mention hashtag" rel="nofollow noopener" target="_blank">#tdah</a> <a href="https://eldritch.cafe/tags/chomage" class="mention hashtag" rel="nofollow noopener" target="_blank">#chomage</a> <a href="https://eldritch.cafe/tags/livre" class="mention hashtag" rel="nofollow noopener" target="_blank">#livre</a> <a href="https://eldritch.cafe/tags/bibliotheque" class="mention hashtag" rel="nofollow noopener" target="_blank">#bibliotheque</a> <a href="https://eldritch.cafe/tags/documentation" class="mention hashtag" rel="nofollow noopener" target="_blank">#documentation</a> <a href="https://eldritch.cafe/tags/servicepublic" class="mention hashtag" rel="nofollow noopener" target="_blank">#servicepublic</a>

claudedid some small work on classic <a href="https://post.lurk.org/tags/Dirt" class="mention hashtag" rel="nofollow noopener" target="_blank">#Dirt</a> <a href="https://post.lurk.org/tags/sampler" class="mention hashtag" rel="nofollow noopener" target="_blank">#sampler</a> <a href="https://post.lurk.org/tags/documentation" class="mention hashtag" rel="nofollow noopener" target="_blank">#documentation</a> the last day or two:- documentation now lists all the available <a href="https://post.lurk.org/tags/OSC" class="mention hashtag" rel="nofollow noopener" target="_blank">#OSC</a> message fields and what they do- documentation now has a <a href="https://post.lurk.org/tags/diagram" class="mention hashtag" rel="nofollow noopener" target="_blank">#diagram</a> of the audio engine signal flow- there is a new dirt-test program that sends a few messages so you can check if Dirt is working or not, which also serves as documentation on how to send messages to Dirt<a href="https://codeberg.org/uzu/dirt" rel="nofollow noopener" translate="no" target="_blank">https://codeberg.org/uzu/dirt</a>

Kevin Karhan :verified:<a href="https://fedi.chadthundercock.com/@chloe" class="u-url mention" rel="nofollow noopener" target="_blank">@chloe</a> espechally those that can't be assed to do the absolute minimum in terms of <a href="https://infosec.space/tags/documentation" class="mention hashtag" rel="nofollow noopener" target="_blank">#documentation</a>.Absolute Minimum of Documentation = Whatever the fuck <a href="https://infosec.space/tags/RaspberryPi" class="mention hashtag" rel="nofollow noopener" target="_blank">#RaspberryPi</a> does.<ul><li>Cuz everyone else isn't even halfassing that so every "competitor" feels scammy by releasing unbaked & unsupported hardware and basically telling paying customers to 'feck off' (like [chinese] garbage phone [EoL'd & dangerously outdated Android versions] manufacturers)…</li></ul>

Kevin Karhan :verified:<a href="https://social.treehouse.systems/@krutonium" class="u-url mention" rel="nofollow noopener" target="_blank">@krutonium</a> <a href="https://mstdn.jp/@landley" class="u-url mention" rel="nofollow noopener" target="_blank">@landley</a> I mean, Ideally <a href="https://infosec.space/@OS1337" class="u-url mention" rel="nofollow noopener" target="_blank">@OS1337</a> would be come a simpler and better alternative to <a href="https://infosec.space/tags/LinuxFromScratch" class="mention hashtag" rel="nofollow noopener" target="_blank">#LinuxFromScratch</a> or <a href="https://infosec.space/tags/YoctoLinux" class="mention hashtag" rel="nofollow noopener" target="_blank">#YoctoLinux</a> / <a href="https://infosec.space/tags/YoctoProject" class="mention hashtag" rel="nofollow noopener" target="_blank">#YoctoProject</a> when it comes to getting started on a device.<ul><li>Ideally <a href="https://infosec.space/tags/SBC" class="mention hashtag" rel="nofollow noopener" target="_blank">#SBC</a> manufacturers would at least release the <a href="https://infosec.space/tags/drivers" class="mention hashtag" rel="nofollow noopener" target="_blank">#drivers</a> (if they can't be assed to <a href="https://infosec.space/tags/mainline" class="mention hashtag" rel="nofollow noopener" target="_blank">#mainline</a> them into <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a>) and <a href="https://infosec.space/tags/ReproduceableBuilds" class="mention hashtag" rel="nofollow noopener" target="_blank">#ReproduceableBuilds</a> with build scripts to make them go brrr...</li></ul>Cuz <a href="https://infosec.space/tags/RaspberryPi" class="mention hashtag" rel="nofollow noopener" target="_blank">#RaspberryPi</a> de-facto monopolized non-<a href="https://infosec.space/tags/amd64" class="mention hashtag" rel="nofollow noopener" target="_blank">#amd64</a> / non-<a href="https://infosec.space/tags/ix86" class="mention hashtag" rel="nofollow noopener" target="_blank">#ix86</a> - <a href="https://infosec.space/tags/SBCs" class="mention hashtag" rel="nofollow noopener" target="_blank">#SBCs</a> because they actually give a shit and publish <a href="https://infosec.space/tags/documentation" class="mention hashtag" rel="nofollow noopener" target="_blank">#documentation</a>! <ul><li>So whilst they certainly don't support other OSes than <a href="https://infosec.space/tags/RaspberryPiOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#RaspberryPiOS</a>, they don't just tell folks like <a href="https://mastodon.social/@geerlingguy" class="u-url mention" rel="nofollow noopener" target="_blank">@geerlingguy</a> to not pester them with questions in their Forums.</li></ul>

Kevin Karhan :verified:<a href="https://floss.social/@jgoerzen" class="u-url mention" rel="nofollow noopener" target="_blank">@jgoerzen</a> yeah, in terms of absolute low power draw there may be something more power efficient than the <a href="https://infosec.space/tags/Pi0W2" class="mention hashtag" rel="nofollow noopener" target="_blank">#Pi0W2</a> (basically a cut-down <a href="https://infosec.space/tags/Pi3" class="mention hashtag" rel="nofollow noopener" target="_blank">#Pi3</a> A+) and <a href="https://infosec.space/tags/Pi0" class="mention hashtag" rel="nofollow noopener" target="_blank">#Pi0</a> / <a href="https://infosec.space/tags/Pi0W" class="mention hashtag" rel="nofollow noopener" target="_blank">#Pi0W</a> (a cut-down Pi 2 Model A)…<ul><li>There should be lower power consuming yet more powerful (or at least more powerful at the same power draw) options already due to snaller structural width. </li><li>After all the Xbox 360 went from 203W to 120W during it's lifecycle despite getting the Kinect as additional power-drawing accessory burdened on.</li></ul>Problem is that so far no "competitior" even came close to <a href="https://infosec.space/tags/RaspberryPi" class="mention hashtag" rel="nofollow noopener" target="_blank">#RaspberryPi</a> when it comes to <a href="https://infosec.space/tags/documentation" class="mention hashtag" rel="nofollow noopener" target="_blank">#documentation</a>. <ul><li>Like most of the time they just randomly release some <a href="https://infosec.space/tags/Android" class="mention hashtag" rel="nofollow noopener" target="_blank">#Android</a> / <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> image and tell buyers to 'feck off' when it comes to reproduceable builds or mainline <a href="https://infosec.space/tags/LinuxKernel" class="mention hashtag" rel="nofollow noopener" target="_blank">#LinuxKernel</a> support…</li></ul>Whereas even some "old" 14nm node'd <a href="https://infosec.space/tags/ARMv5r11" class="mention hashtag" rel="nofollow noopener" target="_blank">#ARMv5r11</a> or <a href="https://infosec.space/tags/ARMv7" class="mention hashtag" rel="nofollow noopener" target="_blank">#ARMv7</a> / <a href="https://infosec.space/tags/ARM64" class="mention hashtag" rel="nofollow noopener" target="_blank">#ARM64</a> we'd all expect something that delivers a desktop @ 2W TDP like the <a href="https://www.intel.com/content/www/us/en/products/sku/93361/intel-atom-x5z8350-processor-2m-cache-up-to-1-92-ghz/specifications.html" rel="nofollow noopener" target="_blank">Intel Atom x5-Z8350</a> did over a decade ago!

KalvinThese two Fediverse servers are the subject of civil proceedings initiated by me due to concerns related to interpersonal interactions, user dignity, accountability, and transparency.- `lemmy.world` - `wizard.casa` The actions I am undertaking include: - Monitoring their activities - Documenting their behavior - Collaborating with authorities - Collecting relevant informationThe purpose of these actions is to address issues related to my rights and well-being and to ensure accountability from the server maintainers. <a href="https://liberica.kupi.my/tags/Fediverse" class="mention hashtag" rel="nofollow noopener" target="_blank">#Fediverse</a> <a href="https://liberica.kupi.my/tags/LemmyWorld" class="mention hashtag" rel="nofollow noopener" target="_blank">#LemmyWorld</a> <a href="https://liberica.kupi.my/tags/WizardCasa" class="mention hashtag" rel="nofollow noopener" target="_blank">#WizardCasa</a> <a href="https://liberica.kupi.my/tags/Accountability" class="mention hashtag" rel="nofollow noopener" target="_blank">#Accountability</a> <a href="https://liberica.kupi.my/tags/Transparency" class="mention hashtag" rel="nofollow noopener" target="_blank">#Transparency</a> <a href="https://liberica.kupi.my/tags/UserRights" class="mention hashtag" rel="nofollow noopener" target="_blank">#UserRights</a> <a href="https://liberica.kupi.my/tags/CivilAction" class="mention hashtag" rel="nofollow noopener" target="_blank">#CivilAction</a> <a href="https://liberica.kupi.my/tags/Justice" class="mention hashtag" rel="nofollow noopener" target="_blank">#Justice</a> <a href="https://liberica.kupi.my/tags/Dignity" class="mention hashtag" rel="nofollow noopener" target="_blank">#Dignity</a> <a href="https://liberica.kupi.my/tags/InterpersonalAbuse" class="mention hashtag" rel="nofollow noopener" target="_blank">#InterpersonalAbuse</a> <a href="https://liberica.kupi.my/tags/Monitoring" class="mention hashtag" rel="nofollow noopener" target="_blank">#Monitoring</a> <a href="https://liberica.kupi.my/tags/Documentation" class="mention hashtag" rel="nofollow noopener" target="_blank">#Documentation</a> <a href="https://liberica.kupi.my/tags/Authorities" class="mention hashtag" rel="nofollow noopener" target="_blank">#Authorities</a> <a href="https://liberica.kupi.my/tags/WellBeing" class="mention hashtag" rel="nofollow noopener" target="_blank">#WellBeing</a> <a href="https://liberica.kupi.my/tags/SocialMedia" class="mention hashtag" rel="nofollow noopener" target="_blank">#SocialMedia</a> <a href="https://liberica.kupi.my/tags/Decentralized" class="mention hashtag" rel="nofollow noopener" target="_blank">#Decentralized</a> <a href="https://liberica.kupi.my/tags/Ethics" class="mention hashtag" rel="nofollow noopener" target="_blank">#Ethics</a> <a href="https://liberica.kupi.my/tags/LegalAction" class="mention hashtag" rel="nofollow noopener" target="_blank">#LegalAction</a> <a href="https://liberica.kupi.my/tags/CommunitySafety" class="mention hashtag" rel="nofollow noopener" target="_blank">#CommunitySafety</a> <a href="https://liberica.kupi.my/tags/Responsibility" class="mention hashtag" rel="nofollow noopener" target="_blank">#Responsibility</a>

Frontend DogmaAccessibility Statements Are Not Legal Contracts—They’re Value Signals, by (not on Mastodon or Bluesky):<a href="https://pedalpoint.com/2025/08/accessibility-statements-are-not-legal-contracts-theyre-value-signals/" rel="nofollow noopener" translate="no" target="_blank">https://pedalpoint.com/2025/08/accessibility-statements-are-not-legal-contracts-theyre-value-signals/</a><a href="https://mas.to/tags/accessibility" class="mention hashtag" rel="nofollow noopener" target="_blank">#accessibility</a> <a href="https://mas.to/tags/documentation" class="mention hashtag" rel="nofollow noopener" target="_blank">#documentation</a> <a href="https://mas.to/tags/compliance" class="mention hashtag" rel="nofollow noopener" target="_blank">#compliance</a> <a href="https://mas.to/tags/legal" class="mention hashtag" rel="nofollow noopener" target="_blank">#legal</a>

Kevin Karhan :verified:<a href="https://infosec.exchange/@JessTheUnstill" class="u-url mention" rel="nofollow noopener" target="_blank">@JessTheUnstill</a> <a href="https://mastodon.social/@GreenRoc" class="u-url mention" rel="nofollow noopener" target="_blank">@GreenRoc</a> Personally I wish for <a href="https://infosec.space/tags/RightToRepair" class="mention hashtag" rel="nofollow noopener" target="_blank">#RightToRepair</a> to be mandated including access to <a href="https://infosec.space/tags/schematics" class="mention hashtag" rel="nofollow noopener" target="_blank">#schematics</a>, <a href="https://infosec.space/tags/parts" class="mention hashtag" rel="nofollow noopener" target="_blank">#parts</a>, <a href="https://infosec.space/tags/firmware" class="mention hashtag" rel="nofollow noopener" target="_blank">#firmware</a> and <a href="https://infosec.space/tags/tools" class="mention hashtag" rel="nofollow noopener" target="_blank">#tools</a> needed so <a href="https://infosec.space/tags/manufacturers" class="mention hashtag" rel="nofollow noopener" target="_blank">#manufacturers</a> would be forced to actually give a shit and build <a href="https://infosec.space/tags/RepairableTech" class="mention hashtag" rel="nofollow noopener" target="_blank">#RepairableTech</a>... <ul><li>Then again the <a href="https://infosec.space/tags/PerverseIncentives" class="mention hashtag" rel="nofollow noopener" target="_blank">#PerverseIncentives</a> of <a href="https://infosec.space/tags/capitalism" class="mention hashtag" rel="nofollow noopener" target="_blank">#capitalism</a> punish <a href="https://infosec.space/tags/HonestMerchants" class="mention hashtag" rel="nofollow noopener" target="_blank">#HonestMerchants</a> and <a href="https://infosec.space/tags/RepairableDesign" class="mention hashtag" rel="nofollow noopener" target="_blank">#RepairableDesign</a> because manufacturers don't give a shit about supporting their devices and work against their interests of the buyers!</li></ul>Remember: Most folks are mere <a href="https://infosec.space/tags/consumers" class="mention hashtag" rel="nofollow noopener" target="_blank">#consumers</a>, not <a href="https://infosec.space/tags/owners" class="mention hashtag" rel="nofollow noopener" target="_blank">#owners</a> and espechally not <a href="https://infosec.space/tags/tinkerers" class="mention hashtag" rel="nofollow noopener" target="_blank">#tinkerers</a>! <ul><li><a href="https://infosec.exchange/@JessTheUnstill/115168865368720873" rel="nofollow noopener" target="_blank">THIS</a> is why <a href="https://infosec.space/tags/RaspberryPi" class="mention hashtag" rel="nofollow noopener" target="_blank">#RaspberryPi</a> were able to basically monopolize the <a href="https://infosec.space/tags/ARM" class="mention hashtag" rel="nofollow noopener" target="_blank">#ARM</a> - <a href="https://infosec.space/tags/SBC" class="mention hashtag" rel="nofollow noopener" target="_blank">#SBC</a> market for tinkerers because they are the only one's that actually build devices that just work out of the box and have <a href="https://infosec.space/tags/documentation" class="mention hashtag" rel="nofollow noopener" target="_blank">#documentation</a>, whereas all the competitors just fart out some PCBs and some hacked-up images and then tell people to 'go fuck themselves' when they don't want to just buy but do something with it!</li></ul>

Kevin Karhan :verified:<a href="https://mstdn.jp/@landley" class="u-url mention" rel="nofollow noopener" target="_blank">@landley</a> <a href="https://fosstodon.org/@lmemsm" class="u-url mention" rel="nofollow noopener" target="_blank">@lmemsm</a> thx. <ul><li>I really appreciate your efforts and espechally <a href="https://infosec.space/tags/documentation" class="mention hashtag" rel="nofollow noopener" target="_blank">#documentation</a> as it makes it so much easier... </li></ul>There's a reason I only considered <a href="https://github.com/OS-1337/OS1337/blob/main/docu/ideas/architectures.tsv" rel="nofollow noopener" target="_blank">architectures</a> to build <a href="https://infosec.space/@OS1337" class="u-url mention" rel="nofollow noopener" target="_blank">@OS1337</a> against that are "obtainable" and I'll prioritize those that I have in my possession and that can be cheaply acquired, which <a href="https://github.com/OS-1337/OS1337/blob/8a2c97ae054561ba4924cbec3e2b363c645a207d/docu/ideas/architectures.tsv" rel="nofollow noopener" target="_blank">as of writing</a> are about 12 build targets across 5 distinct ISAs ( <a href="https://infosec.space/tags/i486" class="mention hashtag" rel="nofollow noopener" target="_blank">#i486</a> and up, <a href="https://infosec.space/tags/amd64" class="mention hashtag" rel="nofollow noopener" target="_blank">#amd64</a>, <a href="https://infosec.space/tags/ARMv5r11" class="mention hashtag" rel="nofollow noopener" target="_blank">#ARMv5r11</a>, <a href="https://infosec.space/tags/ARMv7" class="mention hashtag" rel="nofollow noopener" target="_blank">#ARMv7</a>, <a href="https://infosec.space/tags/ppc64" class="mention hashtag" rel="nofollow noopener" target="_blank">#ppc64</a>) , with only 1 (<a href="https://infosec.space/tags/i486SX" class="mention hashtag" rel="nofollow noopener" target="_blank">#i486SX</a>) being currently <a href="https://infosec.space/@kkarhan/115156067352618033" rel="nofollow noopener" target="_blank">in focus</a> and the next one being the <a href="https://infosec.space/tags/Pi0" class="mention hashtag" rel="nofollow noopener" target="_blank">#Pi0</a> / <a href="https://infosec.space/tags/Pi0W" class="mention hashtag" rel="nofollow noopener" target="_blank">#Pi0W</a> who's code will run (abeit not performant) on the <a href="https://infosec.space/tags/Pi0W2" class="mention hashtag" rel="nofollow noopener" target="_blank">#Pi0W2</a> as well... <ul><li>All 3 <a href="https://infosec.space/tags/PiZero" class="mention hashtag" rel="nofollow noopener" target="_blank">#PiZero</a>|s can be had for like €100 in total with shipping and SD-Cards so it's on-par with a useable <a href="https://infosec.space/tags/amd64" class="mention hashtag" rel="nofollow noopener" target="_blank">#amd64</a> machine like a <a href="https://infosec.space/tags/ThinClient" class="mention hashtag" rel="nofollow noopener" target="_blank">#ThinClient</a> with proper SSD and RAM...</li></ul>Also unlike any other <a href="https://infosec.space/tags/SBC" class="mention hashtag" rel="nofollow noopener" target="_blank">#SBC</a> manufacturer <a href="https://mastodon.social/@raspberry_pi" class="u-url mention" rel="nofollow noopener" target="_blank">@raspberry_pi</a> / <a href="https://infosec.space/tags/RaspberryPi" class="mention hashtag" rel="nofollow noopener" target="_blank">#RaspberryPi</a> actually write <a href="https://www.raspberrypi.com/documentation/computers/linux_kernel.html#kernel" rel="nofollow noopener" target="_blank">proper</a> <a href="https://infosec.space/tags/documentation" class="mention hashtag" rel="nofollow noopener" target="_blank">#documentation</a> and not just fart out some random bootable image file and tell users to feck off!<a href="https://infosec.space/tags/OS1337" class="mention hashtag" rel="nofollow noopener" target="_blank">#OS1337</a>

ariI really enjoyed learning something by reading <a href="https://chaos.social/tags/documentation" class="mention hashtag" rel="nofollow noopener" target="_blank">#documentation</a> today.> SELECT * FROM a JOIN b USING (id);as a shorthand for > SELECT * FROM a JOIN b WHERE a.id=b.id;It's one of the perks of getting older, isn't it?<a href="https://chaos.social/tags/TIL" class="mention hashtag" rel="nofollow noopener" target="_blank">#TIL</a> <a href="https://chaos.social/tags/postgres" class="mention hashtag" rel="nofollow noopener" target="_blank">#postgres</a> <a href="https://chaos.social/tags/SQL" class="mention hashtag" rel="nofollow noopener" target="_blank">#SQL</a>

☮ ♥ ♬ 🧑‍💻“Often, what I find most useful about these tools isn’t even writing <a href="https://ioc.exchange/tags/code" class="mention hashtag" rel="nofollow noopener" target="_blank">#code</a> but understanding it. When I recently had to navigate an unfamiliar <a href="https://ioc.exchange/tags/codebase" class="mention hashtag" rel="nofollow noopener" target="_blank">#codebase</a>, I asked for it to explain its basic <a href="https://ioc.exchange/tags/flow" class="mention hashtag" rel="nofollow noopener" target="_blank">#flow</a>. The AI generated a <a href="https://ioc.exchange/tags/flowchart" class="mention hashtag" rel="nofollow noopener" target="_blank">#flowchart</a> of how the major components fit together, saving me an entire afternoon of spelunking through the code.”A sign of <a href="https://ioc.exchange/tags/documentation" class="mention hashtag" rel="nofollow noopener" target="_blank">#documentation</a> deficiency. <a href="https://ioc.exchange/tags/VibeCoding" class="mention hashtag" rel="nofollow noopener" target="_blank">#VibeCoding</a> / <a href="https://ioc.exchange/tags/AI" class="mention hashtag" rel="nofollow noopener" target="_blank">#AI</a> <<a href="https://www.theverge.com/ai-artificial-intelligence/767973/vibe-coding-ai-future-end-evolution" rel="nofollow noopener" translate="no" target="_blank">https://www.theverge.com/ai-artificial-intelligence/767973/vibe-coding-ai-future-end-evolution</a>> (paywall) / <<a href="https://archive.md/6L0Sn" rel="nofollow noopener" translate="no" target="_blank">https://archive.md/6L0Sn</a>>

Kushal Das :python: :tor: 🇸🇪Can anyone point me to a good <a href="https://toots.dgplug.org/tags/documentation" class="mention hashtag" rel="nofollow noopener" target="_blank">#documentation</a> for <a href="https://toots.dgplug.org/tags/oauth" class="mention hashtag" rel="nofollow noopener" target="_blank">#oauth</a> which explains when to use personal tokens and when to use client credentials? Specially <a href="https://toots.dgplug.org/tags/security" class="mention hashtag" rel="nofollow noopener" target="_blank">#security</a> wise why it is a bad idea to use shared client credentials than allowing users to use tokens per user. @aaronpk maybe you have something ready :)I need to pass this information to a group of old age wise (but new in learning) developers.

Kevin Karhan :verified:<a href="https://soc.megatokyo.moe/users/wyatt" class="u-url mention" rel="nofollow noopener" target="_blank">@wyatt</a> <a href="https://bitbang.social/@ActionRetro" class="u-url mention" rel="nofollow noopener" target="_blank">@ActionRetro</a> <a href="https://bitbang.social/@thisdoesnotcomp" class="u-url mention" rel="nofollow noopener" target="_blank">@thisdoesnotcomp</a> yeah, they have a shitton of issues.<ul><li>But certainly none of their "competitors" don't even halfass the fundamentals like <a href="https://infosec.space/tags/documentation" class="mention hashtag" rel="nofollow noopener" target="_blank">#documentation</a>. </li></ul>And to be honest, most folks ain't gonna bother to go all <a href="https://mastodon.social/@geerlingguy" class="u-url mention" rel="nofollow noopener" target="_blank">@geerlingguy</a> - style into the weeds and build their own kernel and stuff - certainly not for single-digit €/$ price differences!<ul><li>And now we all know why my <a href="https://infosec.space/tags/BananaPiZeroM2" class="mention hashtag" rel="nofollow noopener" target="_blank">#BananaPiZeroM2</a> is unused but I love my <a href="https://infosec.space/tags/Pi0W" class="mention hashtag" rel="nofollow noopener" target="_blank">#Pi0W</a> & <a href="https://infosec.space/tags/Pi0W2" class="mention hashtag" rel="nofollow noopener" target="_blank">#Pi0W2</a>|s...</li></ul>

KattniI'm super excited to share my first open source project: MkDocs PO I18n! I designed tooling to handle translations of MkDocs documentation, using PO files, and hosted on Read the Docs. This project came out of a project I'm doing with BeeWare to consider switching the documentation from Sphinx to MkDocs. The BeeWare tutorial is available in a number of languages, so translations using the existing workflow were a necessary feature if the switch were going to happen. It initially seemed like we weren't going to be able to move forward with it, but I'm not one to give up easily. I couldn't find any viable options, so I wrote my own! I've written a blog post on how to use it: <a href="https://kattni.com/mkdocs-po-i18n-mkdocs-translations-with-po-files-and-read-the-docs" rel="nofollow noopener" translate="no" target="_blank">https://kattni.com/mkdocs-po-i18n-mkdocs-translations-with-po-files-and-read-the-docs</a>You can find the project here: <a href="https://github.com/kattni/mkdocs-po-i18n/" rel="nofollow noopener" translate="no" target="_blank">https://github.com/kattni/mkdocs-po-i18n/</a>I've also published documentation for it to RTD: <a href="https://mkdocs-po-i18n.readthedocs.io/en/latest/" rel="nofollow noopener" translate="no" target="_blank">https://mkdocs-po-i18n.readthedocs.io/en/latest/</a><a href="https://kattstodon.com/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSource</a> <a href="https://kattstodon.com/tags/Documentation" class="mention hashtag" rel="nofollow noopener" target="_blank">#Documentation</a>

Kevin Karhan :verified:<a href="https://snug.moe/@lumi" class="u-url mention" rel="nofollow noopener" target="_blank">@lumi</a> <a href="https://shrimp.starlightnet.work/@hazel" class="u-url mention" rel="nofollow noopener" target="_blank">@hazel</a> yes, it's easier to avoid:<ul><li>Just use <a href="https://infosec.space/tags/IRC" class="mention hashtag" rel="nofollow noopener" target="_blank">#IRC</a> & <a href="https://infosec.space/tags/Mumble" class="mention hashtag" rel="nofollow noopener" target="_blank">#Mumble</a> instead!</li><li>As for <a href="https://infosec.space/tags/documentation" class="mention hashtag" rel="nofollow noopener" target="_blank">#documentation</a>, <a href="https://infosec.space/tags/MkDocs" class="mention hashtag" rel="nofollow noopener" target="_blank">#MkDocs</a>-Material and for project managment, <a href="https://infosec.space/tags/GitLab" class="mention hashtag" rel="nofollow noopener" target="_blank">#GitLab</a> works fine.</li></ul>I merely use <a href="https://infosec.space/tags/GitHub" class="mention hashtag" rel="nofollow noopener" target="_blank">#GitHub</a> because they ain't got impacted by <a href="https://infosec.space/tags/DDoS" class="mention hashtag" rel="nofollow noopener" target="_blank">#DDoS</a> and their moderation team actually cares, and I don't expect other platforms to be able and willing to do the same.<ul><li>If there is a convenient way to only use it to <a href="https://infosec.space/tags/host" class="mention hashtag" rel="nofollow noopener" target="_blank">#host</a> a copy of a repo & files as a "slave" (fork) repo (similar to <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a>) I'll gladly consider that.</li><li>It's just not the highest priority rn as I'm preoccupied with more pressing issues.</li></ul>

RegistrarTrekWhat does a jet have to do with managing previously unmanaged collections? <a href="https://world.museumsprojekte.de/wp-content/uploads/2025/08/cockpit-6622086_1280.jpg" rel="nofollow noopener" target="_blank"></a>Photo by Andreas Glöckner via Pixabay Simple answer:Nothing.More complex answer:I am in the process of translating <a href="https://www.bloomsbury.com/us/managing-previously-unmanaged-collections-9781538190630/" rel="nofollow noopener" target="_blank">the book </a>into German and sometimes there are hiccups. In chapter 4, I talk about the difficulties of enforcing access policies for your storage area. A process which, as we all know, comes with all sorts of difficulties, the problem of taking the key from someone being a humiliating gesture in our Western culture being not the least of it.In the English original, there is the sentence:“Enforce the access policy with the three ps: persistence, patience, and politeness.”Needless to say, such sentences don’t translate well. Usually you just rephrase them and let go of the idea that you can find three words starting with the same letter in the other language. However, I think I did find a way this morning:“Halten Sie mit „Drei G“ an Ihren Zugangsbeschränkungen fest: mit Geradlinigkeit, Geduld und Gutem Benehmen.”Finding three words starting with the letter G with the same meaning like the original (although the third one is cheating a bit, using two words) was already a big win. But the even bigger win was that this way I now have the double meaning of 3 G in it, alluding to the <a href="https://www.youtube.com/watch?v=iWY3-1gOrxk&t=32s" rel="nofollow noopener" target="_blank">g-forces</a> in physics.I could of course take that analogy and run with it, saying that when we change longstanding processes and habits like we inevitably do when we start improving things in our collections, it means that we accelerate things and take people out of where they are used to go and expecting to go. And as we know from physics, if we accelerate things, a force is applied to the one being accelerated, which can have unpleasant side effects.But I don’t want to overburden that little sentence. Instead, just imagine me giggling slightly when you come across it reading the book. 🙂Angela<a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://world.museumsprojekte.de/tag/accesscontrol/" target="_blank">#AccessControl</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://world.museumsprojekte.de/tag/collections-management/" target="_blank">#collectionsManagement</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://world.museumsprojekte.de/tag/documentation/" target="_blank">#documentation</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://world.museumsprojekte.de/tag/museum/" target="_blank">#museum</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://world.museumsprojekte.de/tag/museumdocumentation-2/" target="_blank">#MuseumDocumentation</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://world.museumsprojekte.de/tag/registrar/" target="_blank">#registrar</a>

Paolo AmorosoDave Gauer <a href="https://mastodon.art/@ratfactor" class="u-url mention" rel="nofollow noopener" target="_blank">@ratfactor</a> explains why he reads technical books. He expresses very well motivations I share but couldn't articulate, such as books having a single voice and stylistic convention.<a href="https://ratfactor.com/b/technical-books" rel="nofollow noopener" translate="no" target="_blank">https://ratfactor.com/b/technical-books</a><a href="https://oldbytes.space/tags/books" class="mention hashtag" rel="nofollow noopener" target="_blank">#books</a> <a href="https://oldbytes.space/tags/reading" class="mention hashtag" rel="nofollow noopener" target="_blank">#reading</a> <a href="https://oldbytes.space/tags/documentation" class="mention hashtag" rel="nofollow noopener" target="_blank">#documentation</a>

Paolo AmorosoUsing LLMs to chat with books and documents? That's so 1978.In the 1970s the HELPSYS facility of Interlisp-10 let you interrogate the 700+ pages Interlisp Reference Manual via an English like syntax. You could run queries on topics and system functions such as <code>TELL ME ABOUT EVAL</code> or <code>TELL ME ABOUT THE 2ND ARG OF CHANGEPROP</code> and HELPSYS would print the relevant information or section of the manual. Here's an example session from the 1978 edition of the manual:<a href="https://www.softwarepreservation.org/projects/LISP/interlisp/Interlisp-Oct_1978.pdf#page=474" rel="nofollow noopener" translate="no" target="_blank">https://www.softwarepreservation.org/projects/LISP/interlisp/Interlisp-Oct_1978.pdf#page=474</a>Interlisp-10 was the Interlisp implementation for the PDP-10.<a href="https://oldbytes.space/tags/interlisp" class="mention hashtag" rel="nofollow noopener" target="_blank">#interlisp</a> <a href="https://oldbytes.space/tags/documentation" class="mention hashtag" rel="nofollow noopener" target="_blank">#documentation</a> <a href="https://oldbytes.space/tags/lisp" class="mention hashtag" rel="nofollow noopener" target="_blank">#lisp</a> <a href="https://oldbytes.space/tags/retrocomputing" class="mention hashtag" rel="nofollow noopener" target="_blank">#retrocomputing</a>

Recent searches

Search options

Administered by:

Server stats:

#documentation