Blinko's 952 title matches and 165 app matches need a user-boundary review

Blinko is a self-hosted note tool that combines card notes with AI-assisted retrieval. The service can hold personal writing, attachments, account identity, and the provider credentials that support search and generation. A count-only ZoomEye probe returned 952 assets for title="Blinko" and 165 for app="Blinko". The two counts describe different discovery signals for the same product name and should be reviewed separately.

Blinko's project describes a TypeScript note application with AI-powered retrieval and a privacy-focused self-hosted model. The open-source page says users choose where the application and data run. Those statements establish the data sensitivity. They do not establish that any particular public host has enabled user isolation, secure registration, or protected AI credentials.

What ZoomEye measured

The SDK ran app="Blinko" and title="Blinko" with sub_type="all", page 1, and page size 1 at 08:42 Asia/Shanghai on 17 November 2026. The app query returned 165 and the title query returned 952. The application count is the narrower product fingerprint. The title count can include login pages, documentation, or deployments whose response title contains the name. Neither query checks the note contents or version.

A difference of this size is a reason to inspect the evidence, not to pick the larger number as an exposure count. Start with hosts that match the application fingerprint, verify the deployment owner, and then compare title-only candidates against a known deployment signature.

Separate data, identity, and AI authority

A note application has at least three boundaries. The first is account identity: who can create an account, who is an administrator, and how a removed user loses sessions and API access. The second is note access: whether private, shared, and public notes use distinct authorization checks. The third is AI integration: which provider keys or local models are configured, what text is sent to them, and whether attachments are included.

For a self-hosted deployment, the database and object storage deserve an owner and backup policy. AI provider keys should not be readable by ordinary users or exposed through client-side configuration. If remote generation is enabled, the operator should document data flows to each provider and offer a clear way to disable them.

Build a review queue

Record the host, owner, login mode, registration policy, user roles, note-sharing policy, AI provider, attachment store, and last upgrade. Test a second user against a private note, a shared note, and an AI retrieval query. Confirm that the search index does not return another user's text or metadata.

ZoomEye can identify internet-facing candidates. The question that matters is whether the deployment enforces its note and user boundaries after discovery.

References