Just added some new diagrams to describe the internals of the https://thi.ng/block-fs block storage & filesystem (incl. some examples) and also added/updated CLI tooling docs...

I'm finding converting my personal tech notes to public blog posts more challenging than expected.

They've served me well as quick reference docs, code snippets, & cheat sheets. But they look like utter shit when I consider another person looking at them.

I've leaned too heavily on editing, proof-reading, & expanding existing public docs that my writing from scratch has atrophied.

It's a bit of a struggle; but, I want to get these off my local machine and improve my writing.

GEDTM30 – A Global 1-Arc-Second (~30m) Digital Terrain Model (DTM)
--
https://github.com/openlandmap/GEDTM30 <-- shared GitHub repository
--
#GIS #spatial #mapping #opendata #global #DTM #GEDTM30 #GitHub #30m #landsurface #parameters #documentation #hydrology #remotesensing #earthobservation #slope #geomorphons #hillshade #geomorphometry #geomorphology #topography #Equi7 #terrainheight #DigitalTerrainModel #landform

RiverREM - Generating River Relative Elevation Model (REM) Visualisations
--
https://github.com/OpenTopography/RiverREM <-- shared GitHub repository
--
https://opentopography.github.io/RiverREM/ <-- shared documentation
--
https://opentopography.org/blog/new-package-automates-river-relative-elevation-model-rem-generation <-- shared Open Topography blog post about RiverREM
--
H/T Heidi Luchsinger / Open Topography
[this post should not be considered as an endorsement of this product aka caveat emptor]
#GIS #spatial #mapping #remotesensing #earthobservation #Python #LiDAR #RiverREM #visualisation #hydrology #water #river #rivervalley #floodplain #terraces #GitHub #opensource #opendata #DEM #REM #model #modeling #RiverRelativeModel #documentation #tutorial #learning #tool #elevation #raster #sinuosity #drainage

Don’t Use Scores From Automatic Tools in Your Accessibility Statement, by @cerovac_a11y:

https://cerovac.com/a11y/2025/03/dont-use-scores-from-automatic-tools-in-your-accessibility-statement-do-this-instead/

Mark your calendar, grab a coffee — on April 30 (2–4pm CEST) you're invited to our #DocsReviewParty!

After a long road, the #Decidim documentation is finally updated to the latest version. Now we need you to help us review it!

Your feedback on structure, clarity, and content will help improve the docs for everyone — and it's a big step toward our goal of multilingual, community-driven #documentation by 2026.

Register: https://meta.decidim.org/assemblies/eix-comunitat/f/149/meetings/2087?locale=ca

Check the docs: https://docs.decidim.org/en/v0.29/index.html

What's wrong with AI-generated docs https://buff.ly/xAp81oX

let me tell you what’s wrong with docs and docs sets entirely generated by LLMs.

#discord IS LITERALLY THE PROBLEM!

• It's worse than any #IRC, #Mumble or even the old #TeamSpeak & #Skype for that matter.

• It combines the disadvantages of #Forum, #paywalled #documentation, #chat and #voicechat with 0 redeeming qualities (unlike #Zulip & Mumble & #XMPP+#OMEMO) it's just an #InformationBlackhole!

I'm shure fecking #dread has better moderation and I'd rather use #MicrosoftTeams + #Slack cuz those at least have proper #moderation tools.

• And I'd rather subscribe to the #LKML and see my inbox getting hosed than using any shitty #SaaS!

Case in point: I'd rather #SelfHost all my comms infrastructure than to ever use something like Discord or any other #GDPR-violating SaaS that is just enshittification.

I'd rather recommend people to instead choose a tool that does everything but horrible to go with multiple smaller & good tools

• Public Chat? IRC!
• Group Voicechat? Mumble.
• #Documentation? #mkDocs-material.
• 1:1 Chats? XMPP+OMEMO.
• E2EE Group Chats? #deltaChat.
• E2EE Calls? #WebCall.
• Filehosting? #IPFS, #BitTorrent, oshi.at, etc. ...
• …

Check @alternativeto and @european_alternatives for options.

More and more legal #docs / speciations I read from git repository. Markdown is common for this purpose.

The ability to pull sources and use what ever UI I prefer is so convenient

Dynamic table of content / structure is one of my favorite feature.

La doc de Thymeleaf est raisonnablement bien faite, même si il y a une marche d'entrée un peu élevée à passer. https://www.thymeleaf.org/doc/tutorials/2.1/usingthymeleaf.html#introducing-thymeleaf #template #engine #java #spring #documentation #opensource

Over the past couple of months, I've been spending more time reviewing my tech notes from the last five years.

Partially out of a new interest in posting publicly & also trying to improve my writing.

Despite my placing numerous reference links & quotes in these notes, I feel that I'm really blurring the line between plagiarism, absorbing concepts & re-writing them in my own words.

These notes continue to be useful. Just can't quite place the source. A new imposter syndrome.

Behold the groundbreaking revelation that TigerBeetle's team has reinvented the wheel by ditching #Docusaurus for their docs! Apparently, their obsession with "TigerStyle" and "methodology" provides an unparalleled reading experience – because nothing screams #innovation like rebuilding #documentation from scratch.
https://tigerbeetle.com/blog/2025-02-27-why-we-designed-tigerbeetles-docs-from-scratch/ #TigerBeetle #TigerStyle #HackerNews #ngated

We Designed TigerBeetle's Docs from Scratch

https://tigerbeetle.com/blog/2025-02-27-why-we-designed-tigerbeetles-docs-from-scratch/

A lack of code documentation is killing new libraries.

Wow, #Cloudflare just picked up #Arroyo, because apparently, their platform wasn't confusing enough without throwing in some #serverless #SQL stream processing! Now you can enjoy an open-source headache while navigating the labyrinthian DocumentationGetting StartedSQLAPIDeploymentBlogAbout UsDiscordGitHub vortex.
https://www.arroyo.dev/blog/arroyo-is-joining-cloudflare #Documentation #OpenSource #HackerNews #ngated

Ah, yes, the classic "blame the user" defense: Man pages are the epitome of pristine #documentation, and if you can't decipher them, it's obviously your profound incompetence. Clearly, the real issue is that you peasants insist on using those pesky programs that don’t reveal the hidden wisdom of man pages.
https://whynothugo.nl/journal/2025/04/09/man-pages-are-great-man-readers-are-the-problem/ #blameTheUser #manPages #userExperience #techHumor #programming #HackerNews #ngated

Documentation complaints.

The Curse of Knowledge is real in documentation; even big and pricey ecosystems skip basic information.

Two examples I ran into this morning:

1. GitHub's CODEOWNERS documentation does not explicitly mention where to create the file.

https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners

2. NPM's docs do not explain allowed characters in package names.

https://docs.npmjs.com/package-name-guidelines