







Help Site Map Text Only
API - OpenStreetMap Wiki
OpenStreetMap has an editing API for fetching and saving raw geodata from/to the OpenStreetMap database — this is the entry page for the documentation. If you just want to embed a map into a webpage, you don't want this API. Use a web map library instead. Alternatively, consider the Overpass API which provides read-only API access.
Elicitation - Model Context Protocol
Use this file to discover all available pages before exploring further.

Address Lookup - iroh
Use this file to discover all available pages before exploring further.
Little Free Library World Map - Little Free Library
Find Little Free Libraries near you on the world map. Share your location to see little libraries in your area, or search by city, state/province, zip code, or country.

readeck
Readeck is a simple web application that lets you save the precious readable content of web pages you like and want to keep forever.
Cap'n Web: a new RPC system for browsers and web servers | Hacker News
> .map() is special. It does not send JavaScript code to the server, but it does send something like "code", restricted to a domain-specific, non-Turing-complete language. The "code" is a list of instructions that the server should carry out for each member of the array.
A Beginner’s Guide to Scientific Roadmapping
Wonderful maps and how to read them

This generated some discussion so I want to expand on it a bit The context is that standard.site doesn't currently have any lexicons for the actual content. The idea is that the document content is covered by leaflet, offprint, pckt, or other lexicons. But...
Paul Frazee
You shouldn’t use lexicons that don’t actually exist
wip map of standard.site docs: pub-search.waow.tech/atlas
pub search / atlas
pub-search.waow.techi was annoyed that this isn't explained how i want in the docs so i wrote my own mini-guide to publishing lexicons:
atproto made simple: publishing lexicons
underreacted.leaflet.pubI really love how this handy widget lets you quickly browse through permission sets for various existing services Pro tip for lexicon designers: This is a great way to learn from peers -- @sifa.id, @beaconbits.app, etc -- who've done the work to decompose their permissions into useful subsets 😉