Profile avatar
cjrriley.com
Resilient Autistic that loves solving problems with Swift. Make the world more accessible. 🇨🇦 Currently working on ATProtoKit. #atdev (Profile pic drawn by kaylee_acnh on Twitter.)
2,519 posts 1,967 followers 232 following
Regular Contributor
Active Commenter

The Maple Leafs are going to somehow disappoint me. Just watch.

I’m still sick, so I apologize for not working on ATProtoKit for the past couple of days. But seeing how I’ve been able to get past the worst of it, I should be able to work on it again beginning tomorrow.

I never, ever want to experience a freaking migraine ever again. I never knew it was such a painful experience. 😞

Unfortunately, I’m sick. 🤒 This is frustrating. I hope I can recover quickly: I still have some deadlines to meet right now…

This is... better. (I guess.) Also, I didn't realize that Apple's DocC icon only has one colour block, so part of me feels like I now have permission to use multiple colour blocks. I'll probably do that for the encompassing icon, replacing the one you see in the screenshot.

I’m still working on version 0.26.0 of ATProtoKit. OAuth is still pretty confusing, but I’m getting there; right now, I’m simply trying to see where some of the final pieces fit in place.

Update on version 0.26.0: I'm switching to simply creating an article for now. Right now, the way I've done it is just too complicated. I think that an article should be sufficient enough for learning how to deal with SessionConfiguration.

I've tested the new SessionConfiguration with a few of the lexicon methods. They seem to be running just fine, which is great! Even the UserSessionRegistry and SecureKeychainProtocol are running flawlessly.

Is this normal? From what I understand, this is related to the keychain, but I don't know if this is something I need to worry about.

My guess is that they're now scared that some AT Protocol or ActivityPub developer is going to make an Instagram killer and, therefore, they want to keep their users and finally give them one of the most requested features. (Says my delusional mind.) You're several years too late, though. 😅

Oh snap! (Now watch as everything falls apart.) ... I'm going to bed, though. That's "future Chris"'s problem to deal with. Later today.

Yeah... don't count on it being the actual number: the compiler is still finding more failures and warnings as I go along.

I apologize if you see a bunch of commits that say something like "Update lexicon models due to rework" and then some documentation fixes here and there. It's just a ton of stuff to change because the rework has changed a ton of crap.

My other API libraries have a better error handling system, which I've been meaning to implement (and even then, the ones that have the better version may not be perfect).

There's at least one lexicon method that's using `Result<Success, Failure>` as the returns type. I'm not too sure how I didn't notice that after many,... many passes of looking at the methods. That will be fixed in the next update. Sorry about that.

Making progress...