home.social

#atdev — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #atdev, aggregated by home.social.

fetched live
  1. very good read. keep it open and read it in pieces if you need to (is long).

    #atdev #atproto #artists #art #community and #DisabledInSTEM y’all might appreciate this for its greater message and ideas.

    How creatives and devs can all...

  2. very good read. keep it open and read it in pieces if you need to (is long).

    #atdev #atproto #artists #art #community and #DisabledInSTEM y’all might appreciate this for its greater message and ideas.

    How creatives and devs can all...

  3. Hmm… looks like I need to explicitly set token_endpoint_auth_method to "none", otherwise it defaults to "client_secret_basic" and errors out?… That's… not very "optional" after all 🤔 #atdev #oauth

  4. Hmm… looks like I need to explicitly set token_endpoint_auth_method to "none", otherwise it defaults to "client_secret_basic" and errors out?… That's… not very "optional" after all 🤔 #atdev #oauth

  5. Sharing this! Wish I'm not late for #IETF126

    Tangled found PDS doesn't fit well for contributions even with upcoming permissioned space spec.
    So, we are planning to store record-like data outside of PDS, in Knot. This is a post explaining the reasons & upstream spec change we need.

    #atproto #atdev

    tangled-cob.md · by boltless.m...

  6. Sharing this! Wish I'm not late for #IETF126

    Tangled found PDS doesn't fit well for contributions even with upcoming permissioned space spec.
    So, we are planning to store record-like data outside of PDS, in Knot. This is a post explaining the reasons & upstream spec change we need.

    #atproto #atdev

    tangled-cob.md · by boltless.m...

  7. #atdev community got their work cut out for them when the main app in the Atmosphere has truly the most awful comms in the world like wtf

    This playbook from 2016 doesn’t work anymore and certainly doesn’t fit the atmosphere vibe we want to cultivate

    We don’t have to stoop to legacy social tactics

    RE: https://bsky.app/profile/did:plc:j5wdt346dbekcpjszpu4tvth/post/3mpgtx6b3us27

  8. #atdev community got their work cut out for them when the main app in the Atmosphere has truly the most awful comms in the world like wtf

    This playbook from 2016 doesn’t work anymore and certainly doesn’t fit the atmosphere vibe we want to cultivate

    We don’t have to stoop to legacy social tactics

    RE: https://bsky.app/profile/did:plc:j5wdt346dbekcpjszpu4tvth/post/3mpgtx6b3us27

  9. How does the protocol treat attempts to run a PDS on a port that's not 443, like { "endpoint": "https://pds.mackuba.eu:3000" } ?

    IIRC it doesn't work, but I wonder at what level that is being rejected, is it something in the spec? #atdev

  10. How does the protocol treat attempts to run a PDS on a port that's not 443, like { "endpoint": "https://pds.mackuba.eu:3000" } ?

    IIRC it doesn't work, but I wonder at what level that is being rejected, is it something in the spec? #atdev

  11. I’m makin so many diagrams this week y’all 🧪 #atdev

    I wish Inkscape was faster and less prone to crashing though 😅
  12. @bsky.app doesn't use oauth. my pds is @[email protected] - so ideal is using an app password for bsky i use witchsky or blacksky, where i can't set an app pw: witchsky says no, blacksky redirects to pds/account where there's no option to set one so...i need bsky.app to get an app pw??? why #atdev

  13. there should be a labeler-demo that exists solely to demonstrate all the combos of settings + client effects that exist, with posts on the account linking to labeled content + profiles indicating what those settings are because wow this system is uh, a bit odd?? #AtprotoIdea #AtDev

  14. i know @[email protected] team has a lot to do, priorities, etc. but takedowns not using the !takedown label yet -- so seemingly less a priority -- is kinda a bummer anyway can you tell i'm working on labelers for something? and can you guess what? 👀😜 #atdev #atproto

    Update on Protocol Moderation ...

  15. Does anyone have some recent full plc.directory dump at hand somewhere?… #atdev

  16. Does anyone have some recent full plc.directory dump at hand somewhere?… #atdev

  17. Oh wow, this is interesting… 🤨 Is it valid for a DID JSON to have the "service" field *capitalized* as "Service"?… are these field names case-sensitive? 🤨 #atdev topics.bsky.app/.well-known/...

    topics.bsky.app/.well-known/di...

  18. Oh wow, this is interesting… 🤨 Is it valid for a DID JSON to have the "service" field *capitalized* as "Service"?… are these field names case-sensitive? 🤨 #atdev topics.bsky.app/.well-known/...

    topics.bsky.app/.well-known/di...

  19. My *very subjective and surface-view* look on which relays are most reliable so far: relay3.fr.hose.cam, relay.bas.sh, and Bluesky's relays (duh) Jetstreams: sfo, nyc & jet from firehose.stream, jetstream2.fr.hose.cam, and Bluesky's (ideally I want you to be able to just see for yourself) #atdev

  20. My *very subjective and surface-view* look on which relays are most reliable so far: relay3.fr.hose.cam, relay.bas.sh, and Bluesky's relays (duh) Jetstreams: sfo, nyc & jet from firehose.stream, jetstream2.fr.hose.cam, and Bluesky's (ideally I want you to be able to just see for yourself) #atdev

  21. Reminder: if you have a Bluesky client app or anything else that does authenticated calls to app.bsky.* endpoints, make sure you're adding the `atproto-proxy` header on them - this will be required at some point. #atdev

    add atproto-proxy header on ca...

  22. Is there any sensible way to easily detect accounts which have default avatars (the smiley or @ on a blue background etc.)? Because they seem to have a normal reference to the CDN which just happens to return an image like this that's from the generator and not uploaded, right? #atdev

  23. Could someone from the backend/protocol team reply to this? I didn't manage to catch Bryan before he left on vacation 😉 github.com/bluesky-soci... #atdev

    client app behavior clarificat...

  24. Again, mistakes were made and when realized *why* things were rectified. Repeatedly hearing something you put effort into criticized (esp when you’re receptive to feedback and fix things) with incorrect assumptions is a reoccurring theme in the #atdev space I’m not a fan of.

  25. I analyzed 22k photo posts from 1014 @[email protected] creators to determine if the old grid layout was "broken" After controlling for account size, caption length, alt-text use, and time of day, 4-image posts still got ~39% fewer likes than 1-image posts #atdev sweetbeex.github.io/bsky-photo-n...

    RE: https://bsky.app/profile/did:plc:lcytlkvzs3wslcgbk7i3ygak/post/3mk6rb327uc2j

  26. misc #atdev thought to consider later but we need more tools on both user & viewer side to improve social media experience for people who have audiences of different highly varied demographics... you can't really have an everyTHING account if it isn't smooth and frictionless to have everyONE there

  27. Also: something for you dark mode sickos 🌚 Label groups are sorted by latest label date from that labeller, so any recently assigned labels should be near the top. Within a group, labels are sorted by name. (Some labels/labellers with weird whitespace in names may not show correctly) #atdev

  28. I'm testing Skythread on Tranquil and I just got this error too when creating a record… Is it required to pass a $type in the object to createRecord (separately from 'connection')? It always worked without it… #atdev

    RE: https://bsky.app/profile/did:plc:7x6rtuenkuvxq3zsvffp2ide/post/3mhnaahm6fs4n

  29. to the #atdev community: thank you. I'm overwhelmed (in the best way) from the community response for support yesterday. I owe a lot of thank you's, but extra huge thank you to @[email protected] and @[email protected] especially for going out of your way to boost a lot and make sure I'm ok.

  30. Can someone who understands OAuth (unlike me) tell me how this compares to existing approaches/solutions (the "aip" open source project, the "Token-Mediating Backend" approach, or the mythical Proposal 0010)? #atdev

    RE: https://bsky.app/profile/did:plc:aq5iwu4gjdcg2hq53llism3x/post/3mh7a52ulus2l

  31. "I have so many projects open with unfinished stuff, so I think I'm gonna start a couple new ones" - #atdev in a nutshell 🫣

    RE: https://bsky.app/profile/did:plc:rnpkyqnmsw4ipey6eotbdnnf/post/3mgvklj5u3s2s

  32. #atdev #atproto we need more plain language communication between dev community and general user base. the average casual user does not understand really understand any of what is being built here, even the simplest explanations tend to be too high level for the lay person.

  33. I've pushed some big updates to atproto-crates, and with them the project has a new home at tangled.org/ngerakines.me/atproto-crates. Over the past five months I've made significant updates and am getting closer to what I'd consider a "1.0" release. Here are some highlights. #ATProtocol #atdev

    ngerakines.me/atproto-crates

  34. This is a subskeet because I don't want to shame a specific project, just as a reminder in general: if you have the string "bsky.social" somewhere in your code, it's sus by default unless proven otherwise. #atdev

    RE: https://bsky.app/profile/did:plc:oio4hkxaop4ao4wz2pp3f4cr/post/3lw2d3kt57c2k

  35. #atdev does anyone know if the relay throttles _consumers_? yesterday incoming bandwidth on my ingester went down to almost zero (and didn't go back up until restart), which corresponded suspiciously well with the bad bunny halftime show

  36. Any idea why something like this would be happening on a relay?… (it's the same host over and over) #atdev

  37. if you delete a post, should it delete the sound record too? #atproto #atdev

  38. okay, so, despite bsky being cultivated by furries from the early days... i'm real surprised we don't have a FurAffinity-type thing built on ATProto yet. something like @[email protected] but more complex? 🤔 #atdev #atproto

    RE: https://bsky.app/profile/did:plc:ri3vhthkocqvt3bj35b3iq57/post/3matrqcfvg22b

  39. I think Bluesky and #atdev community have some education work to do on the OAuth front, because some people seem to feel that OAuth is less secure than app passwords (see questions to Clearsky: why can't you just use app passwords like everyone else, why do I need to give you my real password etc.)

  40. You might have seen me posting about a tool called Lycan I've been building in Skythread for searching text in all the posts you've ever liked on Bluesky. It's now publicly available, you can start the import from the "Archive search" page in Skythread and then search once it's finished 🐺 #atdev

    Kuba's Journal - Launching L...

  41. My #Swiftlang #ATProto API library, ATProtoKit, has been updated to version 0.32.0. This ended up becoming a much smaller update than originally intended. It’s now been reduced to some tweaks and removals, such as adding new public initializers, as well as removing ATMacro. #atdev

    GitHub - MasterJ93/ATProtoKit ...

  42. #atdev people, how do I use this atproto-proxy thing? Do I need to have this did:web:your.app.domain#some_identifier defined somewhere on your.app.domain somehow?

    RE: https://bsky.app/profile/did:plc:uu5axsmbm2or2dngy4gwchec/post/3lsh4a6zyrk2n

  43. #atdev If you're planning to use the feed interactions API, read the subthread below this about how to handle the interactions ↓

    RE: https://bsky.app/profile/did:plc:oio4hkxaop4ao4wz2pp3f4cr/post/3lxdct7gkl22m

  44. Firehose go brrr: journal.mackuba.eu/2025/06/24/

    I wrote about doing some more optimizations in the firehose consumer, and the PR I made for the faye-websocket library #atdev #rubylang

  45. An *awesome* (not awesome) issue I ran into is that some part of zod is recursive (or some part of how it's used in Lexicons is), meaning that when the tree gets big enough, the build tools will abort until the Lexicon "complexity" comes way down. Woof. 😾 #atproto #atdev

  46. Spent the evening fighting with the codegen and build tools. The workflow is really kinda bad right now, notably many tools are not setup to fail on error. Instead they wait for *ALL* errors, which takes a SIGNIFICANTLY LONGER time when there's a problem. 😿 Anyway, tools work now. #atproto #atdev