I'm thinking about the tags for sdk.blue: I need to add a bunch of tags to each of the general libraries/SDKs like Atrium, Jacquard, at-cute, Python SDK, ATProtoKit etc.
October 23, 2025 at 1:42 PM
I'm thinking about the tags for sdk.blue: I need to add a bunch of tags to each of the general libraries/SDKs like Atrium, Jacquard, at-cute, Python SDK, ATProtoKit etc.
I didn’t expect to get to 185 stars for ATProtoKit. Thank you very much! I’m humbled for your generosity and support. 🙏
Please do continue to boost this project higher: if you can get it to 200 by the end of the year, I would greatly appreciate it.
Please do continue to boost this project higher: if you can get it to 200 by the end of the year, I would greatly appreciate it.
October 15, 2025 at 10:16 AM
I didn’t expect to get to 185 stars for ATProtoKit. Thank you very much! I’m humbled for your generosity and support. 🙏
Please do continue to boost this project higher: if you can get it to 200 by the end of the year, I would greatly appreciate it.
Please do continue to boost this project higher: if you can get it to 200 by the end of the year, I would greatly appreciate it.
In an effort to improve documentation, I've been in the process of writing an article that explains how lexicon models are supposed to behave. In general, this should help developers understand what to expect when using them. ATLexiconC will strictly abide by these rules as well.
![Serialization and Validation Behavior in Lexicon Models
Learn how lexicon models are expected to behave within ATProtoKit.
ATProtoKit’s lexicon model types implement custom `Codable` logic to support the AT Protocol’s specific data serialization and validation requirements. This article explains the common encoding, decoding, and validation rules applied across lexicon models, including date handling and field length/array size enforcement.
Overview
While lexicon model in ATProtoKit conforms to the `Codable` protocol, not all rely on the standard synthesized implementations. Instead, many models provide explicit implementations of:
- A custom `public` initializer,
- a custom `Decodable` initializer,
- a custom `Encodable` method, and
- a custom `CodingKeys` `enum`.
By having explicit implementations, ATProtoKit can help ensure the models are consistent with the lexicon the `struct`s are following, and the [...]](https://cdn.bsky.app/img/feed_thumbnail/plain/did:plc:l5ppogsebmhgu7gmw27bzqk3/bafkreigyhmdvnyilmzg5feb3gtgtfzzrvniszasmgo7pvtvlrpcq4fvuk4@jpeg)
October 13, 2025 at 9:21 AM
In an effort to improve documentation, I've been in the process of writing an article that explains how lexicon models are supposed to behave. In general, this should help developers understand what to expect when using them. ATLexiconC will strictly abide by these rules as well.
I've updated ATProtoKit to version 0.32.1. This should contain updates to the lexicon models and methods, as well as a couple of bug fixes.
#Swiftlang #ATProto #atdev
#Swiftlang #ATProto #atdev
GitHub - MasterJ93/ATProtoKit at 0.32.1
A straightforward solution for using the AT Protocol and Bluesky, written in Swift. - GitHub - MasterJ93/ATProtoKit at 0.32.1
github.com
October 5, 2025 at 5:28 AM
I've updated ATProtoKit to version 0.32.1. This should contain updates to the lexicon models and methods, as well as a couple of bug fixes.
#Swiftlang #ATProto #atdev
#Swiftlang #ATProto #atdev
⬆️ Christopher Jr Riley just released ATProtoKit v0.23.4 – A straightforward solution for using AT Protocol and Bluesky, written in Swift.
https://swiftpackageindex.com/MasterJ93/ATProtoKit#releases
https://swiftpackageindex.com/MasterJ93/ATProtoKit#releases
February 2, 2025 at 3:37 AM
⬆️ Christopher Jr Riley just released ATProtoKit v0.23.4 – A straightforward solution for using AT Protocol and Bluesky, written in Swift.
https://swiftpackageindex.com/MasterJ93/ATProtoKit#releases
https://swiftpackageindex.com/MasterJ93/ATProtoKit#releases
And yes: I'm still working on ATProtoKit, as well as the lexicon generator, and other things. I haven't abandoned it: I'm just trying to space everything out instead of being stuck working on one thing and one thing alone.
March 17, 2025 at 10:06 PM
And yes: I'm still working on ATProtoKit, as well as the lexicon generator, and other things. I haven't abandoned it: I'm just trying to space everything out instead of being stuck working on one thing and one thing alone.
I should also mention that this will be a major breaking change; this will be done with either the next update (version 0.15.0) or the one after that. It may happen in stages, beginning with the main ATProtoKit class, then the ATBlueskyChat class.
June 30, 2024 at 5:57 AM
I should also mention that this will be a major breaking change; this will be done with either the next update (version 0.15.0) or the one after that. It may happen in stages, beginning with the main ATProtoKit class, then the ATBlueskyChat class.
I've released another hotfix for ATProtoKit: 0.16.3. github.com/MasterJ93/AT...
I fixed a bug where ATProtocolConfiguration crashes the library if there's more than one instance of it (it was due to logger).
Another crash was fixed, where record embeds would crash the library.
I fixed a bug where ATProtocolConfiguration crashes the library if there's more than one instance of it (it was due to logger).
Another crash was fixed, where record embeds would crash the library.
GitHub - MasterJ93/ATProtoKit: A straightforward solution for using the AT Protocol and Bluesky, written in Swift.
A straightforward solution for using the AT Protocol and Bluesky, written in Swift. - MasterJ93/ATProtoKit
github.com
July 18, 2024 at 11:42 PM
I've released another hotfix for ATProtoKit: 0.16.3. github.com/MasterJ93/AT...
I fixed a bug where ATProtocolConfiguration crashes the library if there's more than one instance of it (it was due to logger).
Another crash was fixed, where record embeds would crash the library.
I fixed a bug where ATProtocolConfiguration crashes the library if there's more than one instance of it (it was due to logger).
Another crash was fixed, where record embeds would crash the library.
I didn’t realize that BridgyFed had made support for having clients show the full text from bridged accounts. I don’t understand why I missed that.
I’ll find a way to do it without violating the way lexicon models are handled on ATProtoKit. But after this week and not in the next few updates.
I’ll find a way to do it without violating the way lexicon models are handled on ATProtoKit. But after this week and not in the next few updates.
November 8, 2024 at 12:14 AM
I didn’t realize that BridgyFed had made support for having clients show the full text from bridged accounts. I don’t understand why I missed that.
I’ll find a way to do it without violating the way lexicon models are handled on ATProtoKit. But after this week and not in the next few updates.
I’ll find a way to do it without violating the way lexicon models are handled on ATProtoKit. But after this week and not in the next few updates.
That said, it feels a bit awkward to have some of the libraries in the ATProtoKit family to be able to build on Wasm, but the main library can't.
June 18, 2025 at 6:55 AM
That said, it feels a bit awkward to have some of the libraries in the ATProtoKit family to be able to build on Wasm, but the main library can't.
README is (mostly) completed (just need to make the logo and whatnot).
I'll let Swift Package Index host the documentation site for now (until I get the ATProtoKit website working). Ideally, I want all ATProtoKit-related things into one domain instead of being all over the place.
I'll let Swift Package Index host the documentation site for now (until I get the ATProtoKit website working). Ideally, I want all ATProtoKit-related things into one domain instead of being all over the place.
March 15, 2025 at 7:39 AM
README is (mostly) completed (just need to make the logo and whatnot).
I'll let Swift Package Index host the documentation site for now (until I get the ATProtoKit website working). Ideally, I want all ATProtoKit-related things into one domain instead of being all over the place.
I'll let Swift Package Index host the documentation site for now (until I get the ATProtoKit website working). Ideally, I want all ATProtoKit-related things into one domain instead of being all over the place.
It's also the number one source of bugs that happen within ATProtoKit, so hopefully, that package will make sure that it's less likely to happen. If it does happen, then I can purely blame it on the lexicon generator and I would have a stronger foundation because of it once it's fixed.
June 11, 2025 at 4:32 PM
It's also the number one source of bugs that happen within ATProtoKit, so hopefully, that package will make sure that it's less likely to happen. If it does happen, then I can purely blame it on the lexicon generator and I would have a stronger foundation because of it once it's fixed.
I just need to catch a break. Once ATProtoKit is finally updated, I need a break (like a week... 🙃).
Thanks for the moral support. It helps more than you realize. Good luck with your e-commerce store and may you get a ton of sales and great reviews! 👍
Thanks for the moral support. It helps more than you realize. Good luck with your e-commerce store and may you get a ton of sales and great reviews! 👍
October 2, 2024 at 6:39 AM
I just need to catch a break. Once ATProtoKit is finally updated, I need a break (like a week... 🙃).
Thanks for the moral support. It helps more than you realize. Good luck with your e-commerce store and may you get a ton of sales and great reviews! 👍
Thanks for the moral support. It helps more than you realize. Good luck with your e-commerce store and may you get a ton of sales and great reviews! 👍
An update for ATProtoKit: in the mid-future, I'm going to be re-structuring the lexicon-related models. This is a major breaking change, so I want to say it now; I'll give further warnings later on. I'll try to remember to update people on what branch to use once I've finalized everything.
May 8, 2024 at 5:57 AM
An update for ATProtoKit: in the mid-future, I'm going to be re-structuring the lexicon-related models. This is a major breaking change, so I want to say it now; I'll give further warnings later on. I'll try to remember to update people on what branch to use once I've finalized everything.
This would also allow developers to create their own configuration class, since there's a "ProtocolConfiguration" protocol that ATProtocolConfiguration conforms to.
Great! So what's the problem? ATProtoKit merely asks for the UserSession object and not the configuration object.
Great! So what's the problem? ATProtoKit merely asks for the UserSession object and not the configuration object.
December 3, 2024 at 1:11 PM
This would also allow developers to create their own configuration class, since there's a "ProtocolConfiguration" protocol that ATProtocolConfiguration conforms to.
Great! So what's the problem? ATProtoKit merely asks for the UserSession object and not the configuration object.
Great! So what's the problem? ATProtoKit merely asks for the UserSession object and not the configuration object.
I'm still working on ATProtoKit. I'm still working on it, but Zenless Zone Zero and Wuthering Waves have taken up most of my time. The games eaten up even my Warframe time: a first for me in a very long time; the only game that pulled me from Warframe was Jazz Jackrabbit 2).
July 8, 2024 at 8:39 AM
I'm still working on ATProtoKit. I'm still working on it, but Zenless Zone Zero and Wuthering Waves have taken up most of my time. The games eaten up even my Warframe time: a first for me in a very long time; the only game that pulled me from Warframe was Jazz Jackrabbit 2).
I launched my version 0.1.0 of my Swift API library for AT Protocol: ATProtoKit.
github.com/MasterJ93/AT...
It’s extremely rough and far from complete, but I hope to progress towards completing it everyday.
github.com/MasterJ93/AT...
It’s extremely rough and far from complete, but I hope to progress towards completing it everyday.
GitHub - MasterJ93/ATProtoKit: A straightforward solution for using the AT Protocol and Bluesky, written in Swift.
A straightforward solution for using the AT Protocol and Bluesky, written in Swift. - MasterJ93/ATProtoKit
github.com
February 16, 2024 at 6:39 AM
I launched my version 0.1.0 of my Swift API library for AT Protocol: ATProtoKit.
github.com/MasterJ93/AT...
It’s extremely rough and far from complete, but I hope to progress towards completing it everyday.
github.com/MasterJ93/AT...
It’s extremely rough and far from complete, but I hope to progress towards completing it everyday.
I’ve released version 0.3.1 of ATProtoKit, a Swift API library for AT Protocol and Bluesky.
github.com/MasterJ93/AT...
Among the various improvements, I’ve completed the models and methods for com.atproto.server* lexicons. I’ll work on the admin and feed ones next.
github.com/MasterJ93/AT...
Among the various improvements, I’ve completed the models and methods for com.atproto.server* lexicons. I’ll work on the admin and feed ones next.
GitHub - MasterJ93/ATProtoKit: A straightforward solution for using the AT Protocol and Bluesky, written in Swift.
A straightforward solution for using the AT Protocol and Bluesky, written in Swift. - MasterJ93/ATProtoKit
github.com
February 28, 2024 at 10:39 AM
I’ve released version 0.3.1 of ATProtoKit, a Swift API library for AT Protocol and Bluesky.
github.com/MasterJ93/AT...
Among the various improvements, I’ve completed the models and methods for com.atproto.server* lexicons. I’ll work on the admin and feed ones next.
github.com/MasterJ93/AT...
Among the various improvements, I’ve completed the models and methods for com.atproto.server* lexicons. I’ll work on the admin and feed ones next.
I should probably add notes directly in the in-line documentation of each function, showing what method was converted and what changes have been made. This should be done, and all of the ATProtoKit family of Swift packages will do just that.
May 24, 2025 at 6:05 AM
I should probably add notes directly in the in-line documentation of each function, showing what method was converted and what changes have been made. This should be done, and all of the ATProtoKit family of Swift packages will do just that.
Related to ATProtoKit, the SessionConfiguration rework has been merged to the "develop" branch. I'm going to be tweaking the article about it to remove the OAuth-related details, though: like I said, I need more time.
May 8, 2025 at 3:44 AM
Related to ATProtoKit, the SessionConfiguration rework has been merged to the "develop" branch. I'm going to be tweaking the article about it to remove the OAuth-related details, though: like I said, I need more time.
The way how ATProtoKit is written doesn't allow a flexible way to handle multiple hostnames. It just understands one: "public.api.bsky.app". I have some ideas on how to solve this issue, but I haven't tested it out yet and I don't have time to do that right this second.
May 20, 2025 at 5:06 AM
The way how ATProtoKit is written doesn't allow a flexible way to handle multiple hostnames. It just understands one: "public.api.bsky.app". I have some ideas on how to solve this issue, but I haven't tested it out yet and I don't have time to do that right this second.
Is ATProtoKit... really pushing the boundaries of Swift on non-Apple platforms? 😅 Could you explain your reasoning? Because I feel like I'm simply cobbling up some code and making it work on Linux without doing anything... novel (if that makes sense).
July 27, 2025 at 12:40 AM
Is ATProtoKit... really pushing the boundaries of Swift on non-Apple platforms? 😅 Could you explain your reasoning? Because I feel like I'm simply cobbling up some code and making it work on Linux without doing anything... novel (if that makes sense).
This is something I've been in contact with @cjrriley.com about to see if there was a way to make ATProtoKit help out with this, but if there's something I'm not thinking of please let me know. For now, I'm going to leave the functionality as is and move forward until I can resolve this refresh
October 22, 2024 at 3:10 AM
This is something I've been in contact with @cjrriley.com about to see if there was a way to make ATProtoKit help out with this, but if there's something I'm not thinking of please let me know. For now, I'm going to leave the functionality as is and move forward until I can resolve this refresh
It's possible. I'll keep that in mind and see what's the best path forward with respect to that.
Could you explain a little more about the second part of your post? Is it a pain point in ATProtoKit? Is it something that the project could potentially assist with?
Could you explain a little more about the second part of your post? Is it a pain point in ATProtoKit? Is it something that the project could potentially assist with?
November 24, 2024 at 7:02 PM
It's possible. I'll keep that in mind and see what's the best path forward with respect to that.
Could you explain a little more about the second part of your post? Is it a pain point in ATProtoKit? Is it something that the project could potentially assist with?
Could you explain a little more about the second part of your post? Is it a pain point in ATProtoKit? Is it something that the project could potentially assist with?
It appears there's a bug with respect to ATProtoKit when it comes to SwiftUI. I'll be working on it this weekend while I wrap things up.
If I can't solve it by Monday, then I'll just release the update on Monday and fix it in a hotfix update.
If I can't solve it by Monday, then I'll just release the update on Monday and fix it in a hotfix update.
September 21, 2024 at 2:49 PM
It appears there's a bug with respect to ATProtoKit when it comes to SwiftUI. I'll be working on it this weekend while I wrap things up.
If I can't solve it by Monday, then I'll just release the update on Monday and fix it in a hotfix update.
If I can't solve it by Monday, then I'll just release the update on Monday and fix it in a hotfix update.