Bluesky Personal Data Server

[sfeldkamp]

This was helpful and validated the direction I was headed with it! I am working from a fork of bluesky-social/pds at https://github.com/sfeldkamp/cloudron-bluesky-pds.

Current status is that it's running! I can add invite codes through the app's web terminal with goat CLI. I can register a user account on the PDS and post, reply, like, and follow from it. These all are pushed to the Bluesky firehose and can be seen in the Bluesky App by other accounts.

Still to be debugged / tested:

• Newly created account on the PDS shows "Invalid Handle" warning in Bluesky App.
• Account migration with goat CLI to the PDS from a bsky.social PDS.
• Account migration with goat CLI from the PDS back to bsky.social PDS.
• General soak test to feel comfortable that all parts of the PDS are working correctly.

I have some time off later this week, so I think I can make progress with these things.

[sfeldkamp]

I have resolved the issue with Invalid Handle. The problem was not having a *.[app.domain.com] wildcard domain mapped for the app. There's unfortunately no way to do this with the CloudronManifest.json file during app installation so this will have to be a manual step for installers.

I've tested migrating an account from a Bluesky PDS and that seems good. Tested making and restoring backups in Cloudron. That seems good.

The only remaining work to be done, that I am aware of, is to implement the update mechanism. I'm uncertain whether I should (or even can) do that or if that is something the Cloudron staff will do as they prepare it for the App Store.

https://github.com/sfeldkamp/cloudron-bluesky-pds

If anyone has any guidance on what more I should do, or a better way to "submit" this to the staff let me know.

I will likely move my live account sometime soon to be self hosted on my custom app install, as I expect that process to take awhile. If anyone would like to try it out themselves or review the code, please feel free!

[robi]

@sfeldkamp see https://forum.cloudron.io/post/117766 for aliasDomains in CloudronManifest.json

[sfeldkamp]

@robi

That's the Cloudron CLI, not the CloudronManifest.json. I asked a follow up question though to clarify though, so thank you.

[sfeldkamp]

I added a checklist item to the CloudronManifest.json that makes it as clear as possible for the user to add the wildcard alias. I just couldn't find any way to do this automatically.

I've also moved my primary PDS on the ATProto network to be hosted on my Cloudron custom app. So far so good, no problems I've noticed!

[girish]

@sfeldkamp does the app have any UI?

[sfeldkamp]

@girish

/ - An informational landing page. You can see it here: https://at.sethfeldkamp.com/
/oauth - OAuth routes

Then data is available from
/xrpc - Http API
/.well-known/atproto-did - DID verification

That's all I can find for routes in the source code.

https://github.com/bluesky-social/atproto/tree/main/packages/pds

[girish]

@sfeldkamp yeah, that works for the Cloudron package.

[sfeldkamp]

<Removed>

See comment below: https://forum.cloudron.io/post/123271

[timconsidine]

@sfeldkamp well done !

Is "testing" a valid entry in CloudronVersions.json publishState ? It's creative but I was under impression that it is 'published' or 'revoked', binary choice. But I might be wrong. It's all rather new !

I'd put it as 'published' and just not list it in the community apps category for now.

[robi]

It seems like they're all in alpha testing until they make it into the app store for beta testing.

[sfeldkamp]

@timconsidine

I got this in the output for the cloudron versions add --help command. But I couldn't say if it has any effect or if it's just informational. It doesn't stop anyone from installing the app. Not sure about whether it would trigger updates.

[girish]

@sfeldkamp @timconsidine 'testing' state marks the release (just that version and not the app itself) as 'unstable' (just like cloudron's own app store packages). UI wise: when you install such a version, it will give a warning. Behavior wise: cloudron won't automatically update the app to that version .

It's really an advanced use case. We copied our app store behavior 1:1 for the community apps.

[sfeldkamp]

@girish

Thank you for explaining! It doesn't appear to be working that way for installs. I don't see any visual indicator for the Community App when installing it, nor on the app after it's installed. Here is the link to the versions file.

https://raw.githubusercontent.com/sfeldkamp/cloudron-bluesky-pds/main/CloudronVersions.json

Let me know if I should cross post this to support as a bug report (or elsewhere). I haven't tested whether "testing" prevents an automatic update from being discovered.

[LoudLemur]

@shanelord01 https://forum.cloudron.io/topic/12472/please-use-this-template-to-make-an-app-wishlist-request

[LoudLemur]

This post is deleted!

[jdaviescoates]

@LoudLemur it's already packaged. I'm really not sure of the value of these reports, they appear to mostly be way off the mark.

[LoudLemur]

@jdaviescoates Thanks, I was just processing a batch of them, and didn't check carefully if they had been packaged yet.

One thing that would be useful is to find where these reports stray. If they are just noise, I will definitely stop the monster, but if they can be adjusted to be more helpful, I shall try that.

This one was particularly clear that it was a no-no, yet it manged to be packaged!

[sfeldkamp]

sfeldkamp said:

Hey everyone!

I've published this as a community app. Currently only a "testing" version (how does that work anyway?), so please don't add it to the Community Apps topic just yet. Would love to get some feedback on it and see if any issues are discovered.

https://github.com/sfeldkamp/cloudron-bluesky-pds

This implementation has a critical bug in it that prevents an account alias from being updated or account migration to another PDS, because of the federated nature of the network, these accounts can't be fixed by fixing the app.
I've "unpublished" the community app by removing the CloudronVersions.json file from the repository main branch. I've added information to the github project readme and archived it to prevent any further installations. I've requested that the app be removed from the Community Apps index.