no account? no problem!

thanks to @selfhosted.social 🩵

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

This is expected to happen tomorrow, and we do not expect any downtime when Bluesky PBC does the changeover.

Can keep an eye on our notice message at the top of selfhosted.social if anything changes and will send out modmail via email if there is an extended outage.

Dreams do come true. @selfhosted.social is now running on two PDS containers to spread the work across multiple node processes.

Bad news. It did not help with CPU usage being pegged at 70%. It is now 100%. I guess if you're going pay for something, use it all.

Hey everyone. We're back! I am terribly sorry about the outage today. I wrote a postmortem to explain better what happened.

tldr: We had a large influx of create records, which led to us learn the rate limit was not on and to be rate limited by the relay for a few hours

Looks like we have a pretty large backlog of records for the relay to process, but hoping things should be back to normal as those process.

Sorry again everyone about this!

selfhosted.social appears to be having some issues where posts are delayed before showing after they are created. This affects new posts, replies, and likes. Looking into it.

Details: I think we are experiencing high volume of create records and the relay may be rate limiting us a bit

We were indeed vulnerable to this type of attack, and it has now been patched. This would have only affected you on our landing page at selfhosted.social, nowhere else like inside of the bsky.app. Also, we have no reports that anyone attempted this before the vulnerability was found and patched

I was made aware of this possible attack vector last night and was kindly informed that we could be vulnerable to it on our landing page. As soon as I was made aware I turned off our landing page till it could be tested. All PDS operations are still operational, but the landing page is down for now.

Did you know on our dashboard on selfhosted.social that it shows your current Statusphere status and song you are listening to with teal.fm?

A bit late but we are over 50 active accounts now 🥳

selfhosted.social members now have another backup for their blobs and repos with a new PDS MOOver node instance.

If ever needed, and as long as you have a rotation key, you can use one of these two links

UpCloud, Chicago, US
pdsmoover.com

Railway, Amsterdam, Netherlands
eu.pdsmoover.com

If you're migrating your account to selfhosted.social, you will need to use this PDS MOOver URL since we use a captcha on account creation.

pdsmoover.com/moover/selfh...

We are officially open to the public! selfhosted.social is an independent ATProto PDS managed by @baileytownsend.dev

No invite codes required. Everyone is welcome. We just ask that you read over and agree to our Privacy Policy and Terms of Service.

selfhosted.social/legal

selfhosted.social is getting ready to go "public". This account will become the selfhosted.social account once the dns record resolves. The new landing page is live along with an info section, and our Privacy Policy and Terms of Service if members would like to look them over.