Cachely.dev
nxCloud
hastebin
Pastebin.com
PrivateBin
GitHub Gist
Rentry.co
JustPaste.it
0bin.net
Write.as
Cachely is the managed self-hosted remote cache for Nx and Turborepo - the cache backend you'd otherwise build and run yourself, hosted for you on Cloudflare's edge (R2). It's a drop-in replacement for a DIY @nx/s3-cache / S3 bucket setup: point your build tool at Cachely with a token and two environment variables, and share build cache across CI and every developer's laptop.
Unlike a self-hosted cache, Cachely enforces read-only tokens at the API, so pull-request and fork builds can read but never write - closing the Nx cache-poisoning attack (CVE-2025-36852). It adds ROI reporting (the real build minutes and dollars the cache saved), per-tool insights, and build-optimization suggestions on top.
Pricing is a flat per-workspace subscription with no per-seat fees - add every developer, bot, and CI actor without watching the bill. Cachely never stores your source code; it caches only task outputs and their content hashes. Nx and Turborepo today; Bazel on the roadmap.
Cachely.dev hastebinHastebin is particularly recommended for developers and anyone else who needs a fast, no-frills way to share text and code snippets without the overhead of account creation or the complexities of larger platforms. It's ideal for quick debugging sessions, code reviews, and other temporary sharing needs.
Based on our record, hastebin seems to be more popular. It has been mentiond 24 times since March 2021. We are tracking product recommendations and mentions on various public social media platforms and blogs. They can help you identify which product is more popular and what people think of it.
There's a guide on the subreddit wiki on how to format code for display on reddit. When in doubt, you can also use GitHub Gist or Hastebin, though. Source: over 4 years ago
In future, use code formatting or put your code into hastebin.com and then post a link here. It will make it easier to read. Source: almost 5 years ago
If you want to post a log, you'll have to generate one first (go to settings > logging and set both logging verbosities to 0-debug and 'log to file' to ON, then do whatever you need to do to create the offending behavior; that should make the log. Then, open the resulting log in a text editor and copy/paste the contents somewhere like hastebin.com and post a link to it here). Source: almost 5 years ago
Close RetroArch, then navigate to your 'logs' folder in your RetroArch user directory (if you can't find it, open RetroArch and go to settings > directory and see where your 'logs' directory is located). You should see a text file there. Copy/paste its contents somewhere like hastebin.com and then post a link to it here and I/we can take a look. Source: almost 5 years ago
Can you give me the entire command history that got you to where you are now? If you can do that, make sure there is not personal information in the history, especially passwords. Look at the output of history. If it's large, try hastebin.com . Source: almost 5 years ago
nxCloud - nxCloud is a commercial OwnCloud provider
Pastebin.com - Pastebin.com is a website where you can store text for a certain period of time.