Show HN: I made a private self-destructing image hosting site in Golang

The new site provides a straightforward workflow: a user drops an image, selects an expiration timer or view limit, and receives a unique link. The link is constructed from a long random identifier, which prevents enumeration and is flagged to search engines as non-indexable. Once the chosen condition is met, the server stops serving the image, effectively erasing it without any user-initiated action.

Implementation is done in Go and is hosted on a modest server that cannot afford to retain many files. Because there is no persistent storage layer, the service likely stores uploads only in memory or temporary disk space until the expiry triggers deletion. This design choice keeps operating costs low but also means the service cannot act as a long-term archive.

Operational limits are explicit: uploads must be under 15 MB and limited to common image formats, and the system does not provide a manual delete function. Users must rely on the preset timer or view count to remove content, which simplifies the code path but requires careful selection of limits to avoid premature loss. The absence of user accounts further reduces complexity but also eliminates any ability to manage or retrieve past uploads.

Compared with existing image-sharing platforms that may offer richer features, this implementation trades flexibility for privacy and self-destruction. The focus on a single-use, private link makes it suitable for scenarios where confidentiality and automatic cleanup are paramount, such as sharing screenshots or confidential diagrams. Engineers looking to embed similar functionality can adopt the same pattern of random URLs, expiration hooks, and view counters without needing a full database stack.