WeSearch

Why I built tmpdrop: a self-hosted, expiring file drop

·5 min read · 0 reactions · 0 comments · 9 views
#technology#security#software
Why I built tmpdrop: a self-hosted, expiring file drop
TL;DR · WeSearch summary

The article discusses the creation of tmpdrop, a self-hosted file drop service designed to address privacy concerns with public file hosts. It highlights the issues of file retention, predictable URLs, and security vulnerabilities that can arise from using such services. The author explains how tmpdrop mitigates these risks by implementing features like unguessable URLs, a time-to-live for uploads, and enhanced security measures.

Key facts
Original article
DEV.to (Top)
Read full at DEV.to (Top) →
Opening excerpt (first ~120 words) tap to expand

try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 3950932) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } Kin Pan Ho Posted on May 29 Why I built tmpdrop: a self-hosted, expiring file drop #node #opensource #ai #security I had a screenshot to send. Nothing secret — a stack trace from a side project — but it had an internal hostname, a file path with my username, and a chunk of a config file in the terminal behind it. The fast move is to drag it onto a free image host and paste the link. I sat there with my cursor over the upload button and couldn't do it.

Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).

Anonymous · no account needed
Share 𝕏 Facebook Reddit LinkedIn Threads WhatsApp Bluesky Mastodon Email

Discussion

0 comments

More from DEV.to (Top)