Google Drive vs The Null Pointer

Google Drive's API lets applications create, read, update, and share files and folders stored in a user's Drive, with fine-grained OAuth scopes for personal or Workspace accounts. A live GET against the real gateway, www.googleapis.com/drive/v3/files, returned a 403 without a token, reconfirming OAuth 2.0 auth over HTTPS, and a follow-up OPTIONS preflight echoed the request Origin in Access-Control-Allow-Origin, resolving cors from unknown to yes. The url was updated to Google's current Workspace documentation hub, which the old /drive/ path now permanently redirects to. Personal accounts get 15GB free, with paid Google One and Workspace plans raising the storage cap.

The Null Pointer (0x0.st) is a minimalist, no-account temporary file host and URL shortener: a plain POST with a file returns a bare URL as the entire response body, with retention scaled by file size. A live OPTIONS preflight with an Origin header against the real host, 0x0.st, returned a 200 with no Access-Control-Allow-Origin header, resolving cors from unknown to no; no auth is required for uploads, and HTTPS was reconfirmed. It's a single free, ad-free service with no paid tier, retaining files from 30 days up to 1 year depending on size (max 512MiB).