A handful of federated services, running on hardware I own and a connection I pay
for. There's no company behind this and nothing to sell you. Just open protocols,
kept running by someone who actually uses them.
All of this runs on my hardware. Where a service speaks an open protocol you can
use whichever client you like, and take your account somewhere else whenever you
feel like it. That's rather the point.
Checking service statusChecking services…
Matrix
computingcache.com
Matrix status unknown
A Synapse homeserver, federated with the rest of the Matrix network.
Encrypted rooms, bridges, and whichever client you prefer. Your ID ends up
looking like @you:computingcache.com.
A general-purpose Mastodon instance, federating with Mastodon, Pleroma,
Misskey and anything else that speaks ActivityPub. Signups are open, though
I read every one by hand to keep the spam out.
A public strfry relay, free to read from and write to. No account, no
signup, just point a Nostr client at the address above. It speaks NIP-01
through NIP-77, negentropy sync included. Need a client? I'd start with
Vector.
File sync and sharing, calendars and contacts, all over open standards:
WebDAV, CalDAV, CardDAV. Storage is finite and I pay for it, so accounts get
arranged one at a time.
An experiment in HTTP 402 payments settled over PIVX. The endpoint answers
402 Payment Required, you pay the amount it quotes, and the
content unlocks. Very much a lab demo, not a production service.
Mastodon takes signups on the instance itself, and the Nostr relay needs
no account at all. For anything marked accounts by request, send me
a message below or email
admin@computingcache.com and
say roughly what you'd use it for. Mostly that's so I know you're not a bot.
All of it is free, as-is, and kept running by one person in whatever spare time
there is. Read
the terms before you lean on any of it for something
that matters, and keep your own backups. I do.
One box, wired to thousands
This is the part that makes the whole thing worth doing. My Mastodon instance is
currently in touch with 0 other servers, every one of them
run by somebody else, on their own hardware, under their own rules. The names below
are real, pulled live from the instance's own peer list.
That reach is also the catch. Anything you post gets copied out to the servers
involved in the conversation, and once it lands there, no delete button of mine can
reach it. The privacy policy and terms
both spell this out, but reading about it is not the same as watching it happen.
A three-minute sandbox: publish a post, watch the copies land on other
servers, then try to delete them all. You will not manage it, and that is
the lesson.
Live on the relay
Every blip is a real event landing on the relay, streamed to your browser from
wss://nostr.computingcache.com. Rows are event kinds, and each blip
sits where its own timestamp says it belongs, so you're looking at the last two
minutes of actual traffic rather than a loop.
Connecting to the relay…0 in the last two minutes
notes 0
reactions 0
reposts 0
profiles 0
contacts 0
other 0
0 seen this visit
Only the kind and the timestamp get read. No message text, no
author, no identifiers. A public relay carries whatever strangers decide to publish
to it, and I'm not putting that on my front page unmoderated. Nothing is stored, and
the connection closes when you go.
Reporting content
Mastodon, Matrix and the relay all carry things other people wrote, and federation
means I end up caching content from servers I don't run either. If something here
needs dealing with, this is the quickest way to reach me.
Abuse, copyright and takedown requests
Email admin@computingcache.com
with the exact URL, what's wrong with it, and a way to reach you. I read
these myself, usually within a couple of days.
The reporting and takedown page has the detail: what
to include, what a DMCA notice needs in it, and how counter-notices work.
Contact
It's just me back here, so replies aren't instant. Every message gets read, though.
Or write something here and it lands straight in my inbox.
Anything you send through this form is covered by the
privacy policy. If it's an urgent takedown, please email
admin@computingcache.com directly
instead. It reaches me faster.