Miguel Afonso Caetano<p>"When evaluating documentation’s role, consider these broader strategic questions:</p><p>- Strategic positioning: How does documentation support the company’s core strategic approach?</p><p>- Competitive advantage: Can documentation create or enhance the company’s unique market position? What type of documentation does the competition offer?</p><p>- Value proposition: How does documentation contribute to the product’s overall value for customers?</p><p>- Knowledge management: How does documentation support internal knowledge retention and transfer?</p><p>- Customer lifecycle: How can documentation improve customer acquisition, retention, and satisfaction?"</p><p><a href="https://www.thegooddocsproject.dev/blog/making-business-base-know-company-goals" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">thegooddocsproject.dev/blog/ma</span><span class="invisible">king-business-base-know-company-goals</span></a></p><p><a href="https://tldr.nettime.org/tags/TechnicalWriting" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>TechnicalWriting</span></a> <a href="https://tldr.nettime.org/tags/Documentation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Documentation</span></a> <a href="https://tldr.nettime.org/tags/SoftwareDocumentation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SoftwareDocumentation</span></a> <a href="https://tldr.nettime.org/tags/TechnicalCommunication" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>TechnicalCommunication</span></a></p>
Recent searches
No recent searches
Search options
Not available on writing.exchange.
writing.exchange is one of the many independent Mastodon servers you can use to participate in the fediverse.
A small, intentional community for poets, authors, and every kind of writer.
Administered by:
Server stats:
326active users
writing.exchange: About · Profiles directory · Privacy policy
Mastodon: About · Get the app · Keyboard shortcuts · View source code · v4.3.7
#documentation
4 posts · 2 participants · 0 posts today
Miguel Afonso Caetano<p>"When evaluating documentation’s role, consider these broader strategic questions:</p><p>- Strategic positioning: How does documentation support the company’s core strategic approach?</p><p>- Competitive advantage: Can documentation create or enhance the company’s unique market position? What type of documentation does the competition offer?</p><p>- Value proposition: How does documentation contribute to the product’s overall value for customers?</p><p>- Knowledge management: How does documentation support internal knowledge retention and transfer?</p><p>- Customer lifecycle: How can documentation improve customer acquisition, retention, and satisfaction?"</p><p><a href="https://www.thegooddocsproject.dev/blog/making-business-base-know-company-goals" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">thegooddocsproject.dev/blog/ma</span><span class="invisible">king-business-base-know-company-goals</span></a></p><p><a href="https://tldr.nettime.org/tags/TechnicalWriting" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>TechnicalWriting</span></a> <a href="https://tldr.nettime.org/tags/Documentation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Documentation</span></a> <a href="https://tldr.nettime.org/tags/SoftwareDocumentation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SoftwareDocumentation</span></a> <a href="https://tldr.nettime.org/tags/TechnicalCommunication" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>TechnicalCommunication</span></a></p>
💧🌏 Greg Cocks<p>GEDTM30 – A Global 1-Arc-Second (~30m) Digital Terrain Model (DTM)<br>--<br><a href="https://github.com/openlandmap/GEDTM30" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="">github.com/openlandmap/GEDTM30</span><span class="invisible"></span></a> <-- shared GitHub repository<br>--<br><a href="https://techhub.social/tags/GIS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>GIS</span></a> <a href="https://techhub.social/tags/spatial" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>spatial</span></a> <a href="https://techhub.social/tags/mapping" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>mapping</span></a> <a href="https://techhub.social/tags/opendata" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>opendata</span></a> <a href="https://techhub.social/tags/global" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>global</span></a> <a href="https://techhub.social/tags/DTM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DTM</span></a> <a href="https://techhub.social/tags/GEDTM30" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>GEDTM30</span></a> <a href="https://techhub.social/tags/GitHub" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>GitHub</span></a> <a href="https://techhub.social/tags/30m" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>30m</span></a> <a href="https://techhub.social/tags/landsurface" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>landsurface</span></a> <a href="https://techhub.social/tags/parameters" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>parameters</span></a> <a href="https://techhub.social/tags/documentation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>documentation</span></a> <a href="https://techhub.social/tags/hydrology" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>hydrology</span></a> <a href="https://techhub.social/tags/remotesensing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>remotesensing</span></a> <a href="https://techhub.social/tags/earthobservation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>earthobservation</span></a> <a href="https://techhub.social/tags/slope" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>slope</span></a> <a href="https://techhub.social/tags/geomorphons" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>geomorphons</span></a> <a href="https://techhub.social/tags/hillshade" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>hillshade</span></a> <a href="https://techhub.social/tags/geomorphometry" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>geomorphometry</span></a> <a href="https://techhub.social/tags/geomorphology" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>geomorphology</span></a> <a href="https://techhub.social/tags/topography" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>topography</span></a> <a href="https://techhub.social/tags/Equi7" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Equi7</span></a> <a href="https://techhub.social/tags/terrainheight" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>terrainheight</span></a> <a href="https://techhub.social/tags/DigitalTerrainModel" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DigitalTerrainModel</span></a> <a href="https://techhub.social/tags/landform" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>landform</span></a></p>
💧🌏 Greg Cocks<p>RiverREM - Generating River Relative Elevation Model (REM) Visualisations <br>--<br><a href="https://github.com/OpenTopography/RiverREM" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/OpenTopography/Rive</span><span class="invisible">rREM</span></a> <-- shared GitHub repository<br>--<br><a href="https://opentopography.github.io/RiverREM/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">opentopography.github.io/River</span><span class="invisible">REM/</span></a> <-- shared documentation<br>--<br><a href="https://opentopography.org/blog/new-package-automates-river-relative-elevation-model-rem-generation" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">opentopography.org/blog/new-pa</span><span class="invisible">ckage-automates-river-relative-elevation-model-rem-generation</span></a> <-- shared Open Topography blog post about RiverREM<br>--<br>H/T Heidi Luchsinger / Open Topography<br>[this post should not be considered as an endorsement of this product aka caveat emptor]<br><a href="https://techhub.social/tags/GIS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>GIS</span></a> <a href="https://techhub.social/tags/spatial" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>spatial</span></a> <a href="https://techhub.social/tags/mapping" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>mapping</span></a> <a href="https://techhub.social/tags/remotesensing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>remotesensing</span></a> <a href="https://techhub.social/tags/earthobservation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>earthobservation</span></a> <a href="https://techhub.social/tags/Python" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Python</span></a> <a href="https://techhub.social/tags/LiDAR" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>LiDAR</span></a> <a href="https://techhub.social/tags/RiverREM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>RiverREM</span></a> <a href="https://techhub.social/tags/visualisation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>visualisation</span></a> <a href="https://techhub.social/tags/hydrology" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>hydrology</span></a> <a href="https://techhub.social/tags/water" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>water</span></a> <a href="https://techhub.social/tags/river" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>river</span></a> <a href="https://techhub.social/tags/rivervalley" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>rivervalley</span></a> <a href="https://techhub.social/tags/floodplain" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>floodplain</span></a> <a href="https://techhub.social/tags/terraces" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>terraces</span></a> <a href="https://techhub.social/tags/GitHub" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>GitHub</span></a> <a href="https://techhub.social/tags/opensource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>opensource</span></a> <a href="https://techhub.social/tags/opendata" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>opendata</span></a> <a href="https://techhub.social/tags/DEM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DEM</span></a> <a href="https://techhub.social/tags/REM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>REM</span></a> <a href="https://techhub.social/tags/model" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>model</span></a> <a href="https://techhub.social/tags/modeling" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>modeling</span></a> <a href="https://techhub.social/tags/RiverRelativeModel" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>RiverRelativeModel</span></a> <a href="https://techhub.social/tags/documentation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>documentation</span></a> <a href="https://techhub.social/tags/tutorial" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>tutorial</span></a> <a href="https://techhub.social/tags/learning" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>learning</span></a> <a href="https://techhub.social/tags/tool" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>tool</span></a> <a href="https://techhub.social/tags/elevation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>elevation</span></a> <a href="https://techhub.social/tags/raster" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>raster</span></a> <a href="https://techhub.social/tags/sinuosity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>sinuosity</span></a> <a href="https://techhub.social/tags/drainage" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>drainage</span></a></p>
:mastodon: Mike Amundsen<p>What's wrong with AI-generated docs <a href="https://buff.ly/xAp81oX" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="">buff.ly/xAp81oX</span><span class="invisible"></span></a></p><p> let me tell you what’s wrong with docs and docs sets entirely generated by LLMs. </p><p><a href="https://mastodon.social/tags/api360" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>api360</span></a> <a href="https://mastodon.social/tags/genAI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>genAI</span></a> <a href="https://mastodon.social/tags/documentation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>documentation</span></a></p>
Kevin Karhan :verified:<p><a href="https://infosec.space/tags/discord" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>discord</span></a> <a href="https://www.youtube.com/watch?v=2LhiCP8AQWs" rel="nofollow noopener noreferrer" target="_blank"><em>IS LITERALLY THE PROBLEM!</em></a></p><ul><li><p>It's worse than any <a href="https://infosec.space/tags/IRC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IRC</span></a>, <a href="https://infosec.space/tags/Mumble" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Mumble</span></a> or even the old <a href="https://infosec.space/tags/TeamSpeak" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>TeamSpeak</span></a> & <a href="https://infosec.space/tags/Skype" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Skype</span></a> for that matter.</p></li><li><p>It combines the disadvantages of <a href="https://infosec.space/tags/Forum" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Forum</span></a>, <a href="https://infosec.space/tags/paywalled" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>paywalled</span></a> <a href="https://infosec.space/tags/documentation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>documentation</span></a>, <a href="https://infosec.space/tags/chat" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>chat</span></a> and <a href="https://infosec.space/tags/voicechat" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>voicechat</span></a> with 0 redeeming qualities (unlike <a href="https://infosec.space/tags/Zulip" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Zulip</span></a> & Mumble & <a href="https://infosec.space/tags/XMPP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>XMPP</span></a>+<a href="https://infosec.space/tags/OMEMO" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>OMEMO</span></a>) it's just an <a href="https://infosec.space/tags/InformationBlackhole" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>InformationBlackhole</span></a>!</p></li></ul><p>I'm shure fecking <a href="https://infosec.space/tags/dread" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>dread</span></a> has better moderation and I'd rather use <a href="https://infosec.space/tags/MicrosoftTeams" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>MicrosoftTeams</span></a> + <a href="https://infosec.space/tags/Slack" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Slack</span></a> cuz those at least have proper <a href="https://infosec.space/tags/moderation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>moderation</span></a> tools.</p><ul><li>And I'd rather subscribe to the <a href="https://infosec.space/tags/LKML" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>LKML</span></a> and see my inbox getting hosed than using any shitty <a href="https://infosec.space/tags/SaaS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SaaS</span></a>!</li></ul><p>Case in point: I'd rather <a href="https://infosec.space/tags/SelfHost" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SelfHost</span></a> all my comms infrastructure than to ever use something like Discord or any other <a href="https://infosec.space/tags/GDPR" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>GDPR</span></a>-violating SaaS that is just enshittification.</p><p>I'd rather recommend people to instead choose a tool that does <em>everything but horrible</em> to go with multiple <em>smaller & good tools</em></p><ul><li>Public Chat? IRC!</li><li>Group Voicechat? Mumble.</li><li><a href="https://infosec.space/tags/Documentation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Documentation</span></a>? <a href="https://infosec.space/tags/mkDocs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>mkDocs</span></a>-material.</li><li>1:1 Chats? XMPP+OMEMO.</li><li>E2EE Group Chats? <a href="https://infosec.space/tags/deltaChat" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>deltaChat</span></a>.</li><li>E2EE Calls? <a href="https://infosec.space/tags/WebCall" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>WebCall</span></a>.</li><li>Filehosting? <a href="https://infosec.space/tags/IPFS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IPFS</span></a>, <a href="https://infosec.space/tags/BitTorrent" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>BitTorrent</span></a>, oshi.at, etc. ...</li><li>…</li></ul><p>Check <span class="h-card" translate="no"><a href="https://mas.to/@alternativeto" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>alternativeto</span></a></span> and <span class="h-card" translate="no"><a href="https://mastodon.social/@european_alternatives" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>european_alternatives</span></a></span> for options.</p>
Third spruce tree on the left<p>Everytime I have to write "Yeah, about this button. it doesn't do anything. Don't click it. The developers didn't finish that feature in time but were too lazy to hide it before we shipped" I die a little bit inside. <a href="https://mas.to/tags/TechnicalWriting" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>TechnicalWriting</span></a> <a href="https://mas.to/tags/documentation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>documentation</span></a></p>
Plone<p>Ujjwal Kala and Steve Piercy <span class="h-card" translate="no"><a href="https://fosstodon.org/@stevepiercy" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>stevepiercy</span></a></span> discuss Triple D: Documentation-Driven Development <a href="https://plone.social/tags/plone" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>plone</span></a> <a href="https://plone.social/tags/plone6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>plone6</span></a> <a href="https://plone.social/tags/wpd2025" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>wpd2025</span></a> <a href="https://plone.social/tags/CMS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CMS</span></a> <a href="https://plone.social/tags/Python" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Python</span></a> <a href="https://plone.social/tags/React" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>React</span></a> <a href="https://plone.social/tags/volto" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>volto</span></a> <a href="https://plone.social/tags/opensource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>opensource</span></a> <a href="https://plone.social/tags/community" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>community</span></a> <a href="https://plone.social/tags/documentation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>documentation</span></a> <a href="https://youtu.be/eu7ypPPKZCg" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="">youtu.be/eu7ypPPKZCg</span><span class="invisible"></span></a></p>
Marijke Luttekes<p>Documentation complaints.</p><p>The Curse of Knowledge is real in documentation; even big and pricey ecosystems skip basic information.</p><p>Two examples I ran into this morning:</p><p>1. GitHub's CODEOWNERS documentation does not explicitly mention where to create the file.</p><p><a href="https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">docs.github.com/en/repositorie</span><span class="invisible">s/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners</span></a></p><p>2. NPM's docs do not explain allowed characters in package names.</p><p><a href="https://docs.npmjs.com/package-name-guidelines" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">docs.npmjs.com/package-name-gu</span><span class="invisible">idelines</span></a></p><p><a href="https://fosstodon.org/tags/WebDev" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>WebDev</span></a> <a href="https://fosstodon.org/tags/documentation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>documentation</span></a></p>
fcr<p>new & final status update on 'moving image zines rdam': </p><p>The complete archive (355 videos) from 2005-2025 has been uploaded & is available on archive.org: <a href="https://archive.org/details/moving-image-zines-rdam?sort=-date" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">archive.org/details/moving-ima</span><span class="invisible">ge-zines-rdam?sort=-date</span></a></p><p>All videos are downloadable as high-quality files [mp4/h264 codec, 32 Mbit/s] and reusable under the Creative Commons Attribution-ShareAlike 4.0 International license.</p><p><a href="https://post.lurk.org/tags/video" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>video</span></a> <a href="https://post.lurk.org/tags/movingimage" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>movingimage</span></a> <a href="https://post.lurk.org/tags/diy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>diy</span></a> <a href="https://post.lurk.org/tags/rotterdam" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>rotterdam</span></a> <a href="https://post.lurk.org/tags/documentation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>documentation</span></a></p>
Dave Polaschek (he/him)<p>This morning, I finally checked in the code for turning a few lines of text like:</p><p>Today, Sat Apr 05, 2025<br />1000-1600 Cactus Sale<br />1100-1400 March at the Roundhouse</p><p>into text displayed on the eInk screen from WaveShare. As always, it took longer than expected, but it's mostly working. <a href="https://writing.exchange/tags/coding" class="mention hashtag" rel="tag">#<span>coding</span></a> <a href="https://writing.exchange/tags/documentation" class="mention hashtag" rel="tag">#<span>documentation</span></a> <a href="https://writing.exchange/tags/EverythingTakesLonger" class="mention hashtag" rel="tag">#<span>EverythingTakesLonger</span></a> <a href="https://writing.exchange/tags/YakShaving" class="mention hashtag" rel="tag">#<span>YakShaving</span></a> <a href="https://writing.exchange/tags/WoodWorking" class="mention hashtag" rel="tag">#<span>WoodWorking</span></a>… (1/3)</p>
Gytis Repečka<p>All developers I've met in my career in IT, who insisted <em>code is self-documenting</em> were exceptionally bad in documenting anything :blobcatreading:</p><p>While their code usually ran just fine, they could hardly ever explain how it worked or why it was structured that way to someone else, especially junior developers.</p><p>Comments and annotations exists for a reason.</p><p><a href="https://social.gyt.is/tags/developerlife" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>developerlife</span></a> <a href="https://social.gyt.is/tags/coding" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>coding</span></a> <a href="https://social.gyt.is/tags/documentation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>documentation</span></a></p>
El Duvelle<p>Good <a href="https://neuromatch.social/tags/Coding" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Coding</span></a> practices question for <a href="https://neuromatch.social/tags/Documentation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Documentation</span></a>:</p><p>Are there some general guidelines on what info to put in the comment at the top of each code file? Like date, author, basic description of what the code does? Maybe something about dependencies? Are there templates for this somewhere (e.g. for <a href="https://neuromatch.social/tags/Matlab" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Matlab</span></a> or <a href="https://neuromatch.social/tags/Python" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Python</span></a> if that matters)?</p>
RegistrarTrek<p><strong>Focus on what you CAN do, not what you CAN’T</strong></p><p>In these past few weeks it seems that there were so many horrible things happening that just making a list of them feels overwhelming and exhausting. Some of the decisions of the current U.S. government have an impact on the global level, others hit people personally, some of whom are close friends. And then, there are those who seem to target the very core of our profession, like the shutting down of the Institute of Museum and Library Services (IMLS) and the termination of grants already awarded by the National Endowment of the Humanities (NEH).</p><a href="https://world.museumsprojekte.de/wp-content/uploads/2017/08/ninja-155848_640.png" rel="nofollow noopener noreferrer" target="_blank"></a><p>It is hard not to lose all hope in this climate. And yet, aren’t we, as museum professionals, used to things not really looking pretty? Haven’t we battled budget and staff cuts before? Haven’t we brought uncomfortable truths in front of the eyes of our visitors and politicians before? Maybe the current crisis is not comparable to what we were confronted with before. But just as well, we are well trained in going against adversarial circumstances.</p><p>We have always done so with resilience, creativity, and, most of all, a sense of community. We might be spread out across the world and we might have spread ourselves thin by taking on too many responsibilities, but we are not alone. I have reached out to my network over the past few days to check in on some people, see how they are coping, and getting ideas of what can be done, because, in the end, focusing on what can’t be done never made anything better.</p><p>Turns out that John E. Simmons had already started collecting what can be done to prepare for what is coming at us in something we registrars love: A list. </p><p>I contributed a few of my thoughts to it and we also asked some more colleagues to add to it. What I am posting here today is by no means a comprehensive and finalized list of what to think about and what to do, but it is a start. Feel free to add more ideas in the comments section, just like we enhance it going forward.</p><p><strong><strong>What Can We Do?</strong></strong></p><p><strong>1. <strong>Apply the lessons that museums learned from Covid</strong></strong></p><ul><li>A museum should have a plan for suddenly shutting down or having to reduce staff for a prolonged long period of time.</li><li>The plan should include cross-training for all staff so that a reduced staff can keep the institution functioning and care for the collections. Every staff member should be trained to do tasks that are normally not part of their duties so that they can help in the event of a prolonged emergency.</li><li>The plan should include what the museum can do to remain a destination for visitors during a crisis. This might include regulating the number of visitors in the museum at the any one time during a pandemic, reducing or eliminating admission fees for visitors during a prolonged financial crisis, and how responsibilities could be handled by a reduced staff. It is worth noting that a recent study revealed that art museums that charge admission spend an average of $100 per visitor but attract smaller audiences than free museums, and that there are costs associated with collecting admission fees that may not be recovered by the fee. Details can be found at <a href="https://news.artnet.com/art-world/us-museums-visitors-report-2622358" rel="nofollow noopener noreferrer" target="_blank">https://news.artnet.com/art-world/us-museums-visitors-report-2622358</a>).</li></ul><p><strong>2. <strong>Prepare the collections for long-term, low maintenance storage</strong> </strong></p><p>by preparing the most sustainable and passive storage environment possible:</p><ul><li>Improve the effectiveness of the collection storage furniture, containers, and supports to protect the collections (e.g., replace gaskets on doors, eliminate acidic materials, reduce lighting and UV in storage).</li><li>Keep the collection in order (each object in its proper place in storage) at all times (do not allow a backlog of out-of-place objects to build up).</li><li>Improve environmental controls and environmental monitoring procedures.</li><li>Maintain storage environment equipment in good order (e.g. replace filters, service equipment regularly, replace aging HVAC systems).</li></ul><p><strong>3. <strong>Protect the databases</strong></strong></p><ul><li>Make sure that you have a fully up-to-date, readable copy of all important museum databases stored somewhere outside of the building, preferably in a hard format as well as electronic.</li><li>Make sure that both on-site and off-site databases are protected so they cannot be accessed by unauthorized personnel. Renew passwords and other project on a frequent, regular basis.</li><li>If the institution is forced to close, and you have a good backup copy, consider removing databases from the museum servers to protect confidential information.</li><li>When possible look into storing backup copies of your databases that are not only readable in a proprietary format of one vendor (who might be forced to hand your sensitive data over or might go out of business). If you database allows for it, export your important data as SQL tables or as comma separated values (.csv). Excel formats such as xlsx, xls, or ods are fine, too.</li><li>When possible move your sensitive data to trusted servers outside the U.S. that don’t belong to U.S. based companies who might be forced to hand your sensitive data over or delete your data. </li><li>As a rule of thumb: make access to your data for your trusted staff as easy as possible, but make deleting data from your database hard by setting up a robust rights management and whenever possible enable procedures to revert to earlier data entry points.</li></ul><p><strong>4. <strong>Update the institutional emergency preparedness plan</strong> </strong></p><p>to include procedures for coping with sudden, prolonged shutdowns of the building.</p><p><strong><strong>5. Stock up on critical supplies</strong></strong></p><p><strong>6. <strong>Download anything needed from federal websites</strong> </strong></p><p>(such as the NPS Museum Handbook and Conserve O Grams or IMLS reports) immediately, while the information is still available. Store this data in a safe place that is only accessible to authorized personnel and make deleting those resources as hard as possible.</p><p><strong>7. <strong>Keep in mind that most serious problem going forward will probably not be the cuts in federal funding</strong> </strong></p><p>to the NIH, NEA, NSF, IMLS, etc., because most of this money goes to projects which can be postponed or funded by other sources (such as donations). The most serious problem will be the lack of funds resulting from damage done to the economy due to a combination of the rising deficit, increasing unemployment (e.g., the mass reductions in the federal workforce and corresponding loss of jobs in sectors that serve the federal workforce), and decreased tax revenues due to tax cuts for the wealthy, tariffs on imports, and cuts to social services. In other words, the predicted problems with the US economy are far more likely to be a bigger problem for museums than the loss of federal grant funds.</p><p><strong><strong>Words of Cheer:</strong></strong></p><ul><li>Museums existed long before the IMLS and other federal granting agencies, so they can survive this period, although many worthy projects and much research will be halted unless alternative funding can be found.</li><li>With preparation, museums can survive the coming crisis as they have survived other crises. There will be staff reductions and loss of opportunities, but with any luck, the situation will change within a few years.</li><li>Take a good look at your policies and procedures and investigate new laws and executive orders you are confronted with. Laws that are passed in a great hurry often contain contradictions and loopholes. Often asking for clarifications by authorities can slow processes down and work to your advantage. Often stalling a process in good faith can be much more effective than open opposition which puts you and your staff at risk.</li><li>Be prepared to be patient. Lawsuits and judicial decisions challenging the proposed changes will take time to go through the courts.</li><li>In the longer term, climate change and its effects on museum operations, the economy, and the behavior of the public is the greatest challenge to the future of museums, so the present crisis should be used to prepare for the future.</li></ul><p><strong><strong>Best Advice:</strong></strong></p><p>If your institution does not have a plan for long-term survival during a financial crisis, the next pandemic, or climate change, get busy now to correct this deficit.</p><p><strong><strong>Helpful Information</strong></strong></p><ul><li>Learnings museums made from the Covid-19 pandemic, <a href="https://www.ne-mo.org/news-events/article/learnings-museums-made-from-the-covid-19-pandemic" rel="nofollow noopener noreferrer" target="_blank">https://www.ne-mo.org/news-events/article/learnings-museums-made-from-the-covid-19-pandemic</a></li></ul><ul><li>PEAS Resource Library (Promoting Exhibit Access and Safety), <a href="https://ncp.si.edu/PRICE-PEAS" rel="nofollow noopener noreferrer" target="_blank">https://ncp.si.edu/PRICE-PEAS</a></li></ul><ul><li>Snider, Julianne. 2024. The Wheel is Already Invented: Planning for the Next Crisis. <em>Collections: A Journal for Museum and Archives Professionals</em> 20(2):347-359, DOI: 10.1177/15501906241232309</li></ul><ul><li>Living in a Wild Future (Center for the Future of Museums blog), <a href="https://www.aam-us.org/2025/03/04/living-in-a-wild-future/" rel="nofollow noopener noreferrer" target="_blank">https://www.aam-us.org/2025/03/04/living-in-a-wild-future/</a></li></ul><ul><li>Decrease in Public Funding? A Worldwide Answer from Museums (ICOM), <a href="https://icom.museum/wp-content/uploads/2025/01/IRAPFM-A4-Format_FINAL.pdf" rel="nofollow noopener noreferrer" target="_blank">https://icom.museum/wp-content/uploads/2025/01/IRAPFM-A4-Format_FINAL.pdf</a></li></ul><ul><li>Susana Smith Bautista (2021)—<em>How to Close a Museum. A Practical Guide</em> (Rowman & Littlefield)</li></ul><ul><li>Here is an additional list of resources in case you have to close down your institution: <a href="https://world.museumsprojekte.de/wp-content/uploads/2025/04/ResourcesMuseumsClosing.pdf" rel="nofollow noopener noreferrer" target="_blank">https://world.museumsprojekte.de/wp-content/uploads/2025/04/ResourcesMuseumsClosing.pdf</a></li></ul><ul><li>Christopher J. Garthe (2023)—<em>The Sustainable Museum. How Museums Contribute to the Great Transformation</em> (Routledge)</li></ul><p><strong>Some more notes</strong></p><p>Share this resource freely with anyone you think needs to see this, no need to ask for permission. Add what applies to your special case. Let us know what we should add. Download, save, print, circulate.</p><p><a href="https://world.museumsprojekte.de/wp-content/uploads/2025/04/WhatCanWeDo-2.pdf" rel="nofollow noopener noreferrer" target="_blank">Download List as PDF</a></p><p>Registrar Trek is hosted on a server in Germany and following EU laws. I am currently looking through all the plug-ins I use to make sure none of them collects and shares any personal data with the U.S. Or, in fact, anybody. I always was mindful not to collect any personal information but will double-check again if everything is safe.</p><p>Hang on in there, you are not alone!</p><p><a rel="nofollow noopener noreferrer" class="hashtag u-tag u-category" href="https://world.museumsprojekte.de/tag/budgetcuts/" target="_blank">#BudgetCuts</a> <a rel="nofollow noopener noreferrer" class="hashtag u-tag u-category" href="https://world.museumsprojekte.de/tag/collections-management/" target="_blank">#collectionsManagement</a> <a rel="nofollow noopener noreferrer" class="hashtag u-tag u-category" href="https://world.museumsprojekte.de/tag/documentation/" target="_blank">#documentation</a> <a rel="nofollow noopener noreferrer" class="hashtag u-tag u-category" href="https://world.museumsprojekte.de/tag/grant-erasure/" target="_blank">#grantErasure</a> <a rel="nofollow noopener noreferrer" class="hashtag u-tag u-category" href="https://world.museumsprojekte.de/tag/grants/" target="_blank">#grants</a> <a rel="nofollow noopener noreferrer" class="hashtag u-tag u-category" href="https://world.museumsprojekte.de/tag/imls/" target="_blank">#IMLS</a> <a rel="nofollow noopener noreferrer" class="hashtag u-tag u-category" href="https://world.museumsprojekte.de/tag/museum/" target="_blank">#museum</a> <a rel="nofollow noopener noreferrer" class="hashtag u-tag u-category" href="https://world.museumsprojekte.de/tag/neh/" target="_blank">#NEH</a> <a rel="nofollow noopener noreferrer" class="hashtag u-tag u-category" href="https://world.museumsprojekte.de/tag/preparing-for-shutdown/" target="_blank">#preparingForShutdown</a> <a rel="nofollow noopener noreferrer" class="hashtag u-tag u-category" href="https://world.museumsprojekte.de/tag/registrar/" target="_blank">#registrar</a></p>
Roger Light<p>And this is a possible update. The command synopsis is now split up into multiple logical sections to make it easier to find related options and ignore ones you aren't interested in. As a consequence, it occupies about a full screen height.</p><p>I think it's clearer, but I'm concerned the large amount of screen use is offputting.</p><p>Any thoughts?</p><p><a href="https://fosstodon.org/tags/mosquitto" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>mosquitto</span></a> <a href="https://fosstodon.org/tags/mqtt" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>mqtt</span></a> <a href="https://fosstodon.org/tags/documentation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>documentation</span></a></p>
LaurenAngel sightseeing<br>
<br>
Installation still from a moving interactive performance and imagination construct <br>
<br>
We create stories of love and heartbreak <br>
<br>
<a href="https://pixelfed.social/discover/tags/angel?src=hash" class="u-url hashtag" rel="nofollow noopener noreferrer" target="_blank">#angel</a> <a href="https://pixelfed.social/discover/tags/Installation?src=hash" class="u-url hashtag" rel="nofollow noopener noreferrer" target="_blank">#Installation</a> <a href="https://pixelfed.social/discover/tags/theater?src=hash" class="u-url hashtag" rel="nofollow noopener noreferrer" target="_blank">#theater</a> <a href="https://pixelfed.social/discover/tags/mixedmediaart?src=hash" class="u-url hashtag" rel="nofollow noopener noreferrer" target="_blank">#mixedmediaart</a> <a href="https://pixelfed.social/discover/tags/arte?src=hash" class="u-url hashtag" rel="nofollow noopener noreferrer" target="_blank">#arte</a> <a href="https://pixelfed.social/discover/tags/artecontemporanea?src=hash" class="u-url hashtag" rel="nofollow noopener noreferrer" target="_blank">#artecontemporanea</a> <a href="https://pixelfed.social/discover/tags/artecontemporaneo?src=hash" class="u-url hashtag" rel="nofollow noopener noreferrer" target="_blank">#artecontemporaneo</a> <a href="https://pixelfed.social/discover/tags/photography?src=hash" class="u-url hashtag" rel="nofollow noopener noreferrer" target="_blank">#photography</a> <a href="https://pixelfed.social/discover/tags/documentation?src=hash" class="u-url hashtag" rel="nofollow noopener noreferrer" target="_blank">#documentation</a> <a href="https://pixelfed.social/discover/tags/contemporaryart?src=hash" class="u-url hashtag" rel="nofollow noopener noreferrer" target="_blank">#contemporaryart</a> <a href="https://pixelfed.social/discover/tags/installationart?src=hash" class="u-url hashtag" rel="nofollow noopener noreferrer" target="_blank">#installationart</a>
Alfonso Siciliano<p>I am working on creating a handbook that describes the assistive technologies available in the FreeBSD operating system, which will be freely available online for anyone to consult. Currently, the effort is focused on gathering and documenting accessibility features for visual impairments, and it is sponsored by the <span class="h-card" translate="no"><a href="https://mastodon.social/@FreeBSDFoundation" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>FreeBSDFoundation</span></a></span> </p><p>If you are interested in the topic, a public repository is available for suggestions and corrections: <a href="https://gitlab.com/alfix/freebsd-accessibility" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">gitlab.com/alfix/freebsd-acces</span><span class="invisible">sibility</span></a></p><p><a href="https://mastodon.bsd.cafe/tags/FreeBSD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>FreeBSD</span></a> <a href="https://mastodon.bsd.cafe/tags/UNIX" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>UNIX</span></a> <a href="https://mastodon.bsd.cafe/tags/OpenSource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>OpenSource</span></a> <a href="https://mastodon.bsd.cafe/tags/Accessibility" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Accessibility</span></a> <a href="https://mastodon.bsd.cafe/tags/a11y" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>a11y</span></a> <a href="https://mastodon.bsd.cafe/tags/Blindness" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Blindness</span></a> <a href="https://mastodon.bsd.cafe/tags/LowVision" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>LowVision</span></a> <a href="https://mastodon.bsd.cafe/tags/ColorBlindness" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ColorBlindness</span></a> <a href="https://mastodon.bsd.cafe/tags/AssistiveTechnologies" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>AssistiveTechnologies</span></a> <a href="https://mastodon.bsd.cafe/tags/Inclusion" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Inclusion</span></a> <a href="https://mastodon.bsd.cafe/tags/Documentation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Documentation</span></a> <a href="https://mastodon.bsd.cafe/tags/Coding" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Coding</span></a></p>
Third spruce tree on the left<p>Grammarly: we miss you! Did you take a writing break? </p><p>me: it's not you, it's my new IT department won't allow <a href="https://mas.to/tags/Grammarly" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Grammarly</span></a> and Microsoft Editor sucks donkey balls; I guess having proper <a href="https://mas.to/tags/spelling" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>spelling</span></a>, grammar and <a href="https://mas.to/tags/punctuation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>punctuation</span></a> in our product <a href="https://mas.to/tags/documentation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>documentation</span></a> isn't a priority here at InniTrobe.</p>
Miguel Afonso Caetano<p>"The following are my suggestions regarding what else to consider for each of Daryl White’s excellent questions about choosing a toolset for documenting a software product or project.</p><p>I have appended a brief guide to the main/broad categories of documentation toolsets and some of the platforms/components that are popular in each.</p><p>Finally, this resource ends with a table of possible solutions for various scenarios you might find yourself in.</p><p>Before we start with the existing list of questions, I want to highlight one that I think is most important of all, but which is often assumed by people who create these kinds of guides, as they tend to come from one or another world already.</p><p>What are you documenting?</p><p>When it comes to software technical writing, the more appropriate way to ask this might be: For what user roles is your documentation intended?</p><p>For graphical end-user interfaces (GUIs), the largest range of docs tooling is available, but here some of the more commercial turnkey tools have most of their advantages.</p><p>For administrator interfaces (installation, configuration, etc), again any tooling will work, but we start seeing real advantages for lightweight markup, codebase integration, and version control.</p><p>For developer interfaces, docs-as-code offers significant advantages. Developers can better contribute directly, and it’s generally friendlier for coded samples. APIs (native and remote), SDKs, and CLIs are almost certainly best documented in a docs-as-code environment, even if you integrate it with a more conventional platform for end-user docs."</p><p><a href="https://gist.github.com/briandominick/d4cbe11228de0ebe31cda630976af4ef" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">gist.github.com/briandominick/</span><span class="invisible">d4cbe11228de0ebe31cda630976af4ef</span></a></p><p><a href="https://tldr.nettime.org/tags/TechnicalWriting" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>TechnicalWriting</span></a> <a href="https://tldr.nettime.org/tags/SoftwareDocumentation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SoftwareDocumentation</span></a> <a href="https://tldr.nettime.org/tags/Documentation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Documentation</span></a> <a href="https://tldr.nettime.org/tags/DocsAsCode" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DocsAsCode</span></a> <a href="https://tldr.nettime.org/tags/TechnicalCommunication" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>TechnicalCommunication</span></a> <a href="https://tldr.nettime.org/tags/InformationArchitecture" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>InformationArchitecture</span></a> <a href="https://tldr.nettime.org/tags/CCMS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CCMS</span></a></p>
BlueSpice<p>📄 Still no ticket for the HANNOVER MESSE next week? 📅<br>No problem! Secure your <a href="https://fosstodon.org/tags/free" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>free</span></a> ticket now with <a href="https://fosstodon.org/tags/BlueSpice" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>BlueSpice</span></a> at <a href="https://www.hannovermesse.de/en/application/registration/direct-entry-tickets-passes?code=DshbB" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">hannovermesse.de/en/applicatio</span><span class="invisible">n/registration/direct-entry-tickets-passes?code=DshbB</span></a></p><p>Visit us at our Stand B22/Hall 17 and find out more about the innovative combination of <a href="https://fosstodon.org/tags/Wiki" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Wiki</span></a> and <a href="https://fosstodon.org/tags/AI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>AI</span></a> <br><a href="https://bluespice.com/bluespice-at-hannover-messe-2025/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">bluespice.com/bluespice-at-han</span><span class="invisible">nover-messe-2025/</span></a></p><p>We look forward to your visit!<br><a href="https://fosstodon.org/tags/Networking" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Networking</span></a> <a href="https://fosstodon.org/tags/MediaWiki" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>MediaWiki</span></a> <a href="https://fosstodon.org/tags/KnowledgeManagent" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>KnowledgeManagent</span></a> <a href="https://fosstodon.org/tags/Documentation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Documentation</span></a> <a href="https://fosstodon.org/tags/Compliance" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Compliance</span></a> <a href="https://fosstodon.org/tags/OpenSource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>OpenSource</span></a> <a href="https://fosstodon.org/tags/ISO" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ISO</span></a> <a href="https://fosstodon.org/tags/HM25" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>HM25</span></a></p>
ExploreLive feeds
Mastodon is the best way to keep up with what's happening.
Follow anyone across the fediverse and see it all in chronological order. No algorithms, ads, or clickbait in sight.
LoginDrag & drop to upload