memos

Memos discovery must distinguish a note app from a public share Memos discovery must distinguish a note app from a public share Memos is a self-hosted note-taking application built around a timeline of short notes. Some notes are private, some are visible to signed-in users, and some can be shared publicly. That range makes product discovery different from deciding whether a page exposes a note. A visible login form and a public bearer-token link are separate observations. A ZoomEye count-only measurement on October 31, 2026 at 06:44 Beijing time used page 1, page size 1, and sub_type=all. app="Memos" returned 0 matches and title="Memos" returned 6,134. These counts describe visible ZoomEye fingerprints. They do not identify public notes, signed-in-only pages, or installations with weak access controls. Treat the zero as a fingerprint result A zero app result means the exact application fingerprint was absent from this result scope. It does not mean there are no Memos instances. Self-hosted software often appears under a company domain, with a custom title, a reverse proxy, or a configuration that changes the default response. The title count is broader because the word can appear in login pages, help content, and unrelated pages. Use it to find candidates, then verify the product from an owned deployment. If the page is not owned by the organization, do not use a share path, API route, or login form to test access. A product match is not permission to inspect notes. Separate visibility from sharing Memos' API definitions distinguish a note's visibility from a share grant. A private note belongs to its owner. A signed-in-only note can be read by authenticated users under the deployment's policy. A public note can be read anonymously. A share grant provides read-only access through an opaque bearer token. That means a note URL can be sensitive even when the main application requires login. A share token should be treated as a capability. Anyone who obtains it may be able to read the note until it expires or is revoked. Record who created the share, which note it references, the intended audience, and the revocation path. Check whether shares are visible in the application's administrative interface or only to the note owner. Test revocation on an owned instance. Confirm that a revoked token fails and that the cached page is not still served by a proxy. Review browser history, chat previews, mail archives, and support tickets for share links that escaped their intended recipients. Review instance access settings The deployment policy should state whether the instance is public, authenticated, or private. Public instances may allow anonymous reading of public notes, while private instances should reject unauthenticated access. Do not infer that setting from one page title. Check the effective configuration and test the behavior with a fresh session. Review personal access tokens, administrator accounts, backup access, and database permissions. A token that survives a password change needs an explicit ownership and revocation process. Audit signup and user creation if the instance is exposed. Keep the database and attachment storage out of direct public paths. For external discovery, capture only the hostname, title, first-seen time, and visible authentication status. Do not open note paths or enumerate user names. For an owned asset, compare the public route with the internal service inventory and confirm that the intended access mode matches policy. Build the record that matters The useful unit is a deployment record: owner, hostname, access mode, authentication methods, administrator group, token policy, share policy, backup location, and last review. Add a test note for each visibility state, a share token test, a revocation test, and an unauthenticated request to an internal route. ZoomEye helps find a self-hosted service that may have left the asset catalog. It cannot show whether an individual note is safe. The application's visibility model and share tokens decide what a successful viewer can read. Conclusion Memos app and title counts are discovery evidence, not exposure evidence. The title query is a starting inventory; the app count shows one fingerprint's limit. Security review starts when an owned deployment is connected to its access policy, share tokens, administrators, backups, and revocation tests. References - Memos repository and sharing overview - Memos memo service definitions - Memos security policy - ZoomEye: app="Memos" - ZoomEye: title="Memos"

Repo of the day: one command to self-host your notes We built Memos from source and ran it for real: a private, self-hosted notes app. 🔔 Subscribe for a new GitHub repo tested every week: youtube.com 💬 Comment REPO for the link, or get it here: essaihi04.github.io Repo: usememos/memos (MIT license, by the Memos contributors) Install: docker run -d --name memos -p 5230:5230 -v ~/.memos:/var/opt/memos neosmemo/memos:stable Sources: - Memos README and LICENSE: usememos/memos - Demo: built from source in a sandbox, server started, health check returned HTTP 200 (Docker image not tested) Images: none (animated graphics generated by code). Voice: Piper TTS (synthetic). Music: original, generated. #Shorts #GitHub #SelfHosted #Memos #RepoRadar

Build Autonomous Software Delivery Team with Intelligent Terminal & To Learn how to create an autonomous software delivery team by integrating intelligent-terminal, pi-dynamic-workflows, puppeteer, gatus, and memos. This video demonstrates practical steps to automate workflows and streamline delivery. Focus on real-world implementation rather than theoretical concepts. The process emphasizes scalability and team independence. Repositories used in this architecture: - intelligent-terminal: microsoft/intelligent-terminal - pi-dynamic-workflows: pi-engine/pi-dynamic-workflows - puppeteer: puppeteer/puppeteer - gatus: TwiN/gatus - memos: usememos/memos This episode explains one integrated product architecture, including interfaces, data flow, deployment, security, and failure handling. Subscribe for daily open-source product builds: youtube.com #GitHub #OpenSource #SoftwareArchitecture #Programming

@_kip2 こんばんは。作業ログならMemosが用途に合うかもしれません。マルチプラットフォームで使えます。 usememos/memos

A timeline for your thoughts Memos lets you jot down thoughts in Markdown, add images, and later find them by search, tags, or scrolling any day. It’s self-hosted, zero telemetry, and built with Go, so your data stays yours. 🍒 Built by the Memos team usememos/memos #opensource #golang

灵感来了，别再发给文件传输助手！📝 Memos 像时间线一样记碎片笔记。 支持 Markdown、标签和搜索，还能自己部署。💭 usememos/memos #Notes #SelfHosted #浇朋友 #蓝朋友 #互关 #fo

Memos: Your thoughts, your data, shared on your terms (64k stars) What it does All text below is quoted directly from the project README. >Memos is a timeline for your notes, and it belongs to you. Write in Markdown, post in seconds, and choose who sees each memo: just you, the people you invite, or anyone with the link. Why Memos?: - Write first: Save a thought without choosing a title or folder. Memos are written in Markdown and can include images and files. - Find it later: Search, filter by tag, or look back through any day on the timeline. Pin what matters and save the filters you reuse as views. - Yours to keep: Self-host Memos with zero telemetry, MIT-licensed source, and a full export of your memos. - Share when you choose: New memos are private. Make one visible to signed-in users or public when you want to share it. - Save pages, selections, and images from your browser straight into Memos as source-linked Markdown. >Run Memos with Docker: docker run -d --name memos -p 5230:5230 -v ~/.memos:/var/opt/memos neosmemo/memos:stable Repository usememos/memos Repository stats |Metric|Value| |:-|:-| |Stars|63,833| |Forks|4,863| |Last release|v0.31.0 (2026-09-19)| |Languages|Go 53.4%, TypeScript 45.9%, Shell 0.4%| |Contributors|435| |AI contributor accounts (Claude / Codex / Cursor / Copilot)|Copilot: 18, claude: 125| |AI co-authored commits|Claude: 108, Cursor: 1, Copilot: 17| Main contributor |Field|Value| |:-|:-| |GitHub|@boojack| |Commits to this repo|2,795 (top contributor)| |Followers|1216| |Public repos|8| |On GitHub since|2016-12-19| ----------------------------------------------------------------------------------------- Discover the best GitHub repos without the endless scrolling. Get top repos organized by category (AI, DevOps, Databases & more), plus key takeaways from developers' most useful comments - all in one free, twice-weekly newsletter. 👉 Get the best repos & community insights - Free

想随手记点东西又嫌笔记软件太重，Memos 走轻路线。 像一个自己搭的朋友圈，打开就是输入框，写完就发，一个二进制文件就能跑。 usememos/memos

Capture an idea in seconds! Memos is a personal timeline for quick Markdown notes. Search by tags or dates, and share only when you choose. Great for reading highlights and daily thoughts; self-hostable. usememos/memos #Notes #SelfHosted t.co

@usememos Memos really took me back. I was just browsing some old posts and in all the years I have used the tool. I never thought it would bring me nostalgia. But It brought back my early homelab learning days! Crazy how far I have come. But thanks MEMOS! usememos/memos t.co