whoops yeah I meant listRepos (just return all them).
that gets a bit complex w/ proxying from a relay, b/c listRepos *does* have meaning at the relay (eg, to help with debugging)
IIRC tap will do things like periodically re-enumerate all DIDs to see if there are any new ones it somehow missed (eg, eventual consistency check). that could put load on services like this
I think it might be a common enough use-case that having a dedicated bucket for "all-accounts" would be good.
the use-case is doing full-network backfill, like tap. the new relay implementation only knows about repos it has seen, not previously existing repos
inactive like deleted, takendown, deactivated, etc (anything with "active" flag false).
wildcard: glob matching would be awesomeI I was just thinking "all accounts seen and active"
this hits a couple things I wish collectiondir did; maybe we can switch over to this implementation...
two other things that would be great, but might be hard: reflect account status (eg, don't show inactive accounts); and have support for wildcard (and/or the getRepos endpoint)
in the long run, if a website or app had something sharable, and that thing has an at:// URI, then browser/OS could use your preferences to open to relevant app to interact with that content.
for sharing a URL, I think something like a browser share API (like Emelia linked) would be good
the best precedent to me is email: you don't "message with gmail", you have a 'mailto:' URI, click that, and your browser/OS figures out what software to run. which might be a browser at a location, or might not.
(from a parallel reply)
oh, interesting. I hadn't heard of this, thanks for... sharing!
the @xblock.aendra.dev and @stechlab-labels.bsky.social labelers are good starters for composable moderation.
I don't know if you are scrolling here or just cross-posting, but a couple tweaks you might be interested in...
the "For You" feed run by @spacecowboy17.bsky.social (on a home gaming PC). it works better once you "like" some posts; you can experiment with parameters here: linklonk.com/bluesky
welcome @doctorow.pluralistic.net!
on your own PDS host (bsky.pluralistic.net), using did:web (did:web:pluralistic.net), and self-controlled domain handle.
looks like things are working/interoperating; let us (the atmosphere ecosystem) know if you run in to any issues
Hi! I'm the new Head of Communications @bsky.app.
I've been watching the open social web evolve over the past couple of years. Bluesky represents what I believe the future of the internet should look like: built on principles that put people first.
a series of lexicon names which spell out the poem "This Is Just to Say" by william carlos williams
ufos.microcosm.blue/all/
Pierre Menard, Author of the 4chan
ascii art train thing that says "Lightrail": an engine pulling one train car. (is this light rail train?) "this is an atproto backfill-by-collection assister. available endpoints: - /xrpc/com.atproto.sync.listReposByCollection - /xrpc/com.atproto.sync.getRepoStatus source: https://tangled.org/microcosm.blue/lightrail
progress
(if you reply tell me this depicted rail is not light, you are obligated to include alternate more-correct ascii art in your response thank you)
ooo nice!
this is a bit surprising to me. I don't want to get ahead of any comms T&S does to clarify the situation
emailing users: I don't know about this specific situation, but a lot of folks originally signed up on the bsky PDS instances, and by default migration leaves the old account in "deactivated" status. mod team may have contact info from that, if the account hasn't been fully deleted.
there is a delay before new accounts show up in search, which might be causing confusion. I don't know what the current status of a profile record being required or not is; I think it is at least requires for profile search / typeahead.
I'm not sure about the core issue and don't want to get ahead of T&S team clarifying.
To Ted's note: atproto accounts should be able to jump in network, create a profile record, and start creating post records, and they should show up in the bluesky app; that's sort of the whole point!
Hey devs! Heads up, we're planning on making some changes to our image CDN tomorrow.
- Images will be served as WebP by default
- The URL format you get from the Bluesky API will change a little
You can look forward to an announcement about image quality soon 👀
XRPC requests between atproto servers are authenticated using JWTs. There are some inconsistencies in how OAuth permissions, PDS proxy headers, and JWTs all represent the "audience" of these tokens.
This proposal gives background and describes a rough solution.
Looking for rapid feedback!
The early TOKIMEKI UI
TOKIMEKI celebrates its third anniversary today! 🎉🎉🎉
Three years ago, Bluesky was still in its infancy and only had an iOS app. As an Android user, I could only post properly by creating a web client.
about 28k relay events, which is over the default 24hr rate-limit. I initially assumed these were all new accounts and they were pushing the rate-limit, but it may have been over a few days
FYI a couple PDSes are down (morel, oyster). Investigating
no, we separately are having an incident with a handful of PDS instances
status.bsky.app
we just stop processing new events on our infra (and downstream). have used this lever very infrequently. could re-enable this instance if they slow down
happy to chat with people. we don't have a blanket anti-bot or anti-experimentation policy, but the volume and pattern of interaction was very high
