It's a nice freebie for some disk space! I did hit one little hiccup with it. I think I may of restarted the server without a graceful PDS shutdown or something. But the relay cursor was off from what I had so the relay was not forwarding events when it came back on. Just followed this to fix it
And we should be back! Sorry about that. I think it took close to , or a bit over, the whole 30 minutes. This was a bit of an unusual maintenance that is thankfully a one time thing.
*and to note you need to run `VACUUM;` after the first trim to reclaim the storage space
If you're a PDS admin and also interested in this can find the script here
tangled.org/strings/did:...
growing. Ours is now at 8.4gigs. The maintenance is to shrink it by trimming anything out that is over 48 hours. In my tests I found it brought the size down to 54mb. With this being the first one I need to bring down the server to do it. After that it's a cron job every 48 hours to keep it clean.
The deets:
Every record/event written to a PDS is sent on the "firehose". That's how it goes from the PDS -> relay -> appview. The order of those events and some info is stored in a sqlite db named sequencer. The PDS does not trim that automatically, so since the PDS has been running it has been..
Can expect some down time tonight on 04-04-2026 around 02:00 UTC, or 10pm eastern on the 3rd.
We are hoping this should take only 30mins or less. Can also expect there will be some more down time next week, but details will follow.
Thank you! and nice! They can be had for a lot cheaper as well. selfhosed keeps a bit more ram so it can hopefully support larger repo imports (up to 450mb-ish), so that cost a bit more.
My previous PDS was like a 1 vcpu 2gb ram for $7 and was perfectly fine for a few accounts
- I've notice we seem to get a lot of getRepo's, so cause the CPU to run a bit higher, but does not affect normal browsing
- the $60 goes across: droplet, backups, and S3.
All in all I'm hopeful this holds till 10k, only one way to find out I guess!
Shows CPU, load, and memory usage from digital ocean
*I probably should have said "The hope is 10k+ users" >.>, this is mostly my estimate by guesswork, but I don't want to be misleading.
Current facts:
- DO droplet 2 vcpu, 8 GB ram, 100 gig drive
- 421 active accounts
- 32gigs of blobs in S3 ($5 for the first 250)
- Last 7 days stats from dashboard
The server comes out to about $60 a month, and the plan is that should be enough for 10k+ users.
In time, whew. Really depends. Lower end 5 hours a month, higher end is 20+
Happy to host y'all!
Shows the heading ATProto PDS and "home to 209 accounts"
Our little home has grown to over 200+ active accounts!
New to the Atmosphere? You'll need to select a PDS (Personal Data Server) to access apps on the Atmosphere, such as Bluesky, Tangled, and Spark. selfhosted.social A popular community-run PDS BlueskyThe main Bluesky PDS instance Tophhie CloudA PDS service by Tophhie Blacksky PDSA PDS service by Blacksky Algorithms Another PDS Enter your own PDS host URL Learn more about self-hosting Each host has their own policies and reliability standards. Your ATProto data lives on the host you choose and you can migrate later. Note: Streamplace has its own moderation rules - you can be banned from Streamplace regardless of which host you choose. Read selfhosted.social's Terms of Service and Privacy Policy before continuing. Cancel Continue
Streamplace v0.9.9 is live! Aside from a variety of bugfixes, we've completely revamped our Sign Up button and it now suggests, in randomized order: @selfhosted.social, @blackskyweb.xyz, @tophhie.social, and @bsky.app!
What are other open-access PDS providers we should include?
Idk if I have enough eyes for another chat room 😅
We're happy to give devs somewhere brand new identities on the atmosphere can be created if the user has never been on the atmosphere before!
Not all roads lead to Bluesky in the atmosphere. Sometimes it's to us, or other communities like @blackskyweb.xyz and @transrights.northsky.social.
selfhosted.social, the neighborhood’s PDS. Buy one get one free atproto app everyday.
You can now sign up to @rocksky.app with @selfhosted.social
no account? no problem!
thanks to @selfhosted.social 🩵
whoops! Thank you that notice is done so I hid it. Should be able to refresh and read the site much better.
to the atmosphere who may have never heard of Bluesky, but have of your app and want to sign in to use your app.
Yes! That's the promise of the PDS, and we're a community hosted one. Also worth noting: if the user already has an account with Bluesky, they already have a PDS and login, so they do not have to create a brand new identity. They can just use that one. This is for brand new users to your app and..
We love The Moth App ™️ and would welcome the moths!
You may also let them know they may already have an account on the atmosphere, especially if they found out about it via a Bluesky post.
There are also other great PDSs that do not require an invite code, like Blacksky at blacksky.app. Each PDS has their own T&S so best to review those first.
Create an account screen on the PDS
To do this you just pass the full PDS url prefixed with https, instead of a handle on oauth. This will give them a screen where they can create a new account, then redirect authenticated to your app.
On this page users can also review our T&S and privacy policy before they create the account
shows DeckBelcher's create account page with selfhosted.social set
Blento's login or sign up page
ATProto devs did you know you can use selfhosted.social for users to create brand new accounts on the atmosphere in your applications? Both deckbelcher.com and blento.app uses our PDS. A user's journey into the atmosphere does not always have to be started from Bluesky. It can start from your app.
You can now signup directly on blento.app without having to already have an atproto/bluesky account!
Powered by @selfhosted.social's PDS (thankfully didnt have to set up my own pds 🫶), pretty happy with the sign-up flow too 😊 from no account to created blento page in less than 1 minute!
I second this. If you are running a tap instance if you could please update to this. If you have heard me talking about @selfhosted.social's high CPU usage, it was this.
There was a bug where when a tap instance subscribed to a repo and the repo changed in any way, tap would download the whole repo
shows a list of relay hosts and the status for each
active on the bluesky east and west below. The west one is becoming bsky.network tomorrow if I'm not mistaken
If I'm not mistaken it is changing the host behind bsky.network to the new one. So everything should work. I believe most troubleshooting will be a reboot of the PDS or request crawl once it is in place and switched over. Using debug.hose.cam will be helpful as well and want to see...
