Using my-notes
A little space that follows you.
Create and share
Use Create new note for an eight-character random URL, or open a named note. Share its URL and open it on another device. Names are case-sensitive. Slashes group names logically; they do not create directories or listings. A filename extension does not change note behavior.
Live editing and recovery
Connected browsers merge edits using CodeMirror. “Saved” means persistence was acknowledged. If you lose the connection, keep editing; the draft stays in this tab. Reconnect submits it only if the server version is unchanged. Otherwise, compare the base, your draft, and current server text. Resolve manually or confirm before using the server version. If the server changes during review, your resolution stays available for another comparison.
Download, clear, and undo
Download text saves the text visible in this browser, including unsaved or conflicted text. Clear affects everyone and keeps retained history. Shared undo and the editor's undo shortcut pop the latest editing group regardless of who edited it. Every edit restarts the 30-second idle timer; continuous typing can remain one group. There is no redo. HTTP replacement, append, and clearing are explicit group boundaries.
Privacy and retention
Public note. Anyone with this URL can read, edit, or clear it and access its retained history. Don’t put private information here.
Retained history is visible to readers of the note. Expiry removes current content and history, and administrative purge is separate from normal clearing. Backups have independent retention; neither clear nor purge removes existing backups. Keep unsaved drafts open or download them before leaving the tab.
HTTP and CLI
GET or HEAD the note URL for saved UTF-8 text; missing notes return 404. Browsers get the editor. Use ?format=txt to force text. PUT replaces, POST appends exact input, and DELETE clears. Unsupported media return 406. The CLI offers get, put, append, and clear; my-note.sh appends stdin.
curl https://my-notes.online/example
printf 'hello\n' | my-notes put example
echo 'more' | my-note.sh exampleAuthentication and app storage
Private scripts use Authorization: Bearer TOKEN over HTTPS. Administrators create, list, and revoke tokens with the CLI; no web token administration exists. Manifest changes take effect on restart. An app token may be restricted to one exact app name. JSON resources use /_/apps/APP/KEY; files use /_/apps/APP/files/PATH. GET returns an ETag; use If-Match for replacement/deletion and If-None-Match: * for creation. A stale precondition returns 412. The server replaces whole JSON documents without merging. Live app notifications are not implemented.
Administration
Run my-notes check --config FILE before replacing configuration. Back up with my-notes backup --config FILE --output BACKUP_FILE. Restore only into an absent destination using my-notes restore --config FILE --input BACKUP_FILE. Keep public/private instances and backups separate. See the distribution's README, token reference, app integration guide, and operations guide for permissions and recovery procedures.