Post

fry69
@fry69.dev

->

fry69@fry69.dev

FYI: The compose.yaml file hard codes the PDS to `ghcr.io/bluesky-social/pds:0.4` and the new PDS is 0.5.26, so it will not get automatically updated (which is good/intentional?) See -> github.com/bluesky-soci... The update instructions are outdated in the README, IMHO.

github.comgithub.com
fry69
@fry69.dev

Update ->

Alex@alex.bsky.team

it will actually because we’ve been tagging the images with “0.4.5026” (or other hacked up real version number) for a few months now to work around this since we incremented it by accident. at some point when we have a breaking change we will actually bump it properly

Mark X
@markmx.bsky.social

Amazing! Love to see it. Is there an endorsed/stable way to query a PDS for the service name and logo? We've been adjusting the atmosphere banding in Germ for different PDS hosts, and a consistent way to signal that would be ideal.

Bailey Townsend 🦀
@pds.dad

More than likely be hitting this weekend for us 👀. But it’s also more the admin side showing things like what end points being hit a lot, who is hitting it, etc. things that could be dangerous to users. But if there’s anything fun and not too revealing I will make public